Integrate a service
Put a rights check inside your service.
Check rights before you generate, apply the contracted policy on every turn, and record what was allowed and what was blocked. Connect over REST, OpenAPI or MCP.
What you get
Whether this person is registered and which rights may be used under which terms.
POST /api/v1/rights/checkAddress style, relationship boundaries, knowledge cut-off, prohibited areas, safe lines. Versioned, with a webhook on change.
GET /api/v1/persona-licenses/{code}/policyContracted face and voice files via 10-minute signed URLs. Empty once the contract ends.
GET /api/v1/licenses/{code}/assetsSend allowed and blocked generations alike. Replays are never stored twice.
POST /api/v1/usageYour users register with Rightis without leaving your product. Rightis keeps the consent record.
POST /api/v1/rights-holdersLicense activation, expiry, revocation and settlement changes arrive as signed webhooks.
license.* settlement.* persona_policy.updatedStraight from AI agents
The same API as tools. Claude, ChatGPT, Gemini and any MCP-capable agent just need to be registered.
Streamable HTTP. Pass the API key as a Bearer header and the key's scopes decide which tools open.
https://rightis.org/api/mcpRead as-is by custom GPT Actions, Gemini extensions and code generators.
https://rightis.org/api/v1/openapi.jsonHMAC-SHA256 signature, per-event idempotency key, back-off retries.
X-BR-Signature: t=<unix>,v1=<hmac>How to start
- 01Get a key
One email. Start on a sandbox key; the production key comes with the contract.
- 02Read policy and assets
Fetch the policy and approved assets by license code and wire them into your generation pipeline.
- 03Send usage
One event per generation. Settlement and audit follow from that.