Docs · LLMs and developers
Version3.14.0Isolate Memory API credentials, data, webhooks, usage, and side effects across Test and Production.
Memory API environments
Memory API environments separate integration testing from production data and behavior. An organization can have one environment of each type: Test and Production.
Create API keys and webhook endpoints inside Test or Production before you use them. Each one stays bound to the environment it was created in.
Organizations that had a Staging environment had it converted to Test, keeping its data, limits, API keys, and webhooks. Existing acm_stg_ keys still work.
Environment selection
The credential determines the environment for every request. Keep the existing organization base URL:
https://{organization}.achiral.ai/v1Create a separate credential for each environment. Achiral does not accept an environment override in a request header, query parameter, or request body. A Test credential therefore cannot be redirected to Production by changing request data.
New credentials carry a prefix that names their environment:
| Environment | Context Access Token | Webhook token |
|---|---|---|
| Test | acm_test_... | wh_test_... |
| Production | acm_live_... | wh_live_... |
The stored credential record, rather than its prefix, is the authorization source. Credentials without an environment binding are rejected; recreate them inside the intended environment.
Isolation boundary
Each environment has separate:
- API keys and webhook credentials;
- webhook endpoints and delivery history;
- event-ingestion and idempotency scope;
- memories, candidates, raw events, and audit records;
- usage counters, limits, and retention; and
- notification, automation, and external-write settings.
The same external event identifier may be submitted once to each environment without an idempotency collision. Data is never read from another environment as a fallback.
An owner can copy an environment's side-effect settings, limits, webhook normalizers, and integration mappings to the other environment. The copy does not include credentials, secrets, event payloads, memories, or API keys.
Side effects
Each environment has three switches: Notifications, Automations, and External writes.
- Test starts with all three off. An owner can turn one on after typing the environment's name to confirm.
- Production starts with all three on.
Only an owner can change these switches. Keep external writes off in Test unless an owner has reviewed the target integration.
Limits
New environments start with these default limits:
| Limit | Test | Production |
|---|---|---|
| Requests per minute | 120 | 600 |
| Events per month | 100,000 | 1,000,000 |
| Records per batch | 500 | 1,000 |
| Payload size | 5 MB | 10 MB |
| Raw event retention | 30 days | 90 days |
| Storage | 10 GB | 100 GB |
An environment's own limits replace these defaults where they are set. An owner can lower a limit, or restore it up to the default; raising it further goes through support.
Settings > API (/settings/api) shows the selected environment's requests per minute, events used this month, and events remaining.
What happens when a request reaches a limit:
- Requests per minute:
429 Too Many RequestswithRetry-After; wait that many seconds before retrying. API responses also carry the rate-limit headers described in the API reference. - Events per month:
429withENVIRONMENT_EVENT_CAPACITY_EXCEEDED. The count resets at the start of each month, UTC. - Storage:
429withENVIRONMENT_STORAGE_CAPACITY_EXCEEDED. - Payload size:
413withENVIRONMENT_PAYLOAD_LIMIT_EXCEEDED. - Records per batch:
413withENVIRONMENT_BATCH_LIMIT_EXCEEDED. - Raw event retention: each raw event expires that many days after Achiral receives it.
Administration
Environments are managed under Settings > General > Environments (/settings/general/environments).
| Action | Who |
|---|---|
| See each environment's name and type in the Environment control on Memory pages | Every member |
| See limits, side effects, and activity | Owners and admins |
| Create Test | Owners and admins |
| Create Production | Owners |
| Change side effects or limits | Owners |
| Copy configuration to the other environment | Owners |
| Reset Test data | Owners |
| Disable or archive Test | Owners in Settings; admins too through the environments API |
Copying configuration asks you to type the target environment's name. Production cannot be disabled, archived, or reset. Archiving Test revokes its API keys and archives its webhook endpoints, and an archived environment cannot be reactivated.
Resetting Test removes data only from Test. It asks you to type the environment's name and does not rotate, delete, query, or modify credentials or data in Production. Production uses the organization's normal retention and deletion controls instead.
The environment you select stays selected as you move between Memory and Settings pages. Check it before creating a credential, copying an endpoint URL, or resetting data.