Arcmira vs DeepSeek Search and Fetch API

Arcmira

Four code-mode tools over a documented v1 API, OAuth 2.1 with four scopes, a read-only sign-up key from two API calls and no card, and a 1,000-credit free month. No status page, SLA or security.txt, breaking v1 changes shipped in October with same-day notice, the server is at 0.10.7, and the index covers the shows Arcmira transcribes.

DeepSeek Search and Fetch API

Search returns up to 50 results with a model-length summary, an authority tier and optional full text, and only successful non-empty calls are billed, at $0.75 per 1,000. It opened on 17 October 2026, with 5 requests a second per account, no OpenAPI file, no free tier, and data held in the PRC under a policy that permits training.

Arcmira

1. Call arcmira_describe once per session and write one program per question for arcmira_execute_read; return only the fields the answer needs, since output is cut at 12,000 characters and 3,000 per string.
2. Resolve names with arcmira.resolve (free) before any about, by, entity_ids or channel filter; a name in a filter fails with id_required. Plain keyword search needs no resolver call.
3. Check arcmira.status() or GET /v1/me for the plan, scopes and usage.credits.available before metered reads; on Free, media newer than 30 days and pages past the first fail with freshness_requires_paid and pagination_gated.
4. A Premium read of an untranscribed video starts a transcription that uses credits (300 per started 15 minutes) and may return pending; read the same video again later, which is never charged twice, and send retry: true only when the user asks.
5. Over HTTP send Authorization: Bearer arc_sk_..., an Idempotency-Key on every POST and PATCH, honour Retry-After on 429, and switch on error.code, following unlock.url on 402 and 403 rather than re-authenticating.
6. Use arcmira_execute_write only after listing the user's monitors; it creates, follows and pauses but never deletes, and a connection made before server 0.9.0 answers insufficient_scope until reconnected.

DeepSeek Search and Fetch API

1. Keep query to 128 characters and put filters in it as operators, such as site:github.com lang:en after:2026-01-01
2. Leave need_content false and read summary first, then call Fetch on the URLs you keep
3. Stay under 5 requests a second per account across all keys. On 408, 429 or 5xx wait and retry, since no Retry-After is documented
4. Don't retry a Fetch 403 or 404 unchanged. The page is blocked by policy, unreachable or has no Markdown
5. Don't send private queries or an end user's IP in localization. Data is stored in the PRC