Inteqral.
EU-hosted
Provenance infrastructure

Provenance API for the EU AI Act.

One API. Sign at capture or generation. Verify and recover anywhere. EU-hosted and C2PA-conformant.

EU-hosted HSM-backed signing C2PA-conformant
Trust Vector /verify
{ o: 3 · i: 2 · d: 2 } Hardware C2PA · Social X.509 · Soft binding
01   The requirement

Machine-readable provenance is required under Article 50(2).

From 2026-08-02, AI-generated and AI-manipulated content placed on the EU market must carry machine-readable provenance under EU AI Act Article 50(2). The marking has to be readable by automated detectors and has to survive distribution. Inteqral signs, recovers, and verifies that marking through one API.

Regulation
Article 50
EU AI Act · Reg. (EU) 2024/1689
2026-08-02Current law
2026-12-02Omnibus transitional

Machine-readable marking is enforceable from 2026-08-02. Systems already on the EU market get a transitional grace period to 2026-12-02 under the Digital Omnibus provisional agreement of 7 May 2026.

Capability 01

CA and Trust-Listed signing handled for you

Article 50(2) signing needs a CA relationship and HSM-backed keys. Inteqral provides a Trust-Listed certificate chain and signs every file inside an HSM partition. You call one endpoint.

Capability 02

Recovery after a platform strips the manifest

Most platforms remove C2PA on upload. Inteqral indexes each signed file by perceptual fingerprint and returns the original manifest for a stripped copy, so the marking survives distribution.

Capability 03

A callable API over the C2PA specification

C2PA is published as an open specification. Inteqral exposes it as three endpoints with EUR billing, so a developer signs, recovers, and verifies provenance today.

EU AI Act Article 50(2), Reg. (EU) 2024/1689. Digital Omnibus provisional agreement, 7 May 2026.
02   The primitive

Every C2PA verifier returns valid or invalid. We return the vector.

An AI provider needs the marking to be readable and to survive distribution. We return origin, identity, and durability. The consumer runs its own policy. The same file passes or fails per buyer.

Live reading computed
{ o: 3 · i: 2 · d: 2 } reading

Same file, consumer policy

Each buyer reads the vector against its own threshold.
03   The interface

Three endpoints. One trust boundary.

Sign at capture or generation. Verify anywhere. Recover the original after a platform strips the manifest.

POST /sign

Attach a manifest

Attaches a C2PA manifest to any file. Signed inside the HSM partition.

POST /resolve Differentiated

Recover the original

Most platforms strip C2PA on upload. We match a stripped upload against a perceptual fingerprint and return the original manifest.

Manifest store indexed by perceptual fingerprint
POST /verify

Return the vector

Reads the manifest and returns a trust vector for origin, identity, and durability.

sign and verify
# sign a file at generation
curl -X POST https://api.inteqral.com/sign \
  -H "Authorization: Bearer $KEY" \
  -F "[email protected]" \
  -F "identity=x509" \
  -F "durability=2"

# verify anywhere and read the vector
curl -X POST https://api.inteqral.com/verify -F "[email protected]"
=> { "o": 3, "i": 2, "d": 2 }  // origin · identity (x509) · durability
Identity lane

A claims aggregator takes email, social X.509, Sumsub KYC, or an EUDI Wallet credential and emits an identity tier.

Signing core

Every file is signed inside an EU-hosted HSM partition on a Trust-Listed certificate chain.

Durability lane

A manifest store indexed by perceptual fingerprint. pHash plus an ISCC-compatible learned embedding. Optional chain anchor.

Trust boundary Keys never leave the HSM partition. Every signing call is EU-hosted.
04   Plans

One API. Usage-based plans.

Usage-based and EUR-denominated. One Article 50 obligation, one signed file, one fee.

Developer
For teams adding Article 50 provenance to a generative AI product.
Free10K signs / mo€0
Starter100K / mo€99/mo
Scale1M / mo€499/mo
Customabove 1MQuote
Volume blends to about €0.0005 to €0.001 per sign at Scale.
Commercial
For organizations that need chain-anchored signing with an SLA and audit logs.
Platformflat fee€5K to €25K
Usageper high-durability sign or resolve€0.05 to €0.50
Chain-anchored, eIDAS QTSP. SLA, audit logs, on-prem option, named support.
Sovereign
For regulated entities that need a dedicated HSM partition and on-prem deployment.
Platformflat feefrom €150K
Usageper signaturecustom
Dedicated HSM partition, on-prem deployment, EUDI Wallet integration.
Article 50(2) enforcement

Machine-readable marking is enforceable on 2026-08-02.

000days
00hours
00min
00sec
Reg. (EU) 2024/1689, Article 50(2).
Systems already on the EU market have a transitional grace period to 2026-12-02 under the Digital Omnibus provisional agreement.