Core concepts

SDP exposes two interfaces that operate over the same backend and enforce the same grants, wallet scopes, and audit trails:

• Dashboard — browser-based UI for setup, token management, and compliance operations. Sign in with email, Google, or GitHub.
• REST API: programmatic access for backend integrations. Routes authenticate with an API key in the Authorization header.

Everything the dashboard does is available through the API. Build against the API for automation and integrations; use the dashboard to set up your organization, inspect state, and perform one-off operations.

EnvironmentsCopy Anchor Link

Authenticated environments are a property of the project, not of individual requests. Every tenant resource and API key belongs to a project and inherits that project's environment.

A key's format does not name its environment: the project it belongs to does.

Both environments expose the same route shapes. Develop and test authenticated integrations against a sandbox project, then switch to production by swapping your API key.

Go to mainnet covers requesting access and setting up your production wallets and API key.

Response conventionsCopy Anchor Link

Every successful response wraps its payload in a data envelope with request metadata:

{
  "data": { ... },
  "meta": { "requestId": "req_...", "timestamp": "2026-07-31T12:00:00.000Z" }
}

Errors return a machine-readable code alongside a human-readable message:

{
  "error": { "code": "INVALID_API_KEY", "message": "Invalid API key" }
}

Include the requestId when reporting an issue — it links your request to our internal traces and audit records.

Execution modelCopy Anchor Link

SDP executes custody operations by building, signing, and submitting with the configured custody wallet.

Read nextCopy Anchor Link

• Authentication covers project keys and access checks.
• API keys covers grants and wallet scope.
• Idempotency covers safe retries.
• API conventions covers errors, pagination, limits, and versioning.