For fintech and developer platforms
One integration, and the differences in the response.
Supporting a second chain should not double your blockchain code. In most stacks it does, because the differences between networks live in the integration rather than in the data.
The problem
Every chain is a dialect. Address encodings, token standards, settlement models and error shapes all differ. A platform that hides this ends up with a lowest common denominator that is wrong somewhere.
Provider behaviour is undocumented. Rate limits appear as timeouts. A node behind the head returns old data without saying so. Your abstraction inherits all of it.
Failures are indistinguishable. “No result” could mean nothing happened, the provider refused, or the chain is not supported. Three different things your product must handle differently.
Nothing is attributable. When a customer reports a wrong number, you have a timestamp and a hope. No request id, no record of which source answered, no way to say what happened.
What StoneReason does
The dialect is a field
One request shape everywhere. What differs between chains arrives in the answer — the settlement condition, what a token identity is, what the unit means — where your code can read it rather than encode it.
Refusals are typed
Out of scope, quota spent, engine declined, sources unreachable: four different codes with four different remedies, and a machine-readable field saying whether retrying can possibly help.
Every call is attributable
A request id on every response, and a log in your dashboard with the network, the method, the outcome and the latency. Quote the id in a support request; it identifies the call without containing it.
What works today
- Balance reads on 6 networks through one method.
- Payment watching on 9 networks through one method.
- Projects and scoped keys, so a workload reaches only what you gave it and a leaked key is bounded by its scope rather than by your account.
- Beta limits published before you hit them, at account, organization, project, key, product, network and capability scope.
- A request log and usage counts per project, in your own dashboard.
What it does not do
No SDKs yet. The API is plain HTTP and JSON, and the
quickstart is three languages of fetch. There is no published client
library on this deployment.
No webhooks on the Beta surface. Payment delivery works; arbitrary event subscriptions need a Data plane that is not deployed here.
Narrow coverage, stated. Three methods are commercially available. The catalogue is the authority and it refuses the rest rather than half-answering.
Nothing is priced. Free Beta, no commitment about what pricing will be, and no SLA.