The live Indexer/Gateway OpenAPI specs expose a full account-recovery-delegation feature — POST /pending-recovery-agent, POST /recovery-agent (Indexer), POST /initiate-recovery-agent-update, POST /cancel-recovery-agent-update, POST /execute-recovery-agent-update, GET /health (Gateway) — confirmed live via curl against both specs. A companion PR wires these paths into docs.json's nav so Mintlify auto-generates the raw request/response reference pages, but that only documents the wire format, not the concept: what a Recovery Agent is, when/why an app would delegate recovery to one, the security model, and how it relates to the existing recover-account endpoint.
Needs: a conceptual overview page (likely under world-id/reference/ or world-id/concepts.mdx) explaining the Recovery Agent flow end-to-end, written with input from the protocol team since this touches account-recovery security semantics that shouldn't be guessed at from the OpenAPI schema alone.
The live Indexer/Gateway OpenAPI specs expose a full account-recovery-delegation feature —
POST /pending-recovery-agent,POST /recovery-agent(Indexer),POST /initiate-recovery-agent-update,POST /cancel-recovery-agent-update,POST /execute-recovery-agent-update,GET /health(Gateway) — confirmed live viacurlagainst both specs. A companion PR wires these paths intodocs.json's nav so Mintlify auto-generates the raw request/response reference pages, but that only documents the wire format, not the concept: what a Recovery Agent is, when/why an app would delegate recovery to one, the security model, and how it relates to the existingrecover-accountendpoint.Needs: a conceptual overview page (likely under
world-id/reference/orworld-id/concepts.mdx) explaining the Recovery Agent flow end-to-end, written with input from the protocol team since this touches account-recovery security semantics that shouldn't be guessed at from the OpenAPI schema alone.