> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/arcmira.md).

# Arcmira

Create an Arcmira API key and connect the Appmixer Arcmira connector.

The Appmixer Arcmira connector (**Find Transcripts**, **Resolve Entity**, **Make API Call**) uses **API key** authentication. You do not need to register an OAuth app with Arcmira. Each user creates an API key in their Arcmira account and enters it when they connect Arcmira in Appmixer.

***

## 1. Create an API key

1. Sign in to [Arcmira](https://arcmira.com). Create an account if you do not have one. New accounts start on the Free plan.
2. Open [Dashboard → API keys](https://arcmira.com/dashboard/api).
3. Click **Create key**.
4. Copy the key. It starts with `arc_sk_`. Arcmira shows the secret only once, so store it somewhere safe.

Dashboard keys carry the scopes `read`, `monitors:write`, `trackers:write` and `recommendations:read`. **Find Transcripts** and **Resolve Entity** only need `read`. **Make API Call** can also change monitors and trackers, as far as the key's scopes allow.

{% hint style="info" %}
A key acts in the Arcmira account that was active when the key was created: your personal account or a team account. All requests made with the key use that account's plan and credits. Paid reads use credits from the plan first, then the on-demand budget. Scopes never unlock plan features.
{% endhint %}

Arcmira also lets you get a key without a browser, through its sign-up API. See [Keys and sign-in](https://arcmira.com/docs/authentication) in the Arcmira documentation.

***

## 2. Connect in Appmixer

When you add an Arcmira component to a flow, Appmixer asks you to connect an account. Paste the key into the **API Key** field.

Appmixer sends the key as a bearer token (`Authorization: Bearer <key>`) to `https://api.arcmira.com/v1`. To check the key, it calls `GET /v1/me`, which is free and works even when the account has no credits left. The connection is named after the masked email of the key's owner (or the key label). For a team account, the team name is shown in front of it.

**Make API Call** only sends requests to `https://api.arcmira.com/v1`. It rejects other hosts, so the key is never sent anywhere else.

***

## Rate limits

Arcmira limits requests per API key in a 60-second window: 60 on the Free plan, 240 on paid plans and 600 on Enterprise. The connector queues requests to stay at 60 requests per 60 seconds per connected account, so it stays under the limit on every plan.

***

## Troubleshooting

* **401 when connecting:** check that you copied the whole key (`arc_sk_…`) and that it has not been disabled on the **API keys** page.
* **402 errors when running a flow:** the account has run out of credits or reached its on-demand budget. Check the plan and usage in the Arcmira dashboard.
* **403 `insufficient_scope` from Make API Call:** the key does not have the scope that the request needs (for example `monitors:write`). Create a dashboard key, which carries all write scopes.

***

## Backoffice configuration

Configuration ID: `appmixer:arcmira`. For how to set connector configuration values, see [Connector Configuration](https://docs.appmixer.com/getting-started/services).

You do not need any Backoffice configuration to authenticate, because every user enters their own API key. There is one optional key:

* `outputFilePrefix`: optional. A prefix for the names of CSV files created when **Find Transcripts** runs with the **Store to CSV file** output type. Files are named `<prefix>-<component label in the flow>.csv`. The default is `arcmira-objects-export`.

```bash
appmixer service-config set appmixer:arcmira -u -d '{"outputFilePrefix": "arcmira-objects-export"}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/arcmira.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.