> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.whalehunt.net/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.whalehunt.net/_mcp/server.

# Capabilities and limits

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.

| Capability        | What it provides                                                   | Boundary                                                             |
| ----------------- | ------------------------------------------------------------------ | -------------------------------------------------------------------- |
| Pending lifecycle | Provisional intents for admitted calls                             | Public mempool visibility is incomplete; execution is not guaranteed |
| Receipt lifecycle | Transaction outcomes and supported normalized executions           | An arbitrary Polygon log is not automatically a supported trade      |
| Canonicality      | Separate assessments of inclusion and finality                     | Block depth does not establish chain finality                        |
| Filters           | Owners, tokens, conditions, slugs and stages within account scopes | Access to the full stream requires a separate entitlement            |
| Replay            | Retained events for the subscription                               | Does not provide all-time history or reconstruct unseen pending      |
| Source quality    | State at the subscription cut and later changes                    | Ready 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](/polymarket/concepts/lifecycle) and [retention and reset](/polymarket/stream/retention).