Solution mapping
How Capture helps you comply
One integration. Two provenance layers. Every Article 50 content-marking requirement satisfied — with auditable evidence for regulators.
Architecture
Three layers, one pipeline
Layer 1 — C2PA signing
Embed cryptographically signed content credentials into every AI-generated file at the moment of creation. The credentials include the generator identity, creation timestamp, and a tamper-evident hash of the content. Satisfies Article 50(2) and 50(4).
Layer 2 — ERC-7053 on-chain
Register the content hash on the Numbers Mainnet blockchain. This creates a public, immutable record that survives metadata stripping, screenshotting, and format conversion. Satisfies Article 50(5) durability requirements.
Layer 3 — x402 consent
When AI agents access your content, x402 generates verifiable licensing receipts on-chain. This creates an auditable consent trail that maps to the provenance-of-consent requirements regulators look for.
Requirement mapping
Article 50 to Capture, line by line
| Article 50 requirement | Capture layer | How it works |
|---|---|---|
| Machine-readable marking — 50(2) | C2PA (Layer 1) | Content credentials with generator claim, timestamp, and content hash embedded in file metadata |
| Interoperable format — 50(2) | C2PA (Layer 1) | C2PA is an open, vendor-neutral standard adopted by Adobe, Microsoft, Google, BBC, and 200+ organisations |
| Deepfake labelling — 50(4) | C2PA (Layer 1) | The c2pa.actions manifest with generator assertion identifies synthetic origin |
| Robust, durable marking — 50(5) | ERC-7053 (Layer 2) | On-chain content hash survives metadata stripping, screenshot, re-upload, and format conversion |
| Multi-layer approach — Code of Practice | Layers 1 + 2 | Two independent signals — in-file C2PA plus on-chain ERC-7053 — satisfy the multi-layer mandate |
| Verifiable consent — regulatory best practice | x402 (Layer 3) | HTTP-native micropayment receipts create an auditable licensing chain from creator to AI consumer |
Competitive landscape
How Capture compares
| Capability | Adobe CAI | Truepic | Capture |
|---|---|---|---|
| C2PA signing | Yes | Yes | Yes |
| On-chain durability (ERC-7053) | No | No | Yes |
| Survives metadata stripping | No | No | Yes (via hash lookup) |
| x402 licensing / consent receipts | No | No | Yes |
| Multi-layer (Code of Practice) | Single layer | Single layer | Two layers |
| ISO 27001 certified signing | Yes | Yes | Yes |
| Open standards only | Partial | Partial | Fully open |
Integration
Four steps to compliance
Install the SDK
Add the Capture SDK to your AI inference pipeline. Available as Node.js, Python, REST API, CLI, or native iOS/Android SDKs.
Sign at generation
Call the Capture signing API after your AI model generates content, before delivering to users. C2PA credentials are embedded automatically.
Register on-chain
The same API call registers the content hash on the Numbers Mainnet via ERC-7053. No separate integration needed.
Verify and audit
Use the Capture audit dashboard to export compliance evidence — C2PA validity, on-chain records, and x402 consent receipts — for regulators or third-party assessors.
Sample integration (Node.js)
import { CaptureSDK } from '@nicktomlin/capture-sdk';
const capture = new CaptureSDK({ apiKey: process.env.CAPTURE_API_KEY });
// After your AI model generates an image:
const signed = await capture.sign({
file: generatedImage,
generator: 'my-ai-model-v2',
assertions: [{ label: 'c2pa.created', data: { date: new Date() } }]
});
// signed.c2pa → embedded C2PA credential
// signed.nid → ERC-7053 on-chain record ID
// signed.url → verification URLFrequently asked
Integration and compliance questions
How does Capture help comply with Article 50?
Capture provides a single integration that satisfies Article 50 content-marking requirements through two layers. Layer 1 embeds C2PA content credentials in the file at generation time. Layer 2 registers the content hash on the Numbers Mainnet via ERC-7053. Together, they deliver the multi-layered approach the EU draft Code of Practice mandates.
Do I need to change my AI model to use Capture?
No. Capture operates as post-generation middleware. It signs content after your model generates it, before delivery to users. No model retraining, no architecture changes. The signing API adds sub-100ms median latency.
How is Capture different from Adobe Content Authenticity Initiative?
Adobe CAI provides C2PA signing but does not include an on-chain durability layer. When C2PA metadata is stripped (screenshot, re-upload), provenance is lost. Capture adds ERC-7053 on-chain registration as a second layer, so provenance survives metadata stripping. Capture also includes x402 licensing for consent receipts.
What content types does Capture support?
Capture supports images (JPEG, PNG, WebP, AVIF, HEIC, TIFF), video (MP4, MOV, WebM), audio (WAV, MP3, FLAC, AAC), and PDF documents. The C2PA standard defines the credential format; ERC-7053 is content-type agnostic since it registers the content hash.
How long does integration take?
A typical integration takes 1-2 weeks. Capture provides a Node.js SDK, REST API, CLI, and native iOS/Android SDKs. Reuters completed integration in under 4 weeks with a complex multi-system pipeline; smaller teams ship in days.
What happens when someone screenshots my AI-generated image?
The screenshot strips the embedded C2PA metadata. However, the original content hash was registered on-chain via ERC-7053 at generation time. Any compliant verifier can compute the hash of the original (or a perceptual hash match) and look up the on-chain record to recover the full provenance chain.
Does Capture work with x402 licensing for consent receipts?
Yes. x402 is HTTP-native micropayment protocol that Capture integrates for licensing. When an AI agent accesses your content, x402 generates a verifiable consent receipt — satisfying the provenance-of-consent requirement that auditors look for under Article 50.
Is Capture ISO certified?
Yes. Numbers Protocol, the company behind Capture, holds ISO 27001 certification for its C2PA signing infrastructure. This is important for enterprise compliance, as auditors require evidence of security controls around the signing process.
Start your compliance integration
Get a free 30-day proof-of-concept and ship Article 50 compliance before the deadline.