Documentation
Five services behind one bearer key: live web search, clean content extraction, grounded answers, deep research and standing monitors. Start with a concept guide for what spans every service, or go straight to the reference for the one you're calling. No account needed to read any of it.
# one call, cited answer back curl -X POST https://api.stelq.com/v1/answers/ask \ -H "Authorization: Bearer $STELQ_KEY" \ -d '{"query":"EU refiner exposure to Hormuz"}'
Reading this as an agent?
Every format below is generated from the same model this site renders, needs no key to fetch, and is always current. Point your agent at one of them instead of scraping these pages.
Start here
The cross-service on-ramp: how STELQ fits together, how auth works on every call, and the one path from a fresh key to your first 200. Each service still keeps its own Quickstart on its Docs tab — these tie the five services, MCP, and the wallet into one picture.
Money & limits
How the prepaid wallet works account-wide: what a call costs, charge-on-success-only, what a 402 means, and how to cap spend per key or auto-reload before you run dry. Spans every billed service — every claim maps to the gateway code.
Connect an agent
STELQ's wedge: one hosted MCP server exposes all five services as native tools, and a copy-ready work-order prompt hands a build order straight to a coding agent. One MCP config covers everything — so this is platform-level, not per-service.
Async research (the hard part)
Research is the only async, idempotent service — and where the real integration bugs live. Two guides: the submit → poll lifecycle with idempotency, and webhook signature verification (shared with Monitors). None of it applies to the three synchronous services.
Standing watches
Monitors keep running after the call returns: compiled once, checked on a cadence, every check recorded and badged. The only service priced on two axes (size × cadence) and the second webhook-bearing one. One guide covers sizing, events, thresholds and pause/resume.
Service references 5
One reference per live service: parameters, request and response shapes, errors, rate limits, plus a copy-ready work order for a coding agent.