For platforms and enterprise
Verify the images you cannot vouch for
Platforms and enterprises handle images from people they do not control, and the rules now expect them to know which images are real. Lumethic checks a photo against its RAW file and records the result as a C2PA credential, over an API that handles the volumes a platform deals with.
What Lumethic is
How it fits into a platform
Lumethic runs as an API. You send a photo together with its RAW file, the service compares them, and it returns a result and a C2PA credential. Nothing runs on your side and nothing changes about how photos are taken, so it works with the cameras and RAW files your suppliers already use.
The check reads the sensor data in the RAW file and returns a clear result you can store and act on. That suits a pipeline that has to reach the same decision on every image it handles, at scale.
What you get
For high-volume pipelines
API integration
A REST API with authentication, webhooks, and client libraries. Verification runs inside your existing upload or moderation flow.
Verify, then sign
Each photo that passes gets a Lumethic-attested C2PA credential recording what was checked and when. The credential uses the C2PA format, so standard C2PA tools can read it.
Works with existing kit
It uses the RAW files cameras already record, so your suppliers and contributors need no new hardware and no special capture app.
Volume-based pricing
Pricing is based on volume and agreed directly, so it follows how your verification load actually grows.
Who uses it
Where platforms use it
The same API covers several settings where an unverified image carries a real cost. Each card links to more detail.
Marketplaces and e-commerce
Confirm that product photos from sellers and suppliers are real captures before a listing goes live, and keep a record that supports your own labelling and fraud decisions.
See the e-commerce solutionNews agencies and media
Check freelance and wire submissions against their RAW files before publication, and keep a record that the image was verified in case it is questioned later.
Read the editorial guideEvidence and forensic platforms
Add a verification and a tamper-evident credential to an evidence or claims system through the API. It strengthens the chain of custody without changing how photos are captured.
Read the chain-of-custody guideInsurance: verified photos from your appraisers
For the photos your appraisers, adjusters and surveyors take themselves. Lumethic checks each report photo against its camera RAW, or a capture from Lumethic Capture on iPhone, and records what was checked and when. It is not a screening tool for claimant-submitted JPEGs.
Read the insurance guideWhy it matters now
What the August 2026 rules change
Since 2 August 2026, the EU AI Act requires providers of generative AI systems to mark synthetic images in a machine-readable way, and deployers of systems that generate deepfakes to disclose them. Breaches of these transparency duties can cost up to 15 million euros or 3 percent of worldwide turnover. None of this obliges a platform to verify the images it receives. The practical consequence is different: as marking spreads, an image without a mark and without provenance becomes the one that draws questions from buyers, partners, and fraud teams. A verified credential gives a platform a documented basis for its own decisions about such images, grounded in the camera file.
See the compliance overview and AI Act timelineIntegration and data handling
For a technical and procurement review
A review usually comes down to 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 used only for the verification requested and are never shared or used for training.
- Processing runs on infrastructure in the European Union, and deletion follows Article 17 of the GDPR.
- A data processing agreement is available on request.
Talk to us about integration
Write to us with a few lines about your platform, what you need to verify, and the volumes involved. A real person reads it and replies. If you would rather look around first, the API documentation and pricing are public.