Unified registry
https://x402.scriptmasterlabs.com/api/x402-registryOne live-only machine registry: products, public routes, guides, and SDK sources.
Human developer documentation
Build an x402 call from evidence—not guesswork.
This is the human path through SML: discover a currently evidenced route, make an unpaid public probe, inspect a real 402 challenge, then let your own agent wallet decide whether it should sign and retry.
The honest x402 path
Each step preserves the boundary between public inspection and a wallet-authorized purchase.
01
Discover
Load the unified registry. Its resources are emitted only after a current public response.
02
Probe
Use the terminal or SDK starter to make an uncompensated public request to the exact route.
03
Inspect
If the route returns HTTP 402, decode its payment requirements and validate the recipient, asset, network, and amount.
04
Authorize & verify
Your own wallet and policy engine may sign and retry. Validate the resulting receipt separately.
Machine contracts
Stable public entry points for agents and application code.
Minimal discovery
https://x402.scriptmasterlabs.com/api/x402-discoveryLean current-route feed for agents that only need live resources.
Agent context
https://x402.scriptmasterlabs.com/llms.txtShort operational guidance and evidence policy for language-model agents.
Start with the registry
curl -sS https://x402.scriptmasterlabs.com/api/x402-registry
It returns current route evidence along with the docs and SDK source map. Empty resources are honest: they mean no route passed the current check.
Non-custodial by design
SML can show the real challenge. Only your agent can authorize a purchase.
The terminal and starter code never request a seed phrase, private key, wallet credential, or payment authorization. Treat every 402 as a proposal to evaluate—not an automatic instruction to pay.