SCRIPTMASTERLABS · PRIMARY-SOURCE EVIDENCE

Evidence worth citing.

The Evidence Hub exists to separate observed facts from marketing state. Each record publishes a substantive fact set with a canonical human page and, where appropriate, machine-readable projections. Synthetic tests are never counted as buyers, rankings, settlement or external citations.

SETTLEMENT CUT · 2026-10-02

88% was a bridge.

August’s x402-shaped EVM flow was $2.59B. Strip the bridge and the agent-shaped payments on Base and Polygon moved about $57,000. Four buckets the standard needs — bridge, facilitator settlement, dust cycle, accepted buyer. Machine JSON beside it.

Read the cut →

WHAT COUNTS

Reproducible observations.

Useful evidence names the source, route or artifact being observed; records enough context to reproduce the observation; distinguishes current runtime state from historical state; and keeps unknown or unavailable facts explicit.

WHAT DOES NOT COUNT

No proof inflation.

HTTP reachability is not settlement. A 402 challenge is not a purchase. A payment signature alone is not settlement. An internal probe is not a stranger buyer. A directory listing is not an endorsement unless the directory itself explicitly says so.

CAPSULE 2026-09-06-ROUTE-AUTHORITY-01

Outside-in agent route authority audit

ScriptMasterLabs documented a split between its current first-party agent routing and known legacy entry points that can still exist in external caches or older integrations. This record helps agents distinguish current authority from legacy discovery metadata instead of silently treating every historical route as production truth.

MCPx402route authorityagent discovery

Human-readable record · JSON · CSV

HOW TO USE SML EVIDENCE

Start from the current authority surface.

For live API capability and payment terms, use runtime contracts and fresh target responses. For product routing, use the current buyer-evidence and machine-intent surfaces. For historical observations, cite the dated evidence record and preserve its time boundary rather than projecting it forward as current state.

Open x402 challenge safety vectors: 20 synthetic test cases in machine-readable JSON, checked by executable offline tests. These are implementation tests, not a live market audit.

MACHINE FEEDS

JSON Feed · Citation Mesh contract · Demand-matched research queue · Root machine guide

These public machine surfaces make evidence easier to discover; they do not create evidence by themselves. A crawler seeing a record does not turn that record into a ranking, purchase or external citation.

Publisher: Script Master Labs LLC / SCRIPTMASTERLABS. Correction policy: prior records are not silently rewritten to manufacture freshness. Substantive changes require a new version, a new dated record, or an explicit correction.