A Serper alternative for agents that pay their own way

Pick Serper if

You run high volumes from your own backend and already hold an API key. On price per call it wins.

Pick x402serps if

Your agent should pay per call without a human creating accounts, you want one MCP endpoint with search, extract, research and crawl, or you want to pay in USDC.

How it works

x402serps and Serper both return fast JSON search results. The difference is how you pay and connect. x402serps can be paid per call with x402 (USDC on Base or Solana) with no account, or with prepaid card credits, and it ships an MCP server so agents can call it as a tool directly.

A search costs $0.004 for up to 10 results. Serper's own pricing is per 1,000 queries and is often lower at volume, so if you already have a Serper account and only need raw search, it may stay the better fit. x402serps is for cases where an agent should pay for itself, where you want one key-free endpoint for search, news, extract and verticals, or where you want MCP out of the box.

Responses use a small fixed shape (position, title, url, snippet) and the provider field tells you whether the primary or a backup provider served the call.

Request and response: /api/v1/search

POST /api/v1/search costs $0.004 per call. Send the parameters as a JSON body.

curl -X POST https://x402serps.com/api/v1/search \
  -H "content-type: application/json" \
  -H "X-Trial: 1" \
  -d '{"q":"x402 protocol","num":10,"gl":"us"}'

Example response (values shortened; field names are exactly what the API returns):

{
  "query": "x402 protocol",
  "provider": "primary",
  "results": [
    {
      "position": 1,
      "title": "x402",
      "url": "https://x402.org/",
      "snippet": "x402 is an open payment standard that lets clients pay for APIs and content over HTTP..."
    },
    {
      "position": 2,
      "title": "coinbase/x402: A payments protocol for the internet",
      "url": "https://github.com/coinbase/x402",
      "snippet": "x402 is a chain-agnostic protocol built around the HTTP 402 Payment Required status code..."
    }
  ]
}

Request and response: /api/v1/extract

POST /api/v1/extract costs $0.004 per call. Send the parameters as a JSON body.

curl -X POST https://x402serps.com/api/v1/extract \
  -H "content-type: application/json" \
  -H "X-Trial: 1" \
  -d '{"url":"https://example.com"}'

Example response (values shortened; field names are exactly what the API returns):

{
  "url": "https://example.com",
  "finalUrl": "https://example.com",
  "title": "Example Domain",
  "contentType": "text/html",
  "markdown": "This domain is for use in documentation examples without needing permission...",
  "length": 156,
  "truncated": false
}

Use cases

• Autonomous agents with wallets. An agent with USDC can buy searches as needed without a human creating an account.
• Search plus page reading. Call /api/v1/extract on the URLs you get back to read pages as markdown.
• MCP clients. Connect Claude Code, Cursor or another MCP client to https://x402serps.com/api/mcp.
• Failover. Calls fail over to a backup provider when one is configured, and /status shows uptime.

Paying for calls

Every call is priced on its own. With x402, an unpaid request returns HTTP 402 with the exact amount, asset and recipient for USDC on Base or Solana; your client signs a payment and repeats the same request, and results come back once the payment settles. No account or API key is involved. If you would rather pay by card, buy a credit pack on the pricing page and send Authorization: Bearer xs_.... Cached repeat queries cost half for credit keys, and failed calls are not charged. Paid calls have no per-minute rate limit.

FAQ