x402 pay-per-fetch
AI agents call any registered asset's URL, pay USDC, and receive the file plus an on-chain consent receipt. Per-fetch pricing scales from $0.001 to $1.00 per asset.
Industry solution
Capture for Artificial Intelligence
Provide ethical, consent-based training data with cryptographic provenance. Enable AI companies to comply with EU AI Act Article 50 and California SB 942 while compensating creators on every fetch.
The challenge
What's broken today
AI companies need vast amounts of training data, but copyright suits, opt-out demands, and the EU AI Act's August 2026 enforcement are forcing a shift to consent-based, traceable sourcing. Existing licensing tools were built for humans negotiating contracts, not for agents fetching individual assets at runtime.
How Capture helps
Built-in for Artificial Intelligence
ERC-7053 provenance
Every training data sample carries an immutable on-chain record proving when, by whom, and under what licence it was acquired. Auditors can replay your training set's full chain of custody.
C2PA Article-50 marking
Synthesised outputs are signed with C2PA credentials at inference time, satisfying the EU AI Act's machine-readable marking requirement out of the box.
Consent receipt API
Each fetch produces a structured receipt your training pipeline can store and present to regulators. No spreadsheet juggling, no proof-of-license disputes.
Regulatory alignment
Compliance, by design
| Regulation | What it requires | How Capture satisfies it |
|---|---|---|
| EU AI Act Article 50 | Machine-readable marking of AI-generated content | C2PA credentials embedded in every output + ERC-7053 on-chain record (the multi-layer approach the draft Code of Practice mandates) |
| California SB 942 | Disclosure of AI-generated content | C2PA generator claim plus on-chain attestation |
| NIST AI Risk Framework | Provenance and accountability for AI systems | Numbers Protocol explicitly cited in NIST guidance for digital content trust |
| EU Copyright DSM | TDM opt-out compliance | tdm-policy.json + Capture metadata signal whether training is permitted, automatically |
Recommended stack
Best products for this use case
"Capture's C2PA integration has provided our users with a reliable way to verify content origins. It's a powerful tool for building trust."
Ping-Lin ChangFounder & CEO, Instill AI
Frequently asked
Artificial Intelligence questions
How does Capture help us comply with EU AI Act Article 50?
Capture combines two layers required by the draft Code of Practice — embedded C2PA credentials in every AI output and ERC-7053 on-chain registration. Even if a metadata-stripping screenshot bypasses the first layer, the on-chain record proves provenance independently. This multi-layer approach is exactly what the regulation demands.
Are AI agents really paying x402 fees in production?
Yes. Coinbase Agent Kit, Perplexity, and several leading AI startups have integrated x402 in 2026. The protocol processed over 119 million transactions on Base in its first year. Sub-cent fees are economically viable thanks to ~$0.0001 settlement costs.
Can we use Capture without exposing user data to a third party?
Yes. C2PA signing happens on-device or server-side, with only file hashes and signing payloads crossing our boundary. ERC-7053 registration writes a hash, not your data. You retain custody throughout.
What does it cost?
x402 settlement fees are small (~$0.0001 per transaction). Capture earns a small percentage on settled licenses. C2PA signing pricing is tiered by volume — see the pricing page for details. Self-hosted SDK usage is free.