Getting started with AIDID

Five journeys, generated from a single source (data/guide.json) so the human pages and the machine-readable twin at /start/index.json can never disagree. Every step carries the same status vocabulary as status.json, so a tutorial can never be more optimistic than the status document.

Read this first: what works today, and what does not

Working today: reading the machine-readable contracts, writing and self-testing an RP-side integration, running the fully offline end-to-end demo, and backing up or restoring a local identity. NOT available today: creating a DID (there is no end-user way to obtain the MSG it needs), any chain write, and production login. Nothing on these pages is a sign-up that works end to end today.

Five journeys

Updated: 2026-10-13

Get a DID

Not available today

A DID is a did:msg identity registered on MSGChain. Creating one needs MSG to pay the chain fee, and there is no end-user way to obtain MSG yet, so read this as a specification walkthrough rather than a working sign-up.

Open this journey

Delegate a sub-DID (parent to child)

Offline-testable today

A parent DID can authorise a restricted-scope sub-DID for a purpose, a resource set and a validity period, and bind an AI agent to it. You can rehearse the whole flow offline today; on-chain binding, revocation and quota need stage B and the window parameters.

Open this journey

Integrate AIDID login into your site

Offline-testable today

Write and self-test the RP-side integration today, entirely offline: read the wire contract, install the SDK, build a request, verify a response, and run the offline end-to-end demo. Production login is blocked until the chain-side resolve endpoint is authorised.

Open this journey

Use DID login for payments (payout address)

Offline-testable today

After a verified login you can resolve the DID on your server and read the payout address from the canonical record. You can write and self-test that logic offline today; reading a real address in production is blocked with the rest of production login. pay:address is a declaration the user sees and approves, not a permission.

Open this journey

Back up and restore your local identity

Works today

Backup and restore work today and are entirely local: the payload is encrypted with a passphrase that never leaves your device. There is no server-side recovery, so the backup and its passphrase are the only way to move an identity to another device.

Open this journey

How to read the badges

  • Works todayWorks today.
  • Offline-testable todayYou can write and self-test it today, but it cannot run in production yet.
  • Not available todayNot available today; the reason box quotes status.json.

Machine-readable twin

The same five journeys as JSON (English and Chinese text, per-step status), for agents, crawlers and build tooling.

/start/index.json