C2PA 2.4 / 115 STANDARD CODES / LOCAL
Turn validation codes into an evidence action list.
Paste a code list or a crJSON statusCodes object. The tool separates observed failures, review conditions and success evidence without guessing what custom codes mean.
- 16
- SUCCESS
- 15
- INFORMATIONAL
- 84
- FAILURE
EVIDENCE TRIAGE
Status input and review
No file is selected or uploaded. Submitted URLs and explanations are not returned by the result.
SUPPLIED STATUS
Accepted: space, comma or line-separated codes; arrays; statusCodes; activeManifest; validationResults.activeManifest.
EVIDENCE STATE
Run the triage to classify supplied observations.
- 0
- FAILURE
- 0
- REVIEW
- 0
- SUCCESS
- 0
- CUSTOM / INVALID
No interpreted codes yet.
FREE MCP / READ ONLY / NO AUTH
Give the same triage contract to an AI agent.
The focused endpoint exposes the 115-code catalog, a reusable prompt and structured output. It accepts no source media and has no paid tool.
https://agents.hogarmas.net/mcp/content-credentials
TOOL
triage_c2pa_validation_statuses
OFFICIAL CATALOG
Explore every standard C2PA 2.4 code
Meanings below come from the C2PA 2.4 status tables. Custom namespaces are intentionally not added to the standard catalog.
115 / 115
INTERPRETATION BOUNDARY
Evidence status is not a truth verdict.
- Success code
- One positive observation, not proof that every validation phase ran.
- Failure code
- A reported validation problem in an affected structure, not proof that visible content is false.
- Custom code
- Emitter-defined. Its namespace documentation remains authoritative.
- Source media
- Never accepted by this interpreter; use the local workspace for actual file inspection.
Source: C2PA Content Credentials 2.4, section 10.2.2. Specification text is CC BY 4.0. OPEN OFFICIAL SOURCE