Documentation
Overview
Fundamentals
Connecting to your database
Importing data
Securing your data
Working with your data
Managing tables and views
Working with arrays
Managing indexes
Concepts
Implementing cascade deletes
Dropping objects safely
Dropping objects safely
Guardian Tools API
Developer quickstart
Analyze media for AI generation or manipulation and get a signed verdict in minutes. Learn the basics of the Guardian Tools platform.
curl
1 curl -H “Authorization: Bearer $TOKEN” \
2 -H “Content-Type: application/json” \
3 -d ‘{
“webLocation”: “https://example.com/asset.jpg”,
“modality”: “image”
}’ \
4 https://tools.guardian.deepid.app/deepfake/detect
Mark what you detect
Guardian Tools can write every verdict back into the file as a cryptographically signed C2PA Content Credential — so the result travels with the asset, not just in your database.
Purpose and scope
This document explains what content credentials cover, who they are for, and where they fit in a media trust workflow.
EU AI Act & Code of Practice
How signed content credentials support transparency obligations under the EU AI Act and related codes of practice.
Technical overview
A high-level look at how credentials are generated, attached to assets, and validated end to end.
What is written into the file
The manifest data embedded into each asset, including provenance claims, timestamps, and signatures.
Cryptographic signing profile
The keys, algorithms, and certificate chain used to sign credentials and prove authenticity.
Supported formats
Image, audio, and video formats that support embedded content credentials.
Independent verification
How third parties can validate credentials without trusting the signer directly.
Scope vs. other measures
How content credentials compare to watermarking, hashing, and detection-based approaches.
Summary
A recap of what content credentials provide and when to rely on them.
Contact
Reach our team for integration support, certificates, and verification questions.