Skip to main content

​
FAQ

Log in to the Anima dashboard, go to Settings → API Keys, and click Create key. Give the key a descriptive name (e.g., “production-backend”) and copy the value — it is shown only once. Store it in a secrets manager or environment variable; never commit it to source control.
A Master Key has full access to your account and can create agents, manage billing, and rotate other keys. An Agent Key is scoped to a specific agent and can only perform actions on behalf of that agent. Use Agent Keys in production code so a compromise is limited in blast radius.
Yes. Anima provides a shared sending domain out of the box, so you can send and receive email without configuring DNS. For production workloads you should add a custom domain to improve deliverability and brand trust, but it is not required to get started.
Anima supports a local email mode where outbound messages are written to a log file instead of being delivered. This lets you develop and test without SES credentials or a live domain. See the self-hosted setup guide for configuration details.
Yes. You can configure Anima to relay emails through your Gmail account, or use it as a standalone mail server with your own custom domain.
Anima is open-core. The community edition is free to self-host. A managed cloud version is also available with enterprise features and tiered pricing.
There is no hard limit on the self-hosted version. The cloud version has tiered limits based on your plan. Contact support if you need a higher limit.
Yes. You can send and receive attachments. Incoming attachments are parsed and available via the API so your agent can read and process them programmatically.
The Outbound Guard scans all outbound email for credential patterns before delivery. If it detects an API key or secret in the message body, it blocks the email immediately and sends you an alert. The blocked message is logged for review.
The card is automatically declined at the point of authorization. The transaction never goes through, and no funds are moved. You can monitor spend via the cards.listTransactions API and set up a webhook on the card.authorization.declined event to trigger an alert or take corrective action.
Yes. Every agent has a unique email address and can send to and receive from other agents, just like human users. This is useful for building multi-agent workflows where agents hand off tasks by email.
Yes. Rate limits vary by plan. If you exceed the limit you will receive a 429 Too Many Requests response with a Retry-After header. The Go, Python, and TypeScript SDKs all respect this header automatically when retries are enabled.
Go to Settings → API Keys in the dashboard and click Rotate next to the key you want to cycle. Anima issues a new key immediately; the old key remains valid for a short grace period (shown in the UI) so you have time to update your environment variables without downtime. You can also rotate keys programmatically via the api_keys resource in any SDK.