
Paddock
finance.paddockv3.6.0Updated Oct 2, 2026
Pre-payment verification for AI agents.
Overview
Lets an assistant verify x402 payment endpoints and query market data on AI agent commerce before spending money.
- What it does
- Paddock is a remote MCP server for pre-payment verification and market intelligence on x402 agent payments. Its main tool, verify_before_pay, probes a target endpoint live, checks its contract and published config, and returns a route verdict with dated evidence. Other tools cover market summaries, category detail, provider ranking, domain liveness, snapshot diffs, circular-settlement and whale signals, token metrics, provider revenue, and report data. It can also emit signed Ed25519 attestations for a check.
- When to use it
- Use it when an agent is about to authorize an x402 payment it cannot reverse and needs to confirm the endpoint is real, live, and fairly priced. It also suits agents choosing or ranking providers, checking whether a service is still up, or tracking where agent-commerce spend is moving.
- Requirements
- A remote streamable HTTP endpoint; no local runtime or package. The free tool get_market_summary needs no authentication. Other tools need a free key (issued from an email address), a paid subscription key passed as the api_key argument or X-Paddock-Key header, or per-query USDC settlement via x402. Network access to the endpoint is required.
Installation
In SourceWeft
- Open Paddock in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"paddock": {
"type": "http",
"url": "https://paddock.finance/api/mcp/mcp"
}
}
}README
Paddock
Agent payments have no chargeback. Paddock is pre-payment verification for AI agents.
It checks that an x402 API is real, live, and fairly priced before your agent pays it, and it measures what AI agents actually pay each other on x402 across Base and Solana.
Paddock snapshots the live agent economy, transaction volume, spend, buyers, providers, category share, and reliability, and serves it through a set of MCP tools and an HTTP API that agents can call directly, paying per query with x402 or with a subscription key.
Note on
openapi.json: Theopenapi.jsonin this repository is a byte-for-byte mirror of the live specification served atpaddock.finance/openapi.json, which is generated from the site's route and is the source of truth. Both declare the sameinfo.version(currently3.8.0); if they ever disagree, the live specification is correct and this file is stale. Use either for tool discovery and client generation.
Why agents call it
- Should I pay this endpoint right now?
verify_before_payprobes the target live, checks the contract against what you expect and the seller's own published config, then adds settlement recency, the circular signal, and price versus market, before your agent authorizes a payment it cannot take back. - Find the best live provider. Rank providers in a category by a composite of reliability (7-day success rate), reputation (unique buyers), and price, so an agent can route to the strongest option, not just the cheapest.
- Is this service still up? Per-domain liveness lookup, up/down, 7-day probe success rate, and latency, before an agent commits a paid call to a provider.
- Where's demand moving? Diff today's snapshot against a past date to see new services, retired services, category share movements, and top movers, so an agent knows where spend is shifting.
The MCP tools
Twelve tools are live, across three access tiers. get_market_summary needs no authentication at all. Five tools are covered by a free key, 10 calls per UTC day, shared across all five, issued instantly from an email address. The rest are premium: a Paddock API key, an x402/MPP per-query payment, or one free trial call per day (where noted).
The paid tools (verify_before_pay, get_niche_gaps, get_best_value_provider, get_liveness, get_changes, get_circular_signal, get_whale_activity, get_token_metrics, get_provider_revenue) each allow one free trial call per day per IP. get_report_data has no free trial on the full-data route; only its metadata is free.
get_report_datais published with two paths. The free-metadata route (/api/paddock/mcp/report-data) is declared withsecurity: []and is deliberately excluded from x402scan indexing; the full-data route (/api/paddock/mcp/report-data/paid) carries the x402 payment scheme. Both are visible inopenapi.json.
Signed attestations
Paddock can emit a signed attestation for any pre-payment check: a portable JSON record carrying the observed payment terms, the settlement history it was checked against, the observation window, and the verdict, signed Ed25519 over an RFC 8785 canonical form. The signing key is published at a well-known path, and records verify standalone with no API access and no trust in Paddock. This is the attested-evidence format proposed for the x402 dispute-resolution extension.
- The public key path:
/.well-known/paddock-attestation-key - Verify it yourself: fetch the record, canonicalize per RFC 8785, check the Ed25519 signature against the published key.
- Live example: https://paddock.finance/a/mFxHpIcBGHR0NsmkpT8rHb0wvX_8tIr3K0xOl_4W4UY
Connecting from Claude Desktop
In Claude Desktop, open Settings → Connectors → Add custom connector, then paste the Paddock MCP URL below. Claude discovers the tools automatically.
The free tools work over the connector with no authentication. The paid tools work over the connector too: pass your Paddock API key as the api_key argument on the tool call and the server forwards it as the X-Paddock-Key header, billing the call against your subscription. Omit api_key to use the once-per-day free trial, or to settle the tool's USDC price via x402 pay-per-query.
Connecting from other MCP clients
Paddock exposes a standard MCP HTTP transport at the same URL: point any MCP-compatible client at it:
For tool discovery, schemas, and the full route map, see openapi.json in this repository (mirrored to paddock.finance/openapi.json).
The free key
New here? Build on Paddock is the walkthrough: 60-second start, what each free tool is actually good for, five worked examples, and how to size your usage. The rest of this README is reference.
get_market_summary is open to everyone with no key, no signup, and no rate limit. It is the citation surface. If you are quoting a Paddock figure, quote it from here.
Five more tools, verify_before_pay, get_category_detail, get_niche_gaps, get_token_metrics, get_liveness, are covered by a free key. One request gets you one:
The key is returned in the response and emailed to you. Pass it as the X-Paddock-Key header, or as the api_key argument over the MCP connector.
- 10 calls per UTC day, shared across all five tools, one counter, not 10 each.
- Every successful response carries a
usageobject (used,limit,remaining,resets_at) so you can meter yourself. - Over the limit returns a structured 429 naming the reset time and both paid paths.
- Premium tools are never on a free key. Calling one returns a structured 402 naming the price, and that refusal is not counted against your daily limit.
Free trial and free key are different. The free trial is 1 call per IP per day with no key at all, shared across the paid tools, a zero-friction taste, and it still works. The free key is the workflow tier above it, tied to your key rather than your IP.
Free for development and internal use. Redistribution, resale, or serving Paddock data to your end users requires a commercial license: see paddock.finance/api-access or contact [email protected].
Pricing
The x402 per-query option is for agent-native, pay-per-pull access with no subscription: an agent settles the tool's USDC price at call time. To subscribe to Builder or Pro Agent and obtain an API key, see paddock.finance/api-access.
Authentication
Keys come in three classes and all travel the same way, in the X-Paddock-Key header: pk_free_ (free tier, five tools, 10/day shared), pk_builder_ ($99/mo) and pk_proagent_ ($499/mo). Paid tools accept a Builder or Pro Agent key; Send the key with each request and the call is billed against your subscription's daily quota. Over the MCP connector (e.g. in Claude), pass the key as the api_key tool argument instead; the server forwards it as X-Paddock-Key. Alternatively, agents can pay per query with x402: omit the key and settle the tool's USDC price via the x402 payment flow at call time. Free tools require neither.
Docs & contact
- Canonical documentation:
paddock.finance/docs - Questions:
[email protected] - On X: @PaddockFinance
Status
Production. Snapshots written daily at 23:30 UTC.
Source: README.md at commit 69f3b10
Tools
0Version history
1- v3.6.0LatestOct 2, 2026

