THESIS: Stripe-referenced financial operations with Nexus-owned evidence. OWN-WORLD: system UI, white canvas, purple actions, 14px controls, thin separators. STORY: inspect balances and usage, filter records, review payment and refund evidence. FIRST VIEWPORT: 224px navigation, compact toolbar, real usage trend and role tasks, then period comparisons and editable business metrics. FORM: user-pinned Stripe Dashboard; signature interaction: authenticated date filtering and persisted widget editing. FINISH: unreviewed and undocumented is unfinished; this build ends with the finish review, the verdict, DESIGN.md, and every shipping raster carrying its provenance.THESIS: Stripe-referenced authenticated record workspaces. OWN-WORLD: system UI, white canvas, purple actions, compact 14px controls and thin separators. STORY: inspect records, open stable facts, edit through permission-aware forms, then read technical evidence. FIRST VIEWPORT: compact title and task actions, factual registry or labeled editor; horizontal settings navigation and light Workbench inspector. FORM: user-pinned Stripe Dashboard, no alternate concept roll; signature interaction: record filters, detail tabs, collapsible evidence and the persistent Workbench drawer. FINISH: independent material review, route coverage and scoped design documentation.Dark cinematic four-chapter scroll narrative with one persistent particle field morphing from Nexus core to control boundary, metering stream, and balanced settlement ledgers. Wide restrained typography, teal and frost particles, sparse amber evidence, semantic fallback, reduced-motion support.
Turn an invocation into a recoverable, settlement-ready business outcome.
A business record establishes the idempotency boundary; the gateway handles reservation, model routing, and usage reporting. Applications decide only by stable code 和 retryable signals.
REST address
https://nexus-api.rainlib.com
Authentication
Bearer API Key
Idempotency
X-Nexus-Operation-Key
Tracing
W3C traceparent
01 / Smallest runnable call
Use a published capability route first, then fix the business transaction.
Do not send an upstream provider key; Nexus resolves the model alias, offer, token cap, and pricing snapshot.
1AuthenticateThe API key determines the customer and scope.
2ReserveReserve the maximum risk amount.
3ExecuteRoute to a published provider.
4SettleSubmit usage and refund the difference.
Current public REST endpointhttps://nexus-api.rainlib.com