Documentation

CryptoCadet docs

CryptoCadet puts content and APIs behind an HTTP 402 gateway. Sellers set a price per query. AI agents, or any HTTP client, pay when a URL answers 402 Payment Required, then get the response.

How it works

Every item a seller publishes gets a gateway URL of the form https://api.v4.cryptocadet.app/v4/g/<handle>/<slug>. A request without payment gets a 402 response whose JSON body states the price and the ways to pay. The client pays and repeats the request, and the gateway serves the item: either content CryptoCadet hosts, or the seller's own API, which the gateway calls on the buyer's behalf.

Prices are in US dollars. There are two ways to pay:

Card credits. The buyer tops up a prepaid balance by card through Stripe and gives each agent a token with its own spending caps. No crypto needed.
USDC on Base. The agent pays from its own wallet. The payment goes through the CryptoCadetRouter contract, which sends the seller their share and the fee in the same transaction.

The two sides

One account can sell and buy. Both use the same CLI, cryptocadet (alias ccx).

SellPublish hosted content or put your API behind the gateway. Earn USDC on Base, minus a 3% fee.BuyGive your agent card credits with capped tokens, or a local USDC wallet with a spending policy. Pay with cryptocadet fetch.

Try it

Terminal

curl -fsSL https://cryptocadet.app/install.sh | sh
cryptocadet init
cryptocadet login
cryptocadet fetch https://api.v4.cryptocadet.app/v4/g/<handle>/<slug>

The Quickstart walks through these steps, including how to fund the agent first.

Where to go next

Installcurl, Homebrew, npm and Windows.QuickstartFrom sign-up to your first paid fetch.ConceptsThe gateway, payment rails, wallets, tokens and fees.CLI commandsEvery command, grouped by task.HTTP gateway APIPay from any HTTP client, without the CLI.TroubleshootingCommon errors and how to fix them.

NotePayments in USDC are on-chain transfers on Base and cannot be reversed. Card credits are spent only inside the CryptoCadet gateway.