Only the agent (API key) calls this. The server sets token_purpose in the response.
• If this agent does not yet have a pair+completed claim for the wallet, the agent must own the wallet; a pair code is issued for human claim/confirm.
• After that first pair is complete, the same agent can call again to mint/rotate a restore code (e.g. human may already be owner).
pair or pending restore row (per wallet+agent) and invalidates the previous code.Documentation Index
Fetch the complete documentation index at: https://cobo.com/products/agentic-wallet/manual/llms.txt
Use this file to discover all available pages before exploring further.
Request payload for Initiate wallet pairing (agent-only).
The server returns token_purpose=pair (before the first pair claim is completed) or
token_purpose=restore (after it is completed). Both variants live on the same
wallet_claims row set.
The ID of the wallet to pair.
Already exists (idempotent). Successful Response
Wallet pairing initiate response payload.
Pagination metadata for list responses.
Supports both legacy offset-based and cursor-based pagination.
Cursor fields (has_more, after, before) are populated for
cursor-paginated endpoints. Legacy fields (offset, limit) are
populated when the caller uses the deprecated offset parameter.