Follow current account relationships.
Owner, Finance, Operations and Security can inspect current users and workspaces using a separate admin session with current verification by the exact active passkey. App cookies, merchant API keys and Support access cannot authorize these directory routes.
01Find a user
GET /v1/admin/directory/users accepts exact id, email, workspaceId, platformRole, after and limit. Email is normalized to lowercase. Workspace matching includes recorded owners and current members. Each record includes current name, operator role, membership/ownership counts and aggregate active app session/passkey counts. Tokens, hashes, credential IDs, public keys and signing references are excluded.
02Find a workspace
GET /v1/admin/directory/workspaces accepts exact id, ownerId, memberId, after and limit. Owner filtering uses the recorded workspace owner. Member filtering uses an actual current membership. Wallet counts include every request lifecycle stage and environment; they are not balances, proof of custody or receiving-readiness assertions.
03Continue a live directory
Pages default to 50 records and allow at most 100. Results use ascending record UUID, not registration chronology. Send nextCursor as after with the original filters. Cursors bind the directory area and normalized filters; start again after changing either. Refresh to see later changes. The admin UI retains at most 500 headers before requesting narrower filters.
04Inspect relationships
GET /v1/admin/directory/users/{id} includes up to 100 owned or joined workspaces, with explicit truncation. Ownership is distinct from membership role. GET /v1/admin/directory/workspaces/{id} includes up to 100 current members and wallet lifecycle counts by environment/network/state. A recorded owner without a matching owner membership is flagged for investigation. Use the paginated list filters to inspect larger groups.
05Keep inspection separate from authority
Directory data and account-access counts are current metadata. They do not establish a financial approval, an active custody source, verified identity or solvency. Operator access changes retain their existing separate review workflow. The directory has no role, membership, balance, credential or session override route. Recovery quarantine and Cache-Control: private, no-store apply.
// Current verified operator admin session required.
GET /v1/admin/directory/users?email=merchant%40example.com
GET /v1/admin/directory/users?workspaceId={workspaceId}&limit=50
GET /v1/admin/directory/users?workspaceId={workspaceId}&after={nextCursor}
GET /v1/admin/directory/users/{userId}
GET /v1/admin/directory/workspaces?ownerId={userId}
GET /v1/admin/directory/workspaces?memberId={userId}
GET /v1/admin/directory/workspaces/{workspaceId}
// Current relationships and lifecycle counts, not financial authority.Open your workspace