Human likeness. Explicit permission.

Your identity.
Your say.

Give AI permission to use your likeness. Choose who, where, and for how long—and follow the work through every version.

Consent starts with a person.
Every campaign needs signed terms. A listing never grants permission.

01 / A DIFFERENT KIND OF PASSPORT

Permission doesn’t
end at generation.

An AI commercial becomes a cutdown, a social edit, a new placement. Each version needs a clear connection to the person who said yes.

callmyagent brings agreements, scoped permissions, output records, and expiry into one workspace. Bitpass connects the rights across that lifecycle.

Follow the permission lifecycle →
01 / AGREE

A specific yes.

Approve the brand, depiction, provider, channels, territories, duration, and fee. Both parties sign the same terms.

02 / AUTHORIZE

Every use has limits.

Check generation and publication against the active grant. Out-of-scope requests need a new approval.

03 / FOLLOW

Keep the history.

Register each output under a stable lineage. Track its parents, permission record, and reported uses.

FOR CREATORS

Your likeness.
Your boundaries.

  • 1
    Review exact terms

    Know what you’re authorizing before you sign.

  • 2
    See the record

    Follow permissions and registered outputs in your workspace.

  • 3
    Control future use

    Expiry and revocation stop new permissions at connected gates.

Apply as a creator ↗
FOR BRANDS & PRODUCTION TEAMS

Create with
a clear mandate.

  • 1
    Request the right scope

    Agree on the campaign before production begins.

  • 2
    Check permission

    Receive a signed, time-limited decision for an approved use.

  • 3
    Connect the output

    Register the asset and carry its authorization reference forward.

Tell us your idea ↗
THE IMPORTANT BOUNDARY

A record of consent.
Not a claim of control.

Connected production systems can check and enforce permissions. Unconnected platforms can still copy or alter media.

Revocation changes future authorization. It does not erase distributed files. C2PA provenance validation and content recovery require production integrations.

See integration capabilities →
TRY THE WHOLE LIFECYCLE

From a yes.
To every version.