Was it authorized?
Active rights, scoped decisions, short-lived signed tokens, usage reservations, asset lineage, and audit receipts.
Ask for permission.
Carry the proof.
One authorization service for the workspace and delegated production agents. Creator signatures and verified payment establish the grant before an agent can use it.
What happened to it?
Custom assertion payloads link to Bitpass. Manifest IDs remain separate. This app does not yet embed or validate C2PA media.
How do agents ask?
An experimental synchronous SendMessage adapter calls the same policy service. The Bitpass extension is application-specific, not a published standard.
Let a personal dot find the next collaboration.
The callmyagent MCP connector supports both sides: search verified creators for advertisers, or find published gigs for creators. Discovery uses public listings and never signs or pays.
Connect your dot → · Find or publish gigs →
Request an exact use.
Provision an agent credential with a licensee identity and a fixed audience. Send its bearer credential to the API. Successful authorization reserves one use and returns a five-minute ES256 permission token.
POST /api/bitpass/campaigns/{campaign_id}/authorize
Authorization: Bearer <delegated-agent-credential>
Content-Type: application/json
{
"idempotencyKey": "generation-job-1042",
"use": {
"action": "generate.video",
"provider": "Runway",
"channels": ["TikTok"],
"territories": ["US"],
"face": true,
"voice": false,
"training": false,
"parentAssetIds": []
}
}Complete the chain.
| Endpoint | Purpose |
|---|---|
POST /api/bitpass/campaigns | Human signs a request; verified parties required |
POST /api/bitpass/campaigns/{id}/approve | Creator signs the same agreement |
POST /api/bitpass/campaigns/{id}/checkout | Licensee opens hosted Stripe checkout |
POST /api/bitpass/campaigns/{id}/authorize | Reserve one scoped generation or publication use |
POST /api/bitpass/campaigns/{id}/assets | Register output digest, token, and optional manifest ID |
POST /api/bitpass/campaigns/{id}/publish | Record publication evidence against an issued token |
POST /api/bitpass/campaigns/{id}/revoke | Creator ends future authorization |
GET /api/bitpass/grants/{id}/status | Minimal public current status |
GET /.well-known/jwks.json | Current public verification key |
POST /api/a2a | Experimental A2A SendMessage adapter |
POST /api/mcp | Read-only discovery and grant-status tooling |
Verification has two parts.
Validate the token signature with the issuer’s trusted public key, then check issuer, audience, request digest, grant, and time bounds. Check current grant status at the time of use. The application verifies exact issued tokens on completion and checks current rights again.
A generator submits its output SHA-256 and receives a signed completion receipt plus a custom assertion payload. Production software must bind that assertion to the media through a C2PA implementation. Merely supplying a manifest ID does not validate provenance.
Integration boundaries
- General model training is denied. New channels or providers require a new signed agreement.
- Usage reservations count generation and publication separately. Expired reservations are not automatically refunded.
- Derivatives within a campaign are supported. Cross-campaign compositions are rejected until all contributing grants can be evaluated together.
- Fingerprint and watermark recovery, automated royalties, independent audit checkpoints, and external provider enforcement are not connected.
- Agent credentials are provisioned by the operator. Automated OAuth delegation and signing-key rotation are deployment follow-ups.
Read the Bitpass extension contract or inspect the experimental agent card.