Skip to main content

​
Two protocols

Every Syntalic endpoint accepts two payment protocols. The server auto-detects which you’re using from request headers — there is no separate URL or routing config.
ProtocolNetworkBest forSetup time
x402USDC on Solana or BaseAgents with a wallet~5 min
MPP/TempoTempo hosted micropaymentsAgents that can’t sign on-chain transactions~2 min

​
Pricing tiers

PersonaPrice per queryEndpoint count
Shopper$0.014
Marketing$0.015
Analyst$0.024
All prices are denominated in USD and settled in USDC (x402) or Tempo’s stablecoin equivalent (MPP).

​
Discovery

Endpoints are self-describing. Calling any URL without a payment returns: 
HTTP/1.1 402 Payment Required
Content-Type: application/json

{
  "x-payment-info": {
    "price": "0.01",
    "currency": "USD",
    "x402": {
      "recipient": "...",
      "chain": "solana",
      "asset": "USDC"
    },
    "mpp": {
      "recipient": "...",
      "network": "tempo"
    }
  }
}
Agents that speak either protocol can resolve this metadata, sign payment, and retry — fully unattended. The Syntalic server is also indexed on x402scan, so x402-aware agents can find it via discovery alone.

​
Client options

You don’t have to write your own x402 client. Three pre-built paths:
  • Syntalic MCP — our own MCP server. Leanest path for Claude/Cursor users; no third-party dependency.
  • AgentCash — universal x402 wallet + CLI for many paid APIs. Best if you already use it elsewhere.
  • 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, ~1–2 second confirmation.
  • You don’t want to manage signing keys or wallets: use MPP/Tempo. Tempo holds the balance and handles auth.