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, custom rate limits, or enterprise on-demand limits, mention “API access” in your email and we’ll route accordingly.

​
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.
  • Exports API: large async export jobs (CSV/Parquet) for full mention or appearance dumps, with signed URLs.
  • Sandbox / test mode: a fixed synthetic dataset and a separate key prefix (arc_sk_test_...) for CI and dry-run flows.
  • Teams & Enterprise features: team member management, roles, team-wide usage reporting, and centralized billing for Teams; pooled usage, SSO, and SCIM for Enterprise.
If any of these block your integration, write to hi@arcmira.com: concrete use cases move things up the queue.