DeepChamp for Agents

The free tools need no account and no key. Try one now.

curl 'https://deepchampai.com/api/agent/v1/slate/today?sport=nba'

Connect a coding agent over remote MCP. Pick your client:

claude mcp add --transport http deepchamp https://deepchampai.com/mcp

{
  "mcpServers": {
    "deepchamp": {
      "url": "https://deepchampai.com/mcp"
    }
  }
}

{
  "servers": {
    "deepchamp": {
      "type": "http",
      "url": "https://deepchampai.com/mcp"
    }
  }
}

https://deepchampai.com/mcp

Install the agent skill

npx skills add https://deepchampai.com --skill deepchamp-edge -g -y

The skill teaches your agent every tool and when to use it. The OpenAPI 3.1 document at /openapi.json describes every live REST operation; generate a client from it with any OpenAPI tool.

Every response has four parts: data, compliance, meta and billing. Errors use a smaller body (see Errors).

Prices are integers in micro-USD: one US dollar is 1,000,000 micro-USD. Free responses are cacheable for five minutes. Paid and error responses are never cacheable.

Free tools: none. Do not send a key. Paid tools: one of two ways, which you can mix. Paying is the signup, so there is no form to fill in first.

• Pay per call. Call the tool, receive an HTTP 402 payment challenge, pay it, and repeat the request with the credential. The receipt is your identity.
• API key. A key spends a prepaid balance. Send it in the X-DC-Api-Key header. Keys look like dc_sk_live_ followed by an id, a secret and a checksum, so secret scanners can find a leak. Only a hash is stored. A key is shown once and can be rotated or revoked.

curl 'https://deepchampai.com/api/agent/v1/ranked-picks?sport=nba' \
  -H 'X-DC-Api-Key: dc_sk_live_<your key>' \
  -H 'Idempotency-Key: 6f1c1a52-0a0e-4f6e-9a77-5f0f5d1c9d11'

Never put a key in client-side code, a public repository or a prompt. Paid access is not open yet: only the free tools are live today.

A paid call without a valid credential returns HTTP 402 Payment Required (REST) or JSON-RPC error -32042 (MCP) with a payment challenge: the price, the methods we accept and an expiry. Your agent pays and repeats the same request with the credential. We use the HTTP payment authentication scheme (the Machine Payments Protocol), so clients such as the Stripe link CLI and the mppx library do the exchange for you.

# 1. Call a paid tool without a credential
curl -i 'https://deepchampai.com/api/agent/v1/ranked-picks?sport=nba'
#    HTTP/1.1 402 Payment Required
#    WWW-Authenticate: Payment ...   (the challenge: price, methods, expiry)

# 2. Pay the challenge with a method your agent supports, for example a card token
npx @stripe/link-cli mpp pay '<url>'

# 3. Repeat the same request with the credential and a stable idempotency key
curl -i 'https://deepchampai.com/api/agent/v1/ranked-picks?sport=nba' \
  -H 'Authorization: Payment <credential>' \
  -H 'Idempotency-Key: 6f1c1a52-0a0e-4f6e-9a77-5f0f5d1c9d11'
#    HTTP/1.1 200 OK   (billing.status = charged, Payment-Receipt header)

Rails and their status

• Card, by Shared Payment Token Coming soon npx @stripe/link-cli mpp pay <url>
  Machine Payments Protocol (MPP). US businesses, all states.
• Stablecoin (USDC) over MPP and x402 Coming soon
  US customers except New York. Switches on after our payment processor completes its stablecoin access review.
• stripe pay, zero fee (enterprise) Coming soon stripe pay @deepchampai --dry-run
  Enterprise settles at a 5% discount on this rail.
• Invoice (enterprise) Coming soon
  From $500 per month.
• Stripe Projects Coming soon stripe projects add deepchamp/edge-api
  Listing in progress.
• API key Coming soon
  Never put a key in client-side code, a public repository or a prompt.

No payment rail is live yet. The free tools never ask for payment.

Payment minimums set what can be paid per call: a card payment needs at least $0.50 and a stablecoin payment at least one cent. Calls priced below that, such as the calculators at half a cent, are prepaid-only: fund a balance and use an API key. The 402 response says which methods can pay the call in front of you.

Idempotency

Send an Idempotency-Key header (up to 120 characters) on every paid call. A repeat with the same key and the same request returns the stored response with billing.status of replayed and does not charge again. The same key with a different request is 409 idempotency_conflict. A payment receipt buys exactly one successful call; a receipt whose call failed can be reused.

When you are charged

