Guides & recipes.
This is a navigation hub, not new API content. It points at the how-to material that is live in these docs today, in the order most teams read it: a quick start, a builder hub, the shared sign-in flow, and the two SDK recipe pages. Everything here is Phase 0, testnet, pre-audit. Deeper step-by-step guides land through Phase 1.
Where things stand. The full 35-contract surface has been live on Base Sepolia since 2026·07·01 (34 of 35 source-verified on Basescan), pre-audit. A single external audit of the complete v1 system gates mainnet. There are no real users or volume yet, and these pages say so plainly. See the status board for the live picture.
The guides that exist today
Five pages carry the working how-to material. Read them roughly in this order.
| Guide | What you will do | Open |
|---|---|---|
| Quick start | Install @adunai/sdk from the protocol repo, point a client at Base Sepolia, and see the two integration patterns at a glance. | Quick start |
| Start building | Choose one of three paths into the substrate: SDK-only sign-in, the typed protocol SDK, or direct contract integration. | Start building |
| Sign in with Adunai | Follow the OAuth-shaped grant flow end to end, the one handshake both SDK surfaces share, and read the launch-set scope reference. | Sign in with Adunai |
@adunai/sdk recipes | Initialize the builder client, run signIn(), read attestations, route a payment, and issue attestations if you are an accredited attester. | @adunai/sdk |
@adunai/verify recipes | Verify a signed attestation locally against your own trust policy, with no on-chain writes and no keys to hold. | @adunai/verify |
Quick start
The entry point. It covers the honest Phase 0 install story: @adunai/sdk ships in the protocol repository under Apache-2.0 and is not on npm yet; npm publication lands with the Phase 1 public release. The client targets Base Sepolia, and there is no Adunai mainnet deployment. Begin at the Quick start.
Start building
The builder hub sorts you into a path by what you are: a relying party who verifies people, a builder who composes primitives, or a Solidity team integrating at the contract layer. It also states plainly what can change under you: every protocol upgrade runs an RFC with a 14-day comment window, Technical Advisory Council review, approval by 5 of 9 signers of the nine-signer multi-sig, then a 14-day timelock. Read Start building.
Sign in with Adunai
The grant flow is the shared handshake. A user reviews scopes in the reference identity client, aID, and approves or denies; the grant is recorded through SelectiveDisclosure; the receiving application reads only what was granted and verifies issuer signatures against its own trust policy. A note on consent nuance: benign identity-scoped attestations require the subject's EIP-712 consent, but regulatory and adverse records, such as sanctions or PEP status, are issued without consent by design. The full flow and scope table are in Sign in with Adunai.
The two SDK recipe pages
The recipe material lives on the two SDK pages. @adunai/sdk is the build pattern: init, sign-in, attestation reads, payments routing, and attester issuance. @adunai/verify is the integrate pattern for relying parties: the same sign-in, then local signature verification against a trust-policy file. The verify package is a planned Phase 1 release; today the same reads run against the live registries through @adunai/sdk. Note one live-surface detail for payments recipes: ProtocolConfig's five-token whitelist (USDC, USDT, EURC, cbBTC, WETH) is live, while PaymentsRouter routing ships dormant and arms through the 14-day timelock.
Recipes and the full surface
The recipe snippets you will use in Phase 0 live inside the two SDK pages above. For the surrounding surface, use these:
@adunai/sdkand@adunai/verify: the per-method recipes as they stand today.- Contract registry: all 35 contracts with addresses, responsibilities, and Basescan links, for teams reading or integrating at the contract layer.
- Identity & attestations, Reputation & trust, and Settlement & payments: the protocol concepts a recipe composes over.
- Whitepaper and Foundation Charter: the architecture and the authority boundaries a robust integration should respect.
A consolidated SDK reference (sdk-reference.html), covering every namespace and type, is a Phase 1 addition. Until it publishes, the two SDK pages are the reference for the methods that exist.
What expands in Phase 1
This set is the working minimum. The sidebar lists Guides & recipes, API reference, and FAQ as coming soon for a reason: the fuller step-by-step walkthroughs, the complete API surface, and additional recipes (KYC and employment compose, multi-attester verify, custodial versus self-custody, abandonment and reclaim) expand through Phase 1, alongside the audit and mainnet work. A public reference wallet design preview shows how a consumer wallet composes these primitives; it is a design preview, not a shipped implementation, and the reference wallet itself is held open for Phase 1 and later.
Architectural readiness is not operational maturity. Every guide here describes a testnet surface built to be audited, not a launched network. When a capability is future, these pages label its phase. For anything else, adunai.org; for vulnerabilities, [email protected].