Integration Registry

Sites that integrate AIDID sign-in. The directory is read live from a first-party cache when this page loads, and falls back to the snapshot shipped with this build when that read fails — the label next to the dates says which one you are looking at.

Data as of: 2026-10-12Source: repo+public-repochecking…

There is no fixed refresh schedule: registrations are merged automatically into the public repository, and this page reads a cache refreshed on demand (a read more than 10 minutes old triggers a refresh, rate-limited to once every 10 minutes). A merge therefore normally shows up on your next visit or two, and a quiet period can make the first visit show something older than 10 minutes. Everything stays static and offline-capable: if the read fails, this page shows the snapshot built into this deployment.

Directory

AIDID

https://aidid.im

Domain verifiedOfficialFirst-party
DID
not published
Registered
2026-10-09
  • login
https://aidid.im

AIDID (Cloudflare Pages alternate origin)

https://aidid.pages.dev

Domain verifiedFirst-party
DID
not published
Registered
2026-10-12
  • login
https://aidid.im

Being listed only means the site proved it controls its own domain and declares that it integrates AIDID. It is not a security or reputation endorsement by AIDID.

Being listed is not the whole picture: a site can integrate AIDID without registering here, and not being listed is not a warning.

Sites I've signed in to

Stored only in this browser. Never uploaded, never shared — cleared whenever you want.

Nothing yet. When you approve a sign-in request on /authorize, the requesting site shows up here, locally.

Register your site

Three steps. No account, no API key, and no server of ours is involved — the check is a file on your own domain.

  1. 1. Generate a challenge

    Any unguessable string works as long as you publish exactly the same value. Generate one here so it stays unique.

  2. 2. Publish it on your domain

    Serve the file below over HTTPS. It proves you control this origin; nothing else about your site is touched.

    https://your-domain.example/.well-known/aidid-rp.txt

  3. 3. Open a pull request

    Add the entry below to rp-registry.json in the public registry repository. A GitHub Action fetches your /.well-known/aidid-rp.txt and compares it with the registered challenge; when a pull request changes only that file and the challenge matches, it is merged automatically — pull requests opened from your own fork included, with no invitation or collaborator access needed.

    Open the public registry repository

    Registration is not integration

    Getting listed here proves only that you control this origin and declare the AIDID integration. It does not make AIDID login work: you still have to write and self-test the RP-side flow yourself, and production login stays blocked until the chain-side resolve endpoint is authorised.

    Open the integration tutorial

A did:msg identifier is recommended now and mandatory from phase 1, when registration moves on-chain and is signed by your own DID.

The on-chain registry is not available yet. Phase 1 registration fee: 0.01 MSG per registration — the same price as the authorization service fee, adjustable by contract upgrade. Until then, this pull-request channel is free and explicitly transitional.

Phase 1 will read the registry from the chain at build time instead of from this repository, so the snapshot stops depending on us merging a pull request.