Public Wallets and Identity

These public routes support wallet clients and identity verification. Use the client’s registered configuration; keep server API keys out of these calls.

​

What you can query

Wallet lookup and status take clientId, swigId, and network. Supply a registered client ID, the base58 Swig ID, and NETWORK_MAINNET or NETWORK_DEVNET. The lookup carries these fields in its JSON body; status uses query parameters. A Swig ID is different from the config address used by the authenticated wallet reads.

​

Quota

• Public wallet lookup and status do not consume the API-request or DEX-query counters described in the overview.
• Identity key reads without an application-specific x-client-id are not attributed to an organization’s allowance. An IdP request carrying a valid registered x-client-id consumes one API request for that organization.
• These routes do not use the DEX-query quota. Their public access does not promise unlimited request rates or waive client validation.

​

Reference and integration guides

• Wallet client boundary
• Identity routes and token verification
• IdP integration for the login and session flow