x402 / Pay per request
Sports data an agent can pay for with x402.
HalfPoint's API accepts x402. Without an account or key, an AI agent with a wallet pays in USDC on Base (eip155:8453) per request: USD 0.01 for /odds, 0.05 with the Risk fields, and USD 0.002 for /fixtures, /live and /grades. For many calls or the stream, it buys a pass: a plan for a period, from USD 15 for Realtime for 24 hours.
01 / Prices
Per request.
| Route | Host | Price (USD) |
|---|---|---|
/odds | odds.halfpoint.tech | 0.01 |
/odds?plan=x402.risk | odds.halfpoint.tech | 0.05, with stop, widened and range |
/fixtures, /live, /grades | fixtures.halfpoint.tech | 0.002 |
02 / Sequence
402, sign, 200.
x402 version 2 only: the payment goes in the PAYMENT-SIGNATURE header. An x402 client library does this for you.
GET https://odds.halfpoint.tech/odds?league=nba
→ 402, PAYMENT-REQUIRED: scheme exact, USDC,
the amount in its smallest unit, the address paid
GET https://odds.halfpoint.tech/odds?league=nba
PAYMENT-SIGNATURE: <the signed payment>
→ 200 once the payment is settled,
PAYMENT-RESPONSE: <the transaction>Only an answer that delivers data (2xx) is settled: an error is not charged, and a paid request always gets the full answer. A payer may have 2 paid requests open at once, and one payment serves one request. Paying for a request accepts the terms of service.
03 / Passes
A plan for a period.
A pass comes with a key, shown once, that works until the period ends. Realtime and Risk open the streams. A pass has no email login: a lost key is replaced by signing a message with the paying wallet.
POST https://account.halfpoint.tech/x402/pass?plan=realtime&period=24h| Plan | Period | Price (USD) |
|---|---|---|
realtime | 24h | 15 |
risk | 24h | 49 |
realtime | 7d | 69 |
04 / Docs
Read the documentation.
Questions
Which sports data APIs can an AI agent pay per request with x402?
HalfPoint's API accepts x402. Without an account or key, an agent pays in USDC on Base (eip155:8453): USD 0.01 per /odds request (0.05 with ?plan=x402.risk, which adds stop, widened and range) and USD 0.002 per /fixtures, /live or /grades request.
How does an x402 payment work on HalfPoint?
A request without a key answers 402 with the payment requirements in the PAYMENT-REQUIRED header (scheme exact, USDC, the amount in its smallest unit, the address paid). Retry with the signed payment in the PAYMENT-SIGNATURE header: the answer comes once the payment is settled, with PAYMENT-RESPONSE (the transaction). An x402 client library does this for you.
Which x402 version does HalfPoint support?
Version 2 only. A version 1 client's X-PAYMENT header is not read, and the request gets 402 again.
Is an x402 request charged when it fails?
No. Only an answer that delivers data (2xx) is settled: an error is not charged, and a paid request always gets the full answer, never 304.
What is an x402 pass?
A plan for a period, paid in USDC, with a key that is shown once and works until the period ends: Realtime for 24 hours (USD 15) or 7 days (USD 69), Risk for 24 hours (USD 49). Realtime and Risk open the streams. A pass has no email login; a lost key is replaced by signing a message with the paying wallet.
Consensus and Risk for the sharp side of the market.