Skip to main content

Two protocols

Every paid Syntalic route accepts two payment protocols. Free discovery routes need no payment. The server auto-detects which you’re using from request headers — there is no separate URL or routing config.

Prices

One price per call, the same on both rails: $0.01 to $0.05, set by the measure or the endpoint’s area. The full table is on Pricing. Prices are in USD and settle in USDC (x402) or USDC.e (MPP). Social and Scout calls are scoped to a Shopify taxonomy path (food-beverages-tobacco, health-beauty, or a node under one). Retired browse roots such as grocery-gourmet-food are refused before payment.

Discovery

A valid unpaid request to a paid route returns a 402 carrying the payment options:
  • payment-required header and body accepts[]: the x402 options, one per chain, with amount, asset and payTo.
  • www-authenticate: Payment header: the MPP challenge.
Use the free discovery surfaces: GET /openapi.json (published operations, schemas and prices), GET /v1/measures (available measures and splits), GET /.well-known/x402 (payment discovery), and GET /llms.txt (agent-readable guide). The server is also on x402scan.

Client options

You don’t have to write your own client. Three ready paths:
  • Syntalic MCP — our own MCP server. Leanest path for Claude/Cursor users; handles payment routing for you.
  • pay.sh — the pay CLI and registry. Best if your agent already runs under it.
  • Direct HTTP — official @x402/fetch wrapper for full control over signing.

Which protocol should I use?

  • Your agent has a Solana or EVM wallet: use x402. Settlement is on-chain in USDC; how long it takes depends on the chain and network load.
  • Your funds are USDC.e on Tempo: use MPP/Tempo.

Errors and retries

Send the unpaid request first. A request that can’t succeed is usually refused before the 402, at no charge, and some of those checks run only on the unpaid request. Once you have paid, don’t assume an error was free: an MPP payment is always settled before the query runs, and an x402 payment can be too, so a request that then fails may still be charged. Before retrying, check the status, the problem details (error.code) and any payment receipt. Follow Retry-After when present. If the x402 challenge advertises the optional payment-identifier extension, reuse the same identifier, signed payment and request when retrying; a response you have already paid for is returned again, with X-Payment-Replayed: true, without a second charge. PAYMENT_IN_PROGRESS means to wait and retry the same request; PAYMENT_IDENTIFIER_CONFLICT means the identifier is already bound to another request or payment. After a timeout or an unclear payment result, don’t automatically sign a new payment: the first one may already have settled.