MPA Content Provenance
Sign, embed, and verify C2PA manifests in MPA files (.mpa, .mpg)
What Is MPA Provenance?
MPEG audio format for broadcast and multimedia applications. MPA provenance covers broadcast audio streams and legacy multimedia content.
With Encypher, MPA files carry their own cryptographic proof of origin. A C2PA manifest is embedded directly into the file, recording who created it, when, and whether it has been modified. Anyone can verify a signed MPA file for free, without authentication.
How C2PA Manifests Are Embedded in MPA Files
- MIME Type
- audio/mpa
- File Extensions
- .mpa, .mpg
- Embedding Method
- JUMBF data stored in MPEG audio frame structure
- Container Type
- MPEG audio frame
- Verification Pipeline
- c2pa-python (native C2PA library support)
The C2PA manifest contains a JUMBF (JPEG Universal Metadata Box Format) store with COSE-signed claims. For MPA files, the manifest is stored using jumbf data stored in mpeg audio frame structure. The signing process does not alter the audio content itself. The manifest is metadata, not a modification of the audio samples.
Use Cases for MPA Provenance
- Broadcast audio
- Multimedia applications
- Legacy audio systems
How to Sign MPA Content with Encypher
MPA signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your MPA file, and the API returns a signed copy with an embedded C2PA manifest.
curl -X POST https://api.encypher.com/api/v1/sign/media \ -H "Authorization: Bearer YOUR_API_KEY" \ -F "file=@example.mpa" \ -F "title=My MPA Content" \ -F "action=c2pa.created" \ -o signed.mpa
Verify MPA Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed MPA file to confirm its origin, check for tampering, and read the embedded rights information.