C2PA signing, packaging, and service operations.
This documentation covers the current HTTP service surface, runtime configuration, packaging flows, and operational paths for local and S3-backed deployments. The emphasis is practical: build the spec, call the API, and run the service with the feature profile you actually need.
Contact Us to access it todayStart Here
Get Started
Build the docs, review the API spec, and run the service locally.
Canonical Contract
API Reference
Use the behavior-focused route documentation as the primary human-readable contract.
Feature-Gated Flow
Run With S3
Build the service with `s3`, configure allowed buckets, and route outputs to object storage.
v2
Documented route surface
OpenAPI
Synchronized from service source
Local + S3
Operational paths covered
Primary Paths¶
Use these entry points when you want the shortest path to a working service, the API contract, or a deployment-specific guide.
Runtime
Running Local
Start with local files and local output artifacts before enabling extra features.
Configuration
Configuration Guide
Review current defaults, feature-gated settings, upload limits, and startup expectations.
Docs Tooling
API Docs Mode
Understand the synchronized `api/openapi.json`, runtime `/openapi.json`, and docs build path.
API Highlights¶
The service documentation distinguishes the human-written contract from raw examples and the generated machine-readable spec.
Authoritative
API Reference
Route purpose, accepted inputs, sync versus async behavior, and current status codes.
Execution
cURL Examples
Concrete request payloads for video and audio signing, fragmented publishing, packaging, package+sign, custom assertions, and parent provenance.
Raw OpenAPI
Raw OpenAPI
Open the generated OpenAPI JSON directly from this docs site.
Operational Paths¶
Feature Profile
Run With S3
Enable S3-backed input resolution and request-selected S3 outputs with the right feature flags.
Operations
Troubleshooting
Use this when startup fails, external tools are missing, or runtime limits need adjustment.
Documentation Source¶
Public documentation is maintained in this repository. The generated OpenAPI specification is synchronized from the private service implementation so the public API contract stays tied to the code.
Live /openapi.json exists only when service-http is built with --features openapi. Live /docs exists only when service-http is built with --features "openapi scalar-docs".