Managed C2PA Signing API — Content Credentials

Adding C2PA Content Credentials to your digital assets is valuable for your brand, and in some cases required by law. However, just setting up an in-house pilot often takes months of development time. The Trufo Provenance Platform provides a suite of APIs and SDKs designed specifically for companies looking to add Content Credentials into their workflow.

One Call, Every Feature

There are hundreds of pages of C2PA specifications and dozens of approval processes needed to properly set up a Generator Product (here is a guide). With the Signing API, only a single call is needed, and it is as simple as:

from pathlib import Path

from trufo import sign_c2pa_test
from trufo.util.credentials import TrufoApiKey, load_api_key

api_key = load_api_key(TrufoApiKey.C2PA_SIGN_TEST)

media_bytes = Path("input.jpg").read_bytes()
signed_bytes = sign_c2pa_test(
    api_key,
    media_bytes,
    actions=[
        ["publish", {}],
        ["watermark", {}],
    ],
    assertions=[
        ["ai_disclosure", {}],
        ["cawg_identity", {"cawg_identity_id": "test"}],
    ],
)

Note that the snippet above runs against the test environment, so you can develop and validate your workflow before going live. Use of the Python SDK is not mandatory; it sits above a REST API that you can call from any system. To our knowledge, Trufo is the only C2PA provider that is feature-complete: certificates, timestamps, C2PA and CAWG, watermarks, etc. — trusted by the IPTC and by many other reputable brands.

The onboarding process is quick: create an account on the Trufo Dashboard, set up your account MFA and invite other members to your organization, then purchase the API product and submit the Organization Validation (OV) form.

Documentation

Detailed documentation is available:

Product Tiers

Trufo offers three Signing API tiers:

For more information on what each tier entails, please send an email to contact@trufo.ai or book a Consultation to speak to one of our experts.

Local Processing

For quick integrations, Trufo provides a fully-hosted API, where you send the media file to Trufo servers for signing. For situations where the media files are large (network data cost) or where the media files are sensitive (privacy concerns), Trufo’s SDK allows you to do all the media processing locally, so that the media file never needs to be sent over the Internet. The hash digest is sent to Trufo servers, and if soft-binding is enabled, so is the C2PA manifest for remote recovery. To use the SDK, simply run:

# pip install "trufo[local-full]"

from pathlib import Path

from trufo import sign_c2pa_distributed_test
from trufo.util.credentials import TrufoApiKey, load_api_key

api_key = load_api_key(TrufoApiKey.C2PA_SIGN_TEST)

media_bytes = Path("input.jpg").read_bytes()
signed_bytes = sign_c2pa_distributed_test(
    api_key,
    media_bytes,
    actions=[
        ["publish", {}],
        ["watermark", {}],
    ],
    assertions=[
        ["ai_disclosure", {}],
        ["cawg_identity", {"cawg_identity_id": "test"}],
    ],
)

Watermark Soft-Binding

The Signing API comes with a flag-enabled watermark soft-binding feature, registered as an official C2PA soft-binding algorithm with decoding settings that you can manage. Trufo’s watermarks are the strongest in every modality, so you can rest assured that you will be treating your digital assets well. A GPU is recommended for any local watermarking deployment.

Performance & Scale

The standard signing API runs at 500ms p99 latency for small content — inclusive of database reads and writes, processing, C2PA signing, CAWG signing, trusted timestamps (TSA), and OCSP. Enterprise plans support up to 100 RPS, and Trufo currently handles billions of API calls per year.

Pricing scales well with volume, from a hundred a month to a hundred million a month. Full details are on the Trufo Dashboard.

The Trufo Provenance Platform supports a number of use cases: