Skip to main content
Request a demo
Developers

Read the contracts before you trust them.

What the chain enforces, how events are guaranteed, and where the API surface is a design rather than an endpoint. Each page says which it is.

The developer surface, built and unbuiltIdempotency keys, tenant-scoped clients and the outbox relay exist. The HTTP routes, the API client credentials and outbound webhooks do not, and are drawn as absent components.Your serviceHTTP routesAuth, versioning, rate limitsNot builtThe servicesIdempotency, tenant scoping,authorization, auditBuilt and testedOutboxEvents, in the sametransactionWebhooksNot built — needs SSRF egress controlThe dashed boxes are the honest half of this drawing.Everything a route would need is in place. What is missing is the route — and outboundwebhooks mean HTTP requests to tenant-supplied URLs from inside the network.
DocumentationHow the system is put together, written for somebody who has to integrate with it.Read moreAPIThe intended REST surface: tenant-scoped, idempotent and versioned.Read moreSDKsTyped clients generated from the API contract, once that contract is published.Read moreSandboxA tier where nothing touches real money and mock providers are permitted.Read moreSmart ContractsIdentity registry, compliance module, token and factory — with the rules legible rather than asserted.Read moreWebhooksSigned HTTP callbacks for events that already committed. Verify the signature, deduplicate on the event id, and return 2xx.Read moreStatusWhat is running, what is degraded, and what has never been exercised.Read more