AgentServices

The paid API layer for AI agents — data, intelligence, inference, and media via x402 micropayments

Canonical project: https://github.com/vbkotecha/agentservices-api Official site: https://agentservices.to License: Apache-2.0

AgentServices is an independent project. It is not affiliated with, endorsed by, or a replacement for any other x402 market-data provider.

Live at: agentservices.to | MCP Server: https://agentservices.to/mcp (Streamable HTTP) | Discovery: /.well-known/x402

What is this?

AgentServices is the monetized API layer for AI agents. No API keys, no subscriptions — agents pay per-request with USDC on Base using the x402 payment protocol.

60+ endpoints across crypto data, market intelligence, DeFi analytics, on-chain analytics, 400+ LLM models, image generation, text-to-speech, portfolio intelligence, and dispute resolution. 12 are free. 48+ are paid via x402 (from $0.002 to $0.25 per call).

What's new in v6.0

• 400+ LLM models via OpenAI-compatible /v1/chat/completions — GPT, Claude, Gemini, DeepSeek, Grok, Llama, and more
• Smart router — use model: "auto" and the gateway classifies your task and picks the cheapest model that handles it
• Image generation — /v1/images/generations via gpt-image-2 ($0.05)
• Text-to-speech — /v1/audio/speech with natural voices ($0.05)
• 3 new MCP tools — chat, generate_image, text_to_speech

Buyer path: discover → try → pay → retain

Use the buyer quickstart for the complete path. The exact next action is to run the no-credential discovery check:

python3 examples/mcp_discovery_buyer_proof.py

Then follow the same buyer journey:

1. Discover: confirm the hosted MCP server and free tool catalog with the MCP discovery proof.
2. Try free: retrieve a real price result with the free SDK proof.
3. Inspect the paid challenge: decode the live 402 terms with the paid SDK proof. It never signs or settles payment.
4. Buy an outcome: pay the returned x402 terms, retry the same request, and retain the returned paid result. See the token-risk, market-pulse, and research-brief contracts for result limits and provenance.
5. Retain evidence: run the existing receipt builder with the original challenge, paid response, and your wallet authorization or transaction reference.

The four proofs have different limits: discovery and free SDK verify no-spend access; the paid SDK proof verifies challenge shape only; the receipt builder hashes buyer-held evidence and does not verify settlement. None of them claims adoption, settlement, or revenue.

For activation measurement definitions, see Activation Metrics. To probe the live funnel, run python3 examples/check_activation_funnel.py.

Buyer path: discover → try → pay → retain

Use the buyer quickstart for the complete path. The exact next action is to run the no-credential discovery check:

python3 examples/mcp_discovery_buyer_proof.py

Then follow the same buyer journey:

1. Discover: confirm the hosted MCP server and free tool catalog with the MCP discovery proof.
2. Try free: retrieve a real price result with the free SDK proof.
3. Inspect the paid challenge: decode the live 402 terms with the paid SDK proof. It never signs or settles payment.
4. Buy an outcome: pay the returned x402 terms, retry the same request, and retain the returned paid result. See the token-risk, market-pulse, and research-brief contracts for result limits and provenance.
5. Retain evidence: run the existing receipt builder with the original challenge, paid response, and your wallet authorization or transaction reference.

The four proofs have different limits: discovery and free SDK verify no-spend access; the paid SDK proof verifies challenge shape only; the receipt builder hashes buyer-held evidence and does not verify settlement. None of them claims adoption, settlement, or revenue.

Endpoints

Free (no payment required)

Trade API — venue doors (FREE — not x402)

AgentServices is building venue trade doors under /v1/trade/{venue}/…. Hyperliquid ships first; more venues and a venue-neutral /v1/trade/execute router follow.

Each door is a policy leash + forward — not a smarter router. We do not claim better fills than the venue direct. Execution is free at the call (no x402 on the order path). Builder fees are omitted so routing through us is not more expensive than going direct.

We never collect venue API keys. Agents sign orders locally with an HL-approved agent wallet (approveAgent on the main wallet is the one human bootstrap step). AgentServices policy-checks (max notional, coin allowlist, kill switch) and forwards the signed payload.

Request bodies accept market_type: spot, perp, or future. Hyperliquid implements perp and spot today; unsupported types return a machine-readable market_type_not_supported error.

Legacy hl_* MCP tool names remain as aliases. See GET /v1/trade/hyperliquid/bootstrap for the approveAgent signing model.

Roadmap: /v1/trade/{venue} for additional venues; /v1/trade/execute for venue-neutral routing later.

Paid — Data APIs (x402)

Paid — Synthesis APIs (x402)