>_ USDC-Payable HTTP API

TerminalFeed accepts USDC on Base mainnet for premium real-time data calls. Built for autonomous agents with wallets.

HTTP 402 Payment Required is the RFC 7231 status code originally reserved for resources that need payment to proceed. For thirty years it sat unused because credit-card payment couldn't fit in an HTTP transaction. Stablecoins on a fast L2 changed that. TerminalFeed implements the credits-first variant of the X402 pattern: an autonomous agent buys credits with USDC, gets a bearer token, and spends across nine premium endpoints without a human in the loop.

What 1 USDC Buys You

Mainnet-Proven Today

Quick Start

# 1. Quote a credit purchase
curl -X POST https://terminalfeed.io/api/payment/buy-credits \
  -H "Content-Type: application/json" \
  -d '{"amount_usd": 1.00}'
# -> { "wallet": "0x549c...", "memo": "tf-...", "credits": 50, ... }

# 2. Send USDC on Base mainnet to the returned wallet (memo optional)

# 3. Confirm payment, mint bearer token
curl -X POST https://terminalfeed.io/api/payment/confirm \
  -H "Content-Type: application/json" \
  -d '{"tx_hash": "0xabc...", "nonce": "tf-..."}'
# -> { "token": "tf_live_<64-char-hex>", "credits": 50 }

# 4. Call any premium endpoint
curl https://terminalfeed.io/api/pro/macro \
  -H "Authorization: Bearer tf_live_<64-char-hex>"
# Response includes header X-Credits-Remaining: 48

Premium Endpoints

Nine composed endpoints, each pulling 4 to 14 upstream sources into one bearer-authenticated call:

Full detail at /api/for-agents and /developers/agent-payments. Machine-readable contract at /openapi.json.

FAQ

What is X402?

HTTP 402 Payment Required is the status code returned when a request needs payment to proceed. The X402 pattern revives this RFC 7231 status code as the primary way for autonomous agents to pay for resources on the open web. Agents send a request, receive 402 with a payment hint, settle on-chain, then retry with proof of payment. TerminalFeed implements a credits-first variant: pay once, get a bearer token, spend across many calls.

Do I need a wallet?

Yes. The agent or its operator needs a wallet that holds USDC on Base mainnet. We accept any standard ERC-20 USDC transfer to our published wallet (0x549c82e6bfc54bdae9a2073744cbc2af5d1fc6d1). No KYC. No account creation. The wallet IS the account.

Are credits refundable?

No. All credit purchases are final and non-refundable. The upside: credits never expire, so they remain spendable indefinitely on terminalfeed.io and tensorfeed.ai (shared credit pool). Buy in small amounts ($1 = 50 credits) until you know your call volume, then top up as needed.

Do tokens work on TensorFeed too?

Yes. Bearer tokens minted by /api/payment/confirm on terminalfeed.io are jointly redeemable on tensorfeed.ai. Same wallet, same chain, shared credit pool. One purchase, two data sources: real-time markets and infrastructure (TerminalFeed) plus AI news and model intelligence (TensorFeed).

Read the full agent-payments docs →