For platforms and enterprise

Verification infrastructure for the images you cannot vouch for

Platforms and enterprises handle images from people they do not control, under rules that now require knowing which images are real. Lumethic checks a photo against its RAW source and records the result as a C2PA credential, through an API that runs at the volume a platform needs.

What Lumethic is

A verification step you call, not a system you run

Lumethic is a post-capture verification service. You send a photo and its RAW file, the service compares them, and you get back a result and a C2PA credential. There is no model to train, no hardware to deploy, and no change to how images are captured, which means it works with the cameras and files your suppliers already use.

Because the check is deterministic, based on sensor data rather than a probability, the result is something you can act on and keep. That makes it a fit for a pipeline that has to make the same decision on every image, consistently and at scale.

What you get

Built for a high-volume pipeline

API-first integration

A REST API with authentication, webhooks, and client libraries, so verification fits into an existing upload, intake, or moderation flow rather than sitting beside it.

Verify-then-sign credentials

Each genuine photo carries a C2PA credential that records what was checked and when. The record is interoperable and can be read by any C2PA-compatible tool.

Fits existing workflows

Works with the RAW files cameras already record, so suppliers and contributors do not need new hardware or a specific capture app.

Volume-based terms

Pricing is based on volume and agreed directly, so it tracks the way your verification load actually scales rather than a per-seat plan.

Why it matters now

The regulatory deadline is the buying trigger

The EU AI Act brings transparency duties for AI-generated images, with the first obligations for organisations that publish or distribute content taking effect on 2 August 2026. The ESPR adds product-passport duties for marketplaces. Both push platforms to know which images are real at the point of upload, and penalties for non-compliance can reach into the millions of euros or a share of worldwide turnover. A verified credential gives a platform a defensible record instead of an estimate from a detector that can be wrong.

See the compliance overview and AI Act timeline

Integration and data handling

What your engineering and procurement teams will ask

The points that usually come up in a review are how verification integrates, where data is processed, and what happens to the files afterwards.

  • A REST API with authentication, webhooks, and client libraries, plus an MCP server for agent-based workflows.
  • RAW files are processed in memory and are not stored, so the most sensitive input is short-lived.
  • Processing runs on infrastructure located in the European Union, with deletion consistent with Article 17 of the GDPR.
  • A data processing agreement is available on request for procurement review.

Talk to us about integration

Start with the API documentation, or get in touch about volume verification and a pilot for your platform.