You are charged only when billing.status is charged. You are never charged for a client or server error, a rate limit, a paused line, a provider fault, a timeout, a refused or filtered answer, or a replay. Every error body says billable: false. If a charge ever lands for a call that failed, it is refunded.

We only ever receive payments. DeepChamp never sends money. Card payments settle to our Stripe balance; stablecoin is converted to dollars by Stripe; every paid call has a receipt and a ledger entry.

One row per tool, from the catalog the MCP server, the OpenAPI document and the agent card also read. A tool is live only when its product line is on. The live price book is deepchampai.com/api/agent/v1/pricing and always wins over this table.

Routes are relative to https://deepchampai.com/api/agent/v1. Free tools also have these routes: GET /slate/{date}, GET /matchup/{sport}/{date}/{slug}, GET /pricing, GET /catalog and GET /health.

Two calls are always free and never billed. They are how you tell us what you need, and they decide what we build next.

• POST /request-capability (MCP tool request_capability): ask for a sport, a market type, a format, a latency or a history we do not offer. Enumerated fields plus one optional 280-character note. Ten a day per account.
• POST /rate-response (MCP tool rate_response): rate a response you received as useful or not useful, with a reason when it was not. One rating per request_id.

Notes that contain an at-sign, a link, a long number or a key-shaped token are dropped, not stored. Do not put secrets or personal data in a note.

Every ranked signal carries signal_id, content_hash, model_version and issued_at. The signal_id is stable for identical content. The issued_at time is when we first issued exactly that content. The content_hash is a hash of the immutable fields of the signal, so you can check that the copy you hold is the copy we issued.

Signals are appended to a hash-chained ledger. Ask the verify endpoint whether the hash you hold matches: it returns the issue time, the model version, the chain position and a matches flag. Verification opens with the picks line. The ledger exists for the people who receive signals and for our own evaluation. It records issue times and content, never outcomes.

How to evaluate DeepChamp shows how to use these fields to measure the intelligence yourself.

Errors use one shape and are never billed or cached:

{
  "error": {
    "code": "rate_limited",
    "message": "The free tier allows 20 requests a minute and 300 a day per client. Retry in 43 seconds.",
    "request_id": "req_0000000000sample0000",
    "billable": false,
    "retry_after_seconds": 43
  }
}

A 429 or 503 may carry a Retry-After header. Back off, then retry; use the same Idempotency-Key for a paid retry.

Free tools: 20 requests a minute and 300 a day per IP address, cached for 5 minutes, for today minus 1 to today plus 1 (US Eastern), one sport per call and at most 30 games. Sports: nba, nfl, mlb, nhl, cfb, cbb, wnba.

Paid callers get higher limits by tier. These are beta defaults. Per-key overrides exist and the numbers may change; the response headers and error bodies always state the limit that applies.

Using many keys, addresses or accounts to get around a limit breaks the Acceptable Use Policy. There is no service level in the beta.

The API path is versioned (/api/agent/v1). Adding fields and tools is not a breaking change; build clients that ignore fields they do not know. We give 30 days' notice of a breaking change to a paid tool unless a law, a data provider or security requires faster action. The model version is in meta.model_version on every response.

Status: deepchampai.com/api/agent/v1/health returns liveness and which lines are on, with no upstream calls.

Using the API means accepting two documents. Read them before you build.

• Beta API Terms: the licence, what you may not do, payments and refunds, relaying the compliance object, no automated wagering, and liability.
• Acceptable Use Policy: adults only, no operators without a written agreement, no resale or scraping, honest presentation.
• Privacy Policy.

Research and information, not betting advice. No outcomes are guaranteed. Adults 21+ only, where legal. Every response carries a compliance object. When your product shows our output, or something built from it, to a person, show the notice and the helpline in readable text, say that it is AI-generated, and say it is for adults 21 and over. Show it at the start of each session and with every response that presents a ranked signal, a probability or an edge score.

{
  "age_gate": 21,
  "notice": "Research and information, not betting advice. No outcomes are guaranteed. Adults 21+ only, where legal. AI-generated analysis can be wrong; use your own judgment.",
  "helpline": "1-800-MY-RESET",
  "helpline_url": "https://www.1800myreset.org",
  "ai_generated": true,
  "terms_url": "https://deepchampai.com/terms/api",
  "privacy_url": "https://deepchampai.com/privacy"
}

A person makes every betting decision. Automated wagering with our output is not allowed. If someone shows signs of distress about gambling, show the helpline and do not use an output to encourage more betting. Problem gambling help: call or text 1-800-MY-RESET, or chat at 1800myreset.org.