Agentic Services (x402)

Pay-per-call APIs on the Agentic Services marketplace, gated by the x402 payment protocol on Polygon mainnet. No API keys or subscriptions — each call costs a small USDC amount drawn from your wallet. The CLI (x402-pay) detects the 402 response, signs the exact payment, and retries automatically.

• Base URL: https://agentic-services.polygon.technology
• Live catalog (source of truth): GET https://agentic-services.polygon.technology/api/discover/routes
• Full provider docs: https://agentic-services.polygon.technology/SKILL.md

Always read the live catalog first. It returns every active route with its exact proxy path, method, price, and payTo address (CORS enabled, no payment required to read it). Prices and available services change — treat the catalog as authoritative and this file as orientation.

Prerequisites — check before any x402 call

Every call spends USDC from a funded Polygon wallet. Before running x402-pay:

agent wallet list        # is a wallet configured?

If no wallet is listed, set one up:

1. agent wallet login: opens the agentconnect login page in the browser; sign in with Google or email (works on headless hosts too, no extra flags needed). No setup step is needed first: keys are defaulted, and login auto-provisions Builder credentials.
2. agent wallet address: get the address, then fund it (agent fund)
3. agent balances: confirm USDC is available on Polygon (chain 137) before calling any x402 endpoint

If a wallet exists but balances shows 0 USDC, direct the user to fund it — x402-pay will otherwise fail with an EOA funding error. All services settle in USDC on Polygon (0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359, chain id 137).

How to call a service

Use the full route URL from the catalog. Request bodies and query params mirror the upstream provider's own API.

# POST with a JSON body (e.g. Exa web search)
agent x402-pay \
  --url "https://agentic-services.polygon.technology/api/proxy/exa/search" \
  --wallet main --method POST \
  --body '{"query": "polygon agentic payments", "numResults": 5}'

# GET with query params (e.g. SearchApi Google search)
agent x402-pay \
  --url "https://agentic-services.polygon.technology/api/proxy/searchapi/google?q=<query>" \
  --wallet main --method GET

# Scrape a page to clean markdown (Firecrawl)
agent x402-pay \
  --url "https://agentic-services.polygon.technology/api/proxy/firecrawl/scrape" \
  --wallet main --method POST --body '{"url": "https://example.com"}'

# LLM inference (Llama 3.3 70B, OpenAI-compatible chat body)
agent x402-pay \
  --url "https://agentic-services.polygon.technology/api/proxy/nim/llama-3.3-70b/chat" \
  --wallet main --method POST \
  --body '{"messages": [{"role": "user", "content": "Summarize Polygon in one line."}]}'

Chain and token are auto-detected from the 402 response — no manual config.

Catalog

Prices are per call, in USDC, settling on Polygon (chain 137). All routes below are relative to the base URL https://agentic-services.polygon.technology.

Search, scraping & news (proxied)

AI inference (proxied)

Web automation & email (proxied)

On-chain data, email inboxes & RPC (external providers)

These are x402-native providers: you call their own endpoint URL directly (not a /api/proxy/* path), still settling in USDC on Polygon. x402-pay handles the 402 exactly the same way. Pass the full URL below as --url.

QuickNode RPC — $0.001/call, POST standard JSON-RPC. URL pattern https://x402.quicknode.com/<chain>/:

agent x402-pay \
  --url "https://x402.quicknode.com/matic-mainnet/" \
  --wallet main --method POST \
  --body '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Allium — on-chain wallet analytics — base https://agents.allium.so/api/v1/developer/:

AgentMail — email inbox for the agent — $2/call, base https://x402.api.agentmail.to/v0/inboxes:

How x402 works

1. CLI sends the request to the endpoint.
2. Endpoint responds with HTTP 402 Payment Required + payment details (price, asset, network, payTo).
3. CLI signs an EIP-3009 transferWithAuthorization for the exact amount from the wallet.
4. CLI retries the request with the payment header.
5. Endpoint verifies, calls the upstream API, returns the response; the settlement tx hash comes back in the PAYMENT-RESPONSE header.

The whole flow is transparent to the agent. Chain and token are auto-detected from the 402 response. Do not guess endpoints or search the web for providers — read the live catalog (/api/discover/routes) for the correct, current URLs and prices.