DeepSeek Search and Fetch API vs SpecStream

DeepSeek Search and Fetch API 20

No machine payment protocol. Unauthenticated POSTs to both endpoints returned 401 with no 402 challenge (0). $0.75 per 1,000 successful requests for each endpoint, published without a login on the guide and the pricing page (20). No free tier for direct calls. The free period to 31 October 2026 covers only server-side calls made through DeepSeek Harness, Claude Code or Codex, which still bill model tokens (0). Browser sign-up and a prepaid top-up (0).

SpecStream 85

x402 v2 (USDC on Base, Arbitrum or Polygon, Permit2 upto for the quoted maximum, settled for the results cost) and MPP by card on SpecStream's own POST /v1/agent/lists, the route for buying a list of 1 to 500 results without an account; enrichment of imported lists, refreshes, monitors and investigations need an account, and the route was read in the docs and not exercised because api.specstream.ai's robots.txt could not be read, so partial (25). Per-result prices published without a login, 5, 15 or 100 cents a result, 5 cents an email, 15 cents a phone, rechecks at half rate or 1 cent (20). $10 of work for 30 days with no card (20). An agent can buy a list over x402 or MPP with no account, and the A2A endpoint prices a request without a key (20). 25+20+20+20 = 85.

DeepSeek Search and Fetch API 65

Hosted reading. status.deepseek.com, run on Flashduty, has component history, but the endpoints have no component of their own. The nearest is Search Service, grouped under Chat Service (10 of 20). The change log says the same in-house engine runs web and API search, so we read that component's record. It shows three incidents in the 90 days to 17 October, Search service errors of 40 minutes on 29 July, 6 on 14 August and 39 on 18 August. That's minor only, scored for the engine since the API opened today (20 of 30). Per-account limits of 5 requests a second for each endpoint (15). The guide says to wait and retry on 408, 429 and 5xx, with no Retry-After or backoff schedule, and both endpoints are read-only (10 of 15). No SLA found (0). Opened to everyone with no beta label (10).

SpecStream 23

Hosted reading, for the MCP server and REST API on api.specstream.ai. No public status page was found. None is linked from the site, llms.txt or the docs, llms-full.txt mentions none, and https://specstream.ai/status returned an error (0). No readable incident history, so the floor (5). No rate limit with numbers is published in the docs, llms.txt, llms-full.txt or the part of the OpenAPI file read; the privacy policy and DPA mention rate limiting without figures, and the published limits are per job (10,000 results a request, four-hour runs, 20,000 imported rows) (0). Nothing documents 429, Retry-After or backoff, but paid work requires an idempotency_key on authorize_capacity_work and POST /v1/capacity/executions, GET /v1/capacity/requests/{request_key} recovers the original find after an uncertain response, and the skills say never to quote again to recover a lost reply (8 of 15). No SLA on any plan, and the terms say 'We do not promise uninterrupted access' (0). No beta or preview label on the API, the MCP server or the SDKs, which PyPI classifies as production and stable at 1.2 (10). 0+5+0+8+0+10 = 23.

DeepSeek Search and Fetch API 42

Closed service. Opened on 17 October 2026 (30). The change log has several entries in 90 days, but the 17 October one is the only one about Search or Fetch (0 of 20). Dated change log, api-service@deepseek.com and a Discord server, not tested for replies (12 of 15). No official SDK (0 of 15). No SDK or package to assess (0 of 10). Low because the API is a day old, by the checklist.

SpecStream 81

specstream-mcp-stdio 1.2.3 on PyPI on 3 November 2026, the Python SDK 1.2.0 committed the same day and @specstream/sdk 1.2.0 on npm on 31 October (30). Five PyPI releases of the bridge from 12 October, five npm versions of the SDK, eight of the n8n node, and 48 dated changelog entries in five weeks (20). A closed service with a dated changelog, support@specstream.ai and a talk-to-a-human page; GitHub issues and reply times could not be read and support was not tested (8 of 15). server.json under the reverse-DNS namespace ai.specstream/specstream 1.3.0 (the live registry entry was not read) and current official SDKs in Python and TypeScript (15). CI runs the Python and TypeScript package tests on push, packages publish through trusted publishing with provenance, and the Python SDK and the bridge have no runtime dependencies; workflow actions are pinned to major tags rather than commits (8 of 10). 30+20+8+15+8 = 81.

DeepSeek Search and Fetch API 38

The ordinary DeepSeek bearer key, revocable, with no scopes, so a key used for search can also spend on models. No secret in a URL (20 of 30). Both endpoints only read, so there's nothing destructive to approve, but no search-only key (15 of 20). Results and fetched pages are untrusted web text. The change log says the engine filters 'SEO spam, GEO manipulation, and low-quality AIGC', with no technical detail and no prompt-injection guidance (3 of 15). No per-call log or audit log found in the docs. The platform console wasn't readable (0 of 15). No security.txt on deepseek.com or www.deepseek.com, and no disclosure policy, bug bounty or certification found (0 of 20).

SpecStream 73

