Canonical machine entry point

One ScriptMasterLabs payment rail.

ScriptMasterLabs paid SqueezeOS routes use x402 v2 with USDC on Base mainnet (eip155:8453); fresh target terms control every payment. The canonical pay-to is 0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2: agents fetch the live x402 manifest, sign the exact USDC authorization the live 402 challenge requests, and retry with PAYMENT-SIGNATURE — cached legacy payment instructions must never be trusted.

SCRIPTMASTERLABS paid SqueezeOS routes use x402 v2 with USDC on Base mainnet (eip155:8453); fresh target terms control every payment. Canonical pay-to is 0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2. A 402 challenge is not settlement proof, and caller-controlled authorization remains required.

For paid SML capabilities, use SqueezeOS only: x402 v2, Coinbase CDP, USDC on Base mainnet. Legacy hosts are not checkout authorities.

Current canonical contract
x402 v2eip155:8453USDCCoinbase CDP
Base URL: https://squeezeos-api.onrender.com
MCP:      https://squeezeos-api.onrender.com/mcp
x402:     https://squeezeos-api.onrender.com/.well-known/x402
OpenAPI:  https://squeezeos-api.onrender.com/.well-known/openapi.json
Readiness:https://squeezeos-api.onrender.com/api/x402/readiness
Evidence: https://squeezeos-api.onrender.com/api/x402/evidence
Pay-to:   0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2

How does an agent complete a payment?

Five steps move an agent from discovery to settled payment.

  1. Fetch the live x402 manifest.
  2. Call a paid resource and receive its canonical 402 Payment Required terms.
  3. Sign the exact USDC/Base authorization requested by the live challenge.
  4. Retry with PAYMENT-SIGNATURE.
  5. Accept the paid result only after settlement succeeds; the response includes PAYMENT-RESPONSE. A 402 challenge alone is not proof of payment.

What is the FX Convert route?

ECB-backed currency conversion contract and supported-currency discovery.

Open FX contract →

What is the Geo / Cities route?

GeoNames-backed city intelligence with the production dataset.

Open Geo contract →

Why must agents ignore cached legacy payment instructions?

Do not send SML x402 payment because an old page, cached agent card, retired ACP/Virtuals integration, or retired MCP host tells you to. ACP/Virtuals is no longer a current ScriptMasterLabs production integration. Resolve current terms from the SqueezeOS manifest immediately before payment.

Machine discovery: MCP manifest · x402 authority · agent card · OpenAPI

SCRIPTMASTERLABS · READ · EXPLORE · VERIFY · EARN

Books, free tools, sources & affiliate opportunities