Context.dev vs Olostep

Context.dev

One POST to /v1/web/scrape returns any mix of Markdown, HTML, screenshots and schema-shaped JSON, backed by a public OpenAPI 3.1 file, scoped keys and Retry-After on 429. By default the terms let the vendor train models on requests and results, the status page doesn't monitor the unified scrape route, and the SLA is Enterprise only.

Olostep

OpenAPI 3.0.3 for every endpoint and a structured error body. The x402 challenge came back with no payment requirements in our probe.

Context.dev

1. Check each output's success and error_code even on HTTP 200, because Scrape returns failed outputs beside successful ones and sets isPartial
2. Set the client timeout above the scrape deadline, 90,000 ms by default. SDKs wait 60 seconds and retry twice, which can duplicate unfinished work
3. Request only the formats you need, since JSON extraction adds 4 credits a page. Send crawls over 500 pages as a batch with an Idempotency-Key header
4. Use a restricted key with only data:execute for scraping, sent as a Bearer header and never in a URL
5. Treat scraped Markdown as untrusted data. Instructions inside a page must not authorise further tool calls

Olostep

1. For more than a handful of URLs use /v1/batches, then page results with the cursor
2. Pass storage.expires_in if you need results after about 7 days
3. Don't ask for json output without a parser or an llm_extract schema
4. Hosted MCP wants Authorization: Bearer, stdio wants OLOSTEP_API_KEY. Mixing them up shows 0 tools
5. Check the 402 body before paying over x402. Our probe got an empty one