# Seismic Orchestration > On/off-ramp, wallet, and stablecoin swap orchestration behind a single REST API. Shipped as seismic-orchestration on npm. ## Docs - [Authentication](/docs/authentication.md): Seismic Orchestration accepts **two** auth schemes, mutually exclusive on a single request: - [Getting started](/docs/getting-started.md): Seismic Orchestration is dashboard-first for setup, API-first for everything else. You'll spend a few minutes in the dashboard once — signing up, getting your business KYB-checked, and minting an API key — then drop the key into the TypeScript SDK (or any HTTP client) and you're moving money. - [SDKs](/docs/sdk/overview.md): Every SDK wraps the same REST surface documented under [API Reference](/api/auth) — shared naming (`SeismicOrchestrationClient`), method shapes, and error codes. - [TypeScript SDK](/docs/sdk/typescript/overview.md): **`seismic-orchestration`** is the official TypeScript client for the Seismic Orchestration REST API. It's the same code our own frontend runs — every feature documented here is dogfooded. - [Token stores](/docs/sdk/typescript/token-stores.md): The `tokenStore` config field decides where the client keeps tokens. Three shapes are accepted: - [Accepting a quote](/docs/guides/accepting-a-quote.md): Once you have an `AsyncQuoteSnapshot` with `status === "ready"`, accept it to kick off an order. The server re-validates the chosen leg, creates a `ramp_orders` row, and dispatches settlement for that rail path. - [Onboarding your end users](/docs/guides/end-user-onboarding.md): Use this when **your product** onboards individual end users — a fintech app onboarding a consumer, a payroll product onboarding a contractor — and you need a per-user `customer` row so we can move funds on their behalf. - [Requesting quotes](/docs/guides/first-quote.md): In Seismic Orchestration, a quote snapshot is a **ranked comparison** across every **priced rail leg** for a given (source → destination, amount) trade — each row is identified by `in.rail` / `out.rail` plus a unique `id`. You get back a snapshot id, a list of quotes, and a pre-computed `best_quote_id`. Accept to turn a quote into an order. - [Onboarding your business](/docs/guides/onboarding-business.md): Before you can call the Seismic Orchestration API for live money movement, we need to verify your business once. This guide walks the **dashboard-first** flow: log in to [dashboard.seismic.systems](https://dashboard.seismic.systems), submit one unified KYB form, and we handle verification behind the scenes. - [Bridge compatibility](/docs/bridge-compat/intro.md): Already built on Bridge? For the endpoints we implement, paths, field names, auth header, error envelope, and pagination all follow Bridge's conventions — the goal is that a base-URL swap gets most integrations that we support too running without code changes. This is best-effort, not a contract: if you hit an inconsistency that isn't already called out, or want an endpoint we haven't implemented, [open an issue](https://github.com/SeismicSystems/orchestration/issues) and we'll take a look. - [Not implemented](/docs/bridge-compat/not-implemented.md): Every Bridge endpoint below returns **`501 not_implemented`** when hit on `/api/compat/bridge/v0`. The response body mirrors Bridge's generic error envelope: - [Transfers](/docs/bridge-compat/transfers.md): Bridge's `/transfers` resource. The single most load-bearing endpoint — this is where onramps, offramps, and wallet-to-wallet transfers all live. - [Shared schemas](/docs/bridge-compat/schemas.md): Shapes that appear in more than one Bridge-compat endpoint live here. Each type has its own page so you can deep-link to a specific schema from your integration notes. - [KYC Links](/docs/bridge-compat/kyc-links.md): Bridge's `/kyc_links` resource. One call creates a hosted KYC flow **and** the stub customer behind it — use this when you want the customer to do the typing. - [External Accounts](/docs/bridge-compat/external-accounts.md): Bridge's `/external_accounts` resource. Destinations a customer can receive payouts into, or fund transfers from. - [Exchange Rates](/docs/bridge-compat/exchange-rates.md): Bridge's `/exchange_rates` endpoint. Indicative quotes — the realized rate on a transfer depends on the provider, rail, and size. - [Customers](/docs/bridge-compat/customers.md): Bridge's `/customers` resource. Two customer types share one endpoint, discriminated by `type`: - [TOS Links](/docs/bridge-compat/customers/tos-links.md): Three endpoints related to the hosted Terms of Service flow. All three return a TOS acceptance URL; the differences are *when* you call them and what you get back. - [Associated Persons](/docs/bridge-compat/associated-persons.md): Bridge's `/associated_persons` resource. Beneficial owners, controllers, signers, and directors attached to a business customer. - [Errors](/docs/api/errors.md): Every non-2xx response uses the same JSON envelope: - [API Reference](/docs/api.md): The native Seismic Orchestration API. All endpoints live under `/api/v0/*` — paths in the per-endpoint pages drop the `/v0/` prefix for readability. Curl snippets throughout assume `$SEISMIC_ORCHESTRATION_URL` and `$SEISMIC_ORCHESTRATION_API_KEY`. - [Users](/docs/api/users.md): The user behind the credential is the user who logged in (token auth) or the user who minted the API key. Both endpoints scope to that user. - [Quotes](/docs/api/quotes.md): All endpoints require auth — either an `Api-Key: ` (org-scoped, recommended) or `Authorization: Bearer ` (dashboard session). Curl snippets assume `$SEISMIC_ORCHESTRATION_URL` and `$SEISMIC_ORCHESTRATION_API_KEY` — see [Auth](/api/auth) for the convention. - [Orgs](/docs/api/orgs.md): An **org** is the tenant. Customers, API keys, KYB submissions, quotes, and orders all hang off an org. A user can belong to one or more orgs; the common case is one. Multi-org users get a "Switch org" UI on the dashboard; multi-org API callers mint a separate key per org. - [Members](/docs/api/orgs/members.md): Endpoints for managing user ↔ org memberships. All scoped to the current org. - [KYB](/docs/api/orgs/kyb.md): KYB ("Know Your Business") is how we verify your org before live money movement. We collect a **unified superset** of fields once — aligned with **the platform's requirements** — then run the verification and hosted flows the corridor needs. - [Customers](/docs/api/customers.md): These are **end-user customers** — individuals (or businesses) that *your product* onboards on top of Seismic Orchestration. They're scoped to your org. They are not the same thing as your org's own KYB onboarding — that's covered by [Orgs → KYB profile](/api/orgs). - [Auth](/docs/api/auth.md): All endpoints live under `/auth`. Request + response bodies are JSON. - [API keys](/docs/api/auth/api-keys.md): API keys are org-scoped credentials for server-to-server callers. One key, one org — to access multiple orgs from automation, mint a separate key for each. Revoking a key invalidates it immediately for all in-flight requests; existing access tokens are unaffected (different auth path). - [Accounts](/docs/api/accounts.md): These endpoints expose the accounts your end-user customers have attached — bank accounts, IBANs, UPI VPAs, and on-chain wallets. **Account creation lives under the customer that owns it** at [`POST /customers/:id/accounts`](/api/customers/create-account); the read-side endpoints live here so accounts can be addressed globally by their UUID.