Changes to the Unirail API, SDK and dashboard, newest first
The v1 API and the dashboard went live, with the SDK available to early-access accounts.
New
POST /v1/route_decisions returns a routing decision from masked metadata, with no names or account numbers. Report how each payment went with POST /v1/outcomes. GET /v1/routing_snapshot returns what the decision engine reads, for running it in your own infrastructure by arrangement.
New
@unirail/executor runs the same provider adapters Unirail uses, inside your process, with credentials from your own vault.
The SDK packagesNew
maskAccount() turns a payto:// address into a fingerprint with your own HMAC key, for Decide mode requests.
What Decide mode sendsNew
Record provider contracts (fees, volume tiers, renewals) as versioned deals. Each routing decision is priced under them. The dashboard shows what switching provider would save.
Provider deal trackingNew
The provider catalogue now lists 33 capabilities across banking, verification, identity and compliance, with coverage by country and a source for each claim.
Browse capabilitiesNew
Link sessions, accounts, route quotes, payment intents, events and signed webhooks, with idempotency keys on every write.
The API referenceNew
Manage environments, API keys, Infisical secret sources, provider connections, a versioned routing policy, webhooks and events.
The API and the dashboard are live for early-access accounts. The SDK packages will go to npm at launch. Start in test mode with the developer quickstart, check the fields in the API reference or read the full schemas in the docs.