Developers and agents
SteadyTrader is a browser product, not an integration platform. The market-data engine (modeled dealer positioning, gamma levels, unusual-flow context and historical replay) is gated, per-key rate-limited, and has no anonymous or agent-callable surface. What is public is small. It is documented here so a developer, a crawler, or an AI agent can find out exactly what they can and cannot do without guessing.
Machine-readable resources
Everything an automated client needs to orient itself is served as a stable, versioned document. None of it exposes the paid feed.
- OpenAPI specification. An OpenAPI 3.1 document describing the only genuinely public endpoints: the waiting-list signup and the email and alert unsubscribe links. Each operation carries a stable operationId, typed request and response schemas, and the shared structured error shape, so it is usable directly for LLM function calling. The market-data product is not a public API and is not described there.
- llms.txt. A concise, machine-readable summary of what SteadyTrader is, when an assistant should and should not use it, and the plain statement that there is no public market-data API. It is served as text/markdown and is the fastest way for a model to orient itself before answering a question about the product.
- agent-info.json. Structured browser-use guidance for agents: the launch product, the access mode, the documented limitations, and an explicit empty list of agent-callable actions. Read it before presenting any modeled level as if it were observed fact.
- Sitemap. The canonical list of indexable pages, kept in step with robots.txt so a crawler is never invited to a page that answers a redirect. It advertises only what actually resolves in the current launch state.
Public endpoints and rate limits
Two endpoints are public in every state of the site, and both are described in the OpenAPI document above.
- Waiting-list signup. The signup requires a Cloudflare Turnstile human-verification token, so it is not a surface an automated agent can complete. An agent should send a person to the page rather than call it. Its response is deliberately the same for a new and an already-listed address, so it cannot be used to test whether an address is on the list.
- Unsubscribe links. The email and alert opt-out links carry an opaque, single-purpose token and support both a browser click and the RFC 8058 one-click header used by mail clients. They grant nothing but the opt-out they were minted for.
- Rate-limit headers. Every response carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, plus RateLimit-Policy, and a Retry-After header on a refusal. They advertise the coarse per-IP ceiling that a well-behaved client uses to self-throttle; the tighter per-endpoint budgets are intentionally not published.