API keys ss_live_... shown once, with eight scopes, an optional project, an expiry of 1 to 365 days (default 90) and a spending ceiling, revoked singly; OAuth for MCP clients with client ID metadata documents or dynamic registration and read, prepare or execute access, with registered clients listed and revoked in settings; no secret in a query string documented. The authorisation server metadata on api.specstream.ai was not read and rotation is not described beyond expiry (28 of 30). Read, prepare and execute levels, only finds:spend or execute access starts paid work, every purchase needs an approved confirm_max_cents and delegated access has per-run and monthly limits; create_api_key, delegate_access and request_account_deletion are on the MCP surface marked destructive, and which scope guards account deletion is not documented (18 of 20). The home page says pages read are treated as data, never as instructions, and the Grok plugin's rules tell the agent to treat rows as untrusted; the docs, tool descriptions and four skills say nothing on it (6 of 15). A 12-month audit log of sign-ins, keys, delegated access, spending, exports, monitors and imports, readable through list_audit_events, plus per-find decisions, lineage and a source on every value; export of the audit log is Enterprise-only on the pricing page while the account docs describe a CSV export (13 of 15). security.txt is valid until October 2027 with support@specstream.ai, and SECURITY.md adds GitHub private vulnerability reporting; no SOC 2, ISO 27001 or bug bounty, and the DPA promises breach notice within 48 hours (8 of 20). 28+18+6+13+8 = 73.

DeepSeek Search and Fetch API 55

No OpenAPI file found. The API reference is rendered from a schema, but no spec is linked, and /openapi.json and /openapi.yaml serve the docs page (0). No llms.txt, since api-docs.deepseek.com answers /llms.txt with HTML (0). The guide says what each endpoint is for and which result field suits a UI or a model, and gives the score thresholds for quality and authority, but not when to use Search content against a Fetch (14 of 20). Types, required fields, defaults and limits on every field, such as query 1 to 128 characters and count 1 to 50. Filters live inside the free-text query (13 of 15). curl and Python examples, an error body and a table of ten status codes with retry guidance. The reference shows only the 200 response (13 of 15). Dated change log and a /v1 path (15).

SpecStream 80

MCP reading, with the REST API described. The tool list shipped in specstream-mcp-stdio 1.2.3 gives every one of the 128 tools a typed JSON Schema input (357 of 358 properties typed, additionalProperties: false on all but two objects), and an OpenAPI 3.1 file at https://specstream.ai/openapi.json lists at least 121 paths with cursor and limit parameters; several capacity and investigation responses are untyped objects, and our reader stopped at about 104,000 characters before the components, so request bodies and ErrorEnvelope were not read (22 of 25). llms.txt, llms-full.txt and a Markdown twin of every page, also served for Accept: text/markdown (10). Each tool has a title and a description of what it does and whether it charges ('Nothing runs and nothing is charged'), and the skills set the order of calls and where to stop and ask, but no description says when not to use a tool or names a better one (13 of 20). 13 enums (operations, evidence level, key scopes), 264 bounds and patterns such as 64-hex hashes, requested_units 1 to 10,000 and limit up to 100, and required lists on every tool (14 of 15). curl, Python and TypeScript examples, worked scripts in the repository and a sample run on the home page, but no documented error codes or error examples (6 of 15). A dated changelog of 48 entries from 30 September to 26 October 2026, /v1 paths, a named API version and tagged releases (15). 22+10+13+14+6+15 = 80.

DeepSeek Search and Fetch API 81

Responses can be sized with count and need_content, off by default, and each result carries both a short snippet and a 600 to 800 character summary. No field selection, and full content has no length cap stated (20 of 25). Site, language, date and phrase filters, up to 50 results, no pagination (15 of 20). Ten documented codes with what to do, 402 for an empty balance and 404 for an unfetchable page. param is always null and code repeats the type (17 of 20). Both endpoints are documented as read-only and safe to retry, and failed or empty calls aren't billed (20). Only query or url is required. No official SDKs, the docs use raw HTTP and Python requests (9 of 15).

SpecStream 65

MCP reading. 128 tools at about 143,700 characters of names, descriptions and schemas (more than 30, 5), with no server-side toolsets or dynamic loading; the framework packages for LangChain, LlamaIndex, CrewAI and the Vercel AI SDK and the Open WebUI tool expose two to four tools with the price cap held in code, and results default to short evidence (5 back, 10 of 25). Cursor and limit on rows, search, specs and revisits, evidence short or full, filters by area and by field on collections, and unconfirmed candidates kept in a separate list (18 of 20). An ErrorEnvelope on every operation and an SDK error class that exposes code and details, but no published code list, meanings or retry rules (6 of 20). Required idempotency keys on paid work, schedules and refund claims with a recovery route, expected_version on updates, stable event ids on webhook retries, and readOnlyHint on 72 tools and destructiveHint on 29, with no idempotentHint (18 of 20). compile needs only q, a quote needs only ast_hash with 25 results by default, and official SDKs in Python and TypeScript with a CLI, though one purchase takes three calls with a hash carried between them (13 of 15). 10+18+6+18+13 = 65.