For AI builders
Check the rights before you use the content.
In the EU, respecting a rights reservation is a duty, and showing that you checked is up to you. Query Amlet before you train, retrieve or ground, and keep the answer for every work you touch.
One lookup instead
of a thousand emails.
Rights holders file their declarations once, in one format, in one registry. You query it the same way for every work, whoever published it.
- 01
One registry
Declarations from publishers and aggregators sit side by side, in one machine-readable shape.
- 02
Matches on content
The ISCC is computed from the work itself. A converted or re-uploaded copy with stripped metadata still finds its declaration.
- 03
Fits your stack
A REST API, and an MCP server for agents. Both are documented at amlet.ai/docs.
- 04
A record of what you checked
Every declaration is signed and timestamped. Keep the responses and you can show what you checked, and when.
Technical integration
What the API gives you
If a rights holder is open to licensing, the record tells you who to contact. The deal itself is between you and them. Full documentation is at amlet.ai/docs.
- Look up by ISCC, ISBN, file or text passage
- TDM status for each use on every response
- Similarity search over ISCC fingerprints
- The rights holder named on every record
- An MCP server for agents
- REST endpoints, documented in full
Ask the registry
before you train.
Add Amlet to your AI platform over MCP, or start with the REST docs.