For publishers

A record of your opt-out intent that predates any training cutoff.

Cryptographically signed. Timestamped by Arweave. Independently verifiable forever. No new infrastructure on your end — domain control proves itself through DNS.

Request a publisher account →

The problem

Without the registry, how do you prove later that you opted out before a given training cutoff? robots.txt has no cryptographic timestamp and is silently mutable. ai.txt has the same weakness. Emails to labs@ get lost. Internal records you generated yourself are records a defendant can question. You need an artifact that’s clearly dated, clearly authored by you, and verifiable by a third party who doesn’t trust either side.

What you get

01

An Arweave-anchored record

Public transaction ID. Cryptographically signed by us against your declared intent. Timestamped by Arweave block inclusion, not by our clock.

02

A public verify URL you can cite

Include it in legal correspondence, compliance filings, licensing negotiations. Any third party can verify the record against the public Arweave network without our involvement.

03

A status endpoint, then a webhook

Poll the registry to confirm your record landed. When the webhook ships, you’ll be notified at submission, at Merkle batch anchoring, and on any future state change.

04

A copy-paste deploy kit

Once your domain is verified, the registry generates your in-band signals: a robots.txt Content-Signal block, TDMRep and ADP well-known files, and a permanent _adp DNS record — each pointing back at your anchored record, in channels crawlers already parse. Deploying them is copy-paste; a per-host checklist covers your subdomains.

05

Signal Watch

The registry monitors your deployed signals and emails you when one drifts — a stripped robots line, a deleted file, a removed DNS record. Your anchored record proves the reservation predated the stripping. Nobody can quietly turn your “no” into silence.

How to register

  1. 01

    Email publishers@akaeon.com for a publisher account.

    v1 is manual approval; self-service is a v1.1 target.

  2. 02

    Submit an opt-out via POST /v1/optouts

    With your domain, your policy, and your scope.

  3. 03

    Publish the DNS challenge.

    A TXT record at _akaeon-registry-challenge.<your-domain>. The registry verifies the record across multiple resolvers and signs your opt-out into a Merkle batch anchored to Arweave.

  4. 04

    Deploy your in-band signals.

    Once verified, your status response includes a deploy kit: copy-paste artifacts for robots.txt, /.well-known/, and a permanent _adp TXT record that make the reservation discoverable at scrape time. Signal Watch then monitors them for drift.

What we ask in return

Nothing financially. v1 is free for publishers. We ask that you submit accurate opt-outs via a domain you actually control, expressing intent you actually hold. We ask that you understand opt-outs are public by design. The whole point is that any lab, any court, any auditor can verify the record without going through us.

Email publishers@akaeon.com →