Getting started

Setup is dashboard-first. Everything after is API-first.

1. Sign up + create an org

Sign up at orchestration.seismic.systems with email + password and enroll MFA, then create an org. The signup user becomes the org's owner. See Authentication for the full flow.

2. Submit KYB

Fill out the KYB profile for your org in the dashboard. Quoting and end-user onboarding unlock once the org is approved. API keys can be minted before approval. They just won't authorize gated endpoints yet.

Full walkthrough: Onboarding your organization. The same surface is API-callable under /orgs once you have a key.

3. Mint an API key

Settings → API keys → New key in the dashboard. Label it (e.g. ci-pipeline) and copy the secret. It's shown once. The environment is implicit: the dashboard you're logged into determines whether you get a sandbox or production key, not a selector at mint time.

For programmatic minting see POST /auth/api-keys.

4. Install the client

Single runtime dependency (zod). Runs in browsers, Node ≥ 18, Bun, Deno, and service workers.

5. Pick a base URL

All API endpoints live under /api/v0/* (Bridge-compat at /api/compat/bridge/v0/*).

6. Create a client + make a call

Pass your API key to an environment factory. baseUrl and the Api-Key: header are wired automatically.

import { SeismicOrchestrationClient } from "seismic-orchestration";
 
const api = SeismicOrchestrationClient.sandbox({
  apiKey: process.env.SEISMIC_ORCHESTRATION_API_KEY!,
});
 
const me = await api.auth.me();
console.log(
  me.email,
  me.memberships.map((m) => m.org_name),
);

Next

• Onboarding your end users: per-user customer rows, KYC, attached payout accounts.
• Requesting quotes: create / accept flow.
• SeismicOrchestrationClient: full SDK surface.

Access-token auth

For dashboard frontends authenticating as the logged-in user, skip apiKey and configure a tokenStore instead. See Authentication.