> ## Documentation Index
> Fetch the complete documentation index at: https://crushrewards.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Payments overview

> Two payment protocols, three integration paths.

## 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.

| Protocol                   | Network                    | Best for                                     | Setup time |
| -------------------------- | -------------------------- | -------------------------------------------- | ---------- |
| [x402](/payments/x402)     | USDC on Solana or Base     | Agents with a wallet                         | \~5 min    |
| [MPP/Tempo](/payments/mpp) | Tempo hosted micropayments | Agents that can't sign on-chain transactions | \~2 min    |

## Pricing tiers

| Persona   | Price per query | Endpoint count |
| --------- | --------------- | -------------- |
| Shopper   | \$0.01          | 4              |
| Marketing | \$0.01          | 5              |
| Analyst   | \$0.02          | 4              |

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 theme={null}
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](https://www.x402scan.com/server/fdf15e0c-8d66-49ae-acbb-d872c75e5147), 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](/integrate/mcp)** — our own MCP server. Leanest path for Claude/Cursor users; no third-party dependency.
* **[AgentCash](/integrate/agentcash)** — universal x402 wallet + CLI for many paid APIs. Best if you already use it elsewhere.
* **[Direct HTTP](/integrate/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](/payments/x402). Settlement is on-chain in USDC, \~1–2 second confirmation.
* **You don't want to manage signing keys or wallets:** use [MPP/Tempo](/payments/mpp). Tempo holds the balance and handles auth.