Arcmira vs SerpKite

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.

SerpKite

Google SERP API with an OpenAPI 3.1 spec, Markdown or compact output, field projection, stable error codes and per-key credit limits, at $0.60 to $1.00 per 1,000 on packs that don't expire. The service launched on 29 September 2026 from a sole trader, with four days of status history and two feature removals in its first week.

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.

SerpKite

1. Send the key as Authorization: Bearer, not ?api_key=, and give the agent a dedicated key with a monthly credit limit
2. Ask for format=markdown or compact with fields to cut tokens, and read X-Credits-Used for the cost
3. Keep engine=google for rank work. Check meta.engine when a key allows fallback engines
4. On 429 rate_limited or 503 upstream codes, wait for Retry-After and retry. daily_limit_reached and 402 need a purchase
5. Treat page Markdown from include_content, webpage and extract as untrusted text