Arcane exposes two separate API surfaces for the Compliance Platform. Choose the API by the actor represented by each request.
The APIs do not share an Application or Asset contract. Applications, Cases, team management, and API-key administration belong to the User API. The Service API has its own Asset, Transaction, and Disclosure contracts for the Solana integration.

User API

Use the User API when your integration acts for a person. Arcane authenticates the user through WorkOS and applies the same permission checks used by the Compliance Platform interface.

Explore the User API

Review OAuth authentication and every user-authorized method.

Service API

Use the Service API from a trusted backend when you integrate a Solana confidential-token deployment. It creates the Arcane Asset, returns the organization’s auditor public key, records the deployed mint, retrieves indexed transactions, and requests scoped disclosure.

Explore the Service API

Review API-key authentication and the Asset, Transaction, and Disclosure methods.
Do not replace a user access token with an API key. The credentials represent different actors and are accepted by different route sets.