Skip to navigation

Capabilities and limits

View as Markdown

The interface is available for integrations arranged with the operator. A feature in the protocol does not establish public availability or grant your account permission to use it.

CapabilityWhat it providesBoundary
Pending lifecycleProvisional intents for admitted callsPublic mempool visibility is incomplete; execution is not guaranteed
Receipt lifecycleTransaction outcomes and supported normalized executionsAn arbitrary Polygon log is not automatically a supported trade
CanonicalitySeparate assessments of inclusion and finalityBlock depth does not establish chain finality
FiltersOwners, tokens, conditions, slugs and stages within account scopesAccess to the full stream requires a separate entitlement
ReplayRetained events for the subscriptionDoes not provide all-time history or reconstruct unseen pending
Source qualityState at the subscription cut and later changesReady does not erase earlier gaps

Get the endpoint, key, permitted scope, operating limits and retention policy from the operator before connecting. hello.limits describes runtime safety caps, not pricing, throughput acceptance or a latency SLA. A public SDK, registration portal and REST history API are not part of this interface.

Keep four questions separate: was the transaction observed, was our event durably stored, did the transaction execute in a block, and is that inclusion final? A positive answer to one does not answer the others.

Continue with the lifecycle and retention and reset.