No lab can negotiate the long tail bilaterally. The registry aggregates it into licensed supply under one agreement, and every lookup returns a signed receipt you keep. The contract framework, the reporting API, and the settlement rails are being designed with early counterparties; the ask on this page is participation, not a purchase.
Start the conversationAlltio is not a content seller, a toll booth, or a competing lab. It is the neutral clearing layer both sides of a licensing transaction can trust as the bookkeeper of record. Two of these four are true today; two are what the pre-seed builds.
The registry serves written work today — documents, reports, specifications — with image, video, motion capture, and sensor data joining as re-encoding-proof fingerprints ship. Depth is being seeded through aggregators — stock agencies, specialist catalogs, guilds and collecting societies — because one agreement brings in a catalog rather than a file. One parametrized contract is designed to reach the whole of it: the long tail no lab can assemble bilaterally.
Flat, tiered, capped, usage-based, or dynamic — the contract framework is parametrized for all of them, and the signed reporting API and settlement engine are what make the usage-based variants runnable at all. Both are in build; dynamic pricing is where bespoke paper fails hardest.
Article 53 of the EU AI Act has been enforceable since 2 August 2026: providers of general-purpose AI must document their training content and operate a copyright-compliance policy, with penalties to €15M or 3% of global turnover. Signed usage records and settlement history are designed to produce that documentation as a byproduct of normal operation rather than a reconstruction exercise. A lookup returns a signed answer, including when the answer is that a work is not registered — evidence that the check was made. The lookup returning a signed diligence receipt is specified — the spec is public and in draft, and we would rather argue about it with you now than after it ships.
Read the draft Lookup API spec →Alltio operates no model, no answer engine, and no competing platform. Both sides of every transaction can trust the record because the record-keeper competes with neither. This one is structural — it is true on day one and it is the seat a conflicted incumbent cannot take.
Training happens occasionally; inference happens continuously. Settlement, when it ships, is designed to consume usage signals at the confidence level your architecture supports — from deterministic to pooled — rather than waiting on attribution science that does not exist. We promise no detection we cannot ship.
Your pipeline already logs which licensed items entered the context window. Those logs support deterministic per-retrieval payouts — the highest-confidence tier, and one that needs no new science, only the rail to settle on.
For training and bulk use: report consumption under contract, cryptographically signed. Attribution by attestation — no model internals shared, no detection science required.
Collective licensing splits pro-rata by corpus share, quality tier, and recency — the model music and broadcast have run on for a century.
Agents presenting verifiable credentials against registry policy — authorization, provenance, and settlement bound into one protocol, so autonomous purchasing has a paper trail.
You can evaluate the registry's depth yourself, so we would rather state the position than have you discover it.
An open registry of fingerprinted works with countersigned, timestamped records; a public draft of the lookup API and site-declaration format; a contract framework and settlement design built with early counterparties. Neutrality and registry integrity are live properties, not roadmap items.
A populated corpus at the scale that would make one contract compelling on volume alone, or a settlement rail with cleared transactions behind it. Depth is being seeded through aggregators. If you need licensed supply at scale this quarter, we are not that yet — and we will tell you so on the call.
You should not have to take our word for the state of the API. There is no key to request, no sandbox to be provisioned into, and no sales call in front of it. These endpoints are public and unauthenticated today. Paste them into a terminal.
GET https://alltio.com/api/health
Liveness and API version. Returns {"ok":true,"service":"alltio-registry-api","version":"v1.1"}.
GET https://alltio.com/api/verify/{recordId}
Verification of a registry record by its ID: the work, the rights holder, the declared terms, the timestamp, and whether Alltio’s countersignature validates. A malformed ID returns 400 and an unknown one returns 404. Both are answers you can log.
GET https://alltio.com/api/diagnose?domain={domain}
What a domain’s robots.txt and rights files say: which named AI crawlers may read it, and whether any machine-readable reservation is published. This is what powers the check on our home page.
GET https://alltio.com/r/{recordId}
The same record as a citable web page, for takedowns, contracts, and footnotes.
Fingerprint lookup. Resolving a SHA-256 straight to a record, the call your ingestion pipeline actually wants, is specified and not yet shipped. Today you can verify a record you have been given an ID for. You cannot yet hand us a hash and ask who owns it. We would rather you learn that here than from a 404. Read the draft spec and argue with it →
Signed diligence receipts, API keys, and rate tiers. The signed-answer design described above is exactly that: a design. No key system exists today, which is why lookup needs no key, and why we cannot yet promise you a rate limit in writing.
Registration itself is POST /api/register, and it is what the form on /register calls. Content never reaches it: the browser computes the SHA-256 locally and posts the fingerprint, never the file.
We are building the contract framework, reporting API, and settlement rails with a small set of early counterparties across publishing, robotics training data, and medical AI. Early counterparties set the terms the standard inherits — that is the argument for talking now rather than when it is finished. If your licensing roadmap needs infrastructure rather than another negotiation, talk to us.
Become an anchor partner