Primitives, not platforms.
Typed, idempotent APIs for moving money. Every call is safe to retry, and every response ties back to a ledger entry you can audit.
curl https://api.aureus.com/v1/transfers \
-H "Authorization: Bearer sk_live_••••" \
-H "Idempotency-Key: a1f9c2e0-8d31-4b7a" \
-H "Content-Type: application/json" \
-d '{
"from": "acct_8842",
"to": "acct_5190",
"amount": 4825000,
"currency": "USD",
"rail": "fedwire"
}'From install to settled transfer.
Three steps from an empty terminal to money on the ledger. No bespoke onboarding, no waiting on a sales call to read the docs.
- 01
Install
Add the SDK for your language. One dependency, typed end to end, no codegen step to run.
- 02
Authenticate
Mint a secret key in the dashboard. Sandbox keys are free and isolated; live keys move real value.
- 03
Move money
Send your first transfer with an idempotency key. The response ties straight back to a ledger entry.
npm i @aureus/node
# or: pnpm add @aureus/nodeA client for the way you build.
Hand-tuned libraries, generated from the same OpenAPI spec the API is built on. Typed, idempotent, and versioned in lockstep with the platform.
Python
pip install aureusSync and async clients, full type hints, and Pydantic models throughout.
DocsGo
go get github.com/aureus/aureus-goContext-aware, zero-dependency, with generated types for every resource.
DocsCLI
brew install aureus/tap/aureusInspect accounts, replay webhooks, and tail the ledger from your terminal.
DocsOperational, and observably so.
A live view of the systems your integration depends on. Subscribe for incident notices, or poll the status API as part of your own checks.
- APIOperational
- LedgerOperational
- WebhooksOperational
- DashboardOperational
One spec, every client.
The API is described in OpenAPI 3.1 — the same spec our SDKs are generated from and the one you can generate your own clients against. Idempotency, pagination, and errors behave the same on every endpoint.
{
"id": "txn_9F2aR8KQ",
"object": "transfer",
"status": "posted",
"amount": 4825000,
"currency": "USD",
"rail": "fedwire",
"ledger_entry": "le_3KQ2aR9F",
"created": "2026-05-12T14:22:08Z"
}Shipped, and dated.
A running record of what changed and when. Breaking changes are versioned and announced ahead of time — never sprung on a live integration.
FedNow corridors live
Instant settlement on FedNow across all US operating accounts, posted to the ledger on clear.
Go SDK 2.0
Context-aware clients, generics-based pagination, and typed errors for every endpoint.
Stablecoin payouts on Base
USDC settlement on Base, with fiat-in and on-chain-out captured in a single balanced entry.
Webhook replay
Replay any delivered event from the dashboard or CLI, with signatures preserved for verification.
The details developers ask about first.
Every request carries a secret key as a bearer token. Keys are scoped to an environment — sandbox or live — and to a set of permissions. Rotate keys at any time from the dashboard; revoked keys stop working immediately.
Every money-moving call accepts an Idempotency-Key header. Replay the same key and you get the original response back, never a duplicate transfer. Keys are retained for 24 hours, which makes safe retries the default rather than an afterthought.
Yes. Sandbox keys run against a full simulation of the ledger and every rail — free, isolated, and seeded with test accounts. Simulate settlement, failures, and returns before a single live key is minted.
Each event is signed with a per-endpoint secret and delivered with a timestamp. Verify the signature with the SDK helper to confirm origin and guard against replay. Failed deliveries retry with backoff, and any event can be replayed by hand.
Build on the standard.
Read the docs, mint a sandbox key, and move your first dollar on the ledger today.