HTTP-native endpoints
Every registered asset becomes a standard URL. Returns 402 Payment Required to unauthenticated agents, and the licensed file once payment lands on-chain.
API
x402 Licensing — pay-per-fetch for the AI era.
Capture is the first and only blockchain licensing framework with x402 support. Wrap every C2PA-signed, ERC-7053-registered asset in an HTTP-native licensing endpoint — AI agents simply call the URL, pay the micropayment, and receive an on-chain consent receipt.
What is x402 Licensing?
x402 Licensing exposes every Capture-registered asset as a paid HTTP endpoint that AI agents can fetch directly using the x402 protocol. Provenance, payment, and audit happen in a single round-trip — no API keys, no contracts, no custom integration.
Capabilities
What you get
Per-fetch USDC settlement
AI agents pay between $0.01 and $1.00 USDC per fetch on Base L2. Settlement fees are ~$0.0001, so even sub-cent transactions are profitable.
On-chain consent receipts
Every successful fetch mints an audit-ready receipt linking agent → asset → payment → license terms. Satisfies the EU AI Act multi-layer requirement.
Open standard
Stewarded by the x402 Foundation (Coinbase + Cloudflare). No proprietary lock-in — your endpoints work with any compliant agent or browser.
Who it's for
Built for these scenarios
AI training data licensing
Sell consent-based access to your photos, videos, and articles for AI training. Each fetch pays you directly, with a consent receipt anchored on-chain for compliance.
Real-time editorial agents
Newsroom AI agents fetch verified imagery on demand, paying licensing fees that flow back to the originating photographer or publisher.
Synthetic content provenance
AI-generated content can sign and register through Capture, then expose itself as a paid endpoint with full attribution to the underlying training data.
Quick start
Get integrated in minutes
# AI agent fetches a licensed asset using x402
curl -X GET https://licensing.captureapp.xyz/asset/0xABC123 \
-H "X-Payment: <signed-x402-payment>" \
-o licensed-image.jpg
# Server responds with the file + receipt:
# 200 OK
# X-Receipt: 0xRECEIPT_HASH
# Content-Type: image/jpeg
Agents can also receive a 402 Payment Required first, sign a payment, and retry. See docs for the full protocol.
Built on open standards
x402 — HTTP 402 Payment Required protocol
C2PA — Content credentials embedded in the response
ERC-7053 — On-chain registration linked to each endpoint
Frequently asked
x402 Licensing questions
What is x402?
x402 is the HTTP-native micropayment protocol stewarded by the x402 Foundation (Coinbase and Cloudflare). It uses the existing HTTP 402 Payment Required status code to let any web resource demand a stablecoin payment before serving content. The standard processed over 119 million transactions on Base in its first year.
How does Capture x402 Licensing make money for creators?
When an AI agent fetches your asset, it pays a USDC micropayment (typically $0.01–$1.00) directly to your wallet. You set the price per asset class. There are no platform subscription fees — Capture earns a small percentage on settlement only.
Do AI agents actually pay these fees?
Yes. Major AI platforms (Coinbase Agent Kit, Perplexity, and others) have integrated x402 to pay for verified content. The economic logic is clear — a $0.01 fetch with a 99% gross margin (after $0.0001 settlement) is worth it for compliance-grade training data.
What if an agent ignores the paywall?
The asset URL returns the file only when the x402 payment has settled on-chain. Agents that try to access without paying receive a 402 status. ERC-7053 registration also serves as proof of unauthorized use if discovered later.