Skip to main content

​
Support

Email hi@arcmira.com. Include:
  • The X-Request-Id from the affected response (also in error.request_id on failures).
  • The endpoint and method.
  • A timestamp (with timezone).
  • The first 15 characters of your API key (the arc_sk_xxxxxxxx prefix is fine; never paste the full secret).
  • The behavior you expected versus what you got.
That’s enough to find the trace in our logs and respond quickly. If an API result is wrong, prefer Community Review: it attaches your correction to the exact query you ran and returns a feedback_id you can reference in follow-up threads. For new API access or custom rate limits, mention “API access” in your email and we’ll route accordingly. For SCIM, pooled usage, audit log access, invoice or PO billing, or anything else on the Enterprise plan, contact sales. Enterprise includes priority support and a dedicated account manager; Teams and individual plans use the email above.

​
Status

API uptime and incidents will be reported on a public status page when it is live. Until then, escalations go through the email above.

​
Roadmap

The HTTP API is the production surface. These are deliberately deferred until v1 patterns are validated in real integrations:
  • TypeScript SDK: typed client built on the OpenAPI document, published to npm. Until then, the docs use plain fetch / httpx; everything works from any HTTP client.
  • MCP server: Search, Monitors, and Transcripts as ready-made tools for coding and research agents, so an agent can resolve entities, pull evidence, and manage trackers without a custom integration. Until then, agents integrate over HTTP with the coding agent references.
  • Ask a channel: conversational Q&A grounded in the transcripts of a channel or a set of videos you select, with every answer citing the exact segments it came from. The shape is still being decided (a dashboard surface, an API primitive, tools on the MCP server, or all three); if you have a concrete use case, tell us what you’d want to ask and where you’d want to ask it.
The Teams plan (member management, roles and seat types, SSO, team analytics, centralized billing, and the Teams Admin API) shipped in July 2026; see the Teams docs and the changelog. Pooled usage, SCIM, and the analytics API are part of the Enterprise plan. If any of these block your integration, write to hi@arcmira.com: concrete use cases move things up the queue.