API Overview

The API splits into two planes.

Plane	What it covers	Authentication
Data plane	The memory operations your agent calls at runtime. Metered in credits.	API key: `Authorization: Bearer anona_live_...`
Control plane	Account, workspace, key, and billing management. Backs the dashboard, and is callable programmatically.	Session token, or an API key where noted

Base URL: https://api.anonalabs.com

https://memory.anonalabs.com also works and always will. If that is what your code already uses, nothing needs to change. api.anonalabs.com is simply the recommended host for new integrations. The one exception is the remote MCP endpoint, which stays at https://memory.anonalabs.com/mcp.

Every endpoint returns errors in a single envelope. See Errors.

Data plane

Runtime memory operations. See Authentication for how to pass your API key.

Method and path	What it does	Reference
`POST /v1/record`	Stores a memory. Anona extracts the durable facts and files them in the space. Pass `"async": true` to queue the write and get a `job_id` back immediately.	Memories
`POST /v1/record/batch`	Bulk-ingests up to 100 memories in one call. Always async, returns a `job_id`.	Memories
`GET /v1/spaces/{space_id}/jobs/{job_id}`	Status of an async ingestion job. Free, consumes no credits.	Memories
`POST /v1/retrieve`	Semantic and keyword search over a space. Returns ranked memories with entities and event time.	Retrieve
`POST /v1/reason`	Cross-memory synthesis: asks a question and reasons over everything in the space.	Reason
`GET /v1/spaces/{space_id}/memories`	Lists stored memories, filtered by `type`, `state`, or text `q`, with pagination.	Memories
`GET /v1/spaces/{space_id}/memories/{memory_id}/history`	Change history for a memory: what it said before, and when it changed.	Memories
`DELETE /v1/spaces/{space_id}/memories/{memory_id}`	Deletes a memory.	Memories
`POST /v1/spaces/{space_id}/documents`	Uploads files. Their content is parsed, chunked, and made searchable.	Documents
`GET /v1/spaces/{space_id}/graph`	The entity graph built from the space, as nodes and co-occurrence edges.	Graph
`POST /v1/chat/completions`	OpenAI-compatible chat that auto-retrieves relevant memories into the prompt, and stores the turn back. Supports streaming.	Chat
`POST /v1/responses`	The same memory wrapper in the OpenAI Responses API shape.	Responses
`POST /v1/messages`	The same memory wrapper in the Anthropic Messages shape.	Messages
`GET` `PUT` `DELETE /v1/spaces/{space_id}/chat-settings`	Per-space defaults for the proxy: how many memories to inject, the injected token budget, whether to auto-record. Free.	Chat
`POST /mcp`	Remote MCP endpoint. Tools: `record`, `retrieve`, `list_spaces`, `reason`.	MCP
`GET /v1/usage/me`	Credits and rate limit remaining for the calling API key.	Usage
`POST` `GET` `PATCH` `DELETE /v1/spaces/{space_id}/webhooks`	Registers an HTTPS endpoint Anona calls when memories are stored or consolidated, instead of polling.	Webhooks

Try it out: record and retrieve a memory

Record

curl -X POST https://api.anonalabs.com/v1/record \
  -H "Authorization: Bearer anona_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "space_id": "demo-space",
    "content": "The user prefers dark mode and replies in Spanish."
  }'

Retrieve

curl -X POST https://api.anonalabs.com/v1/retrieve \
  -H "Authorization: Bearer anona_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "space_id": "demo-space",
    "query": "What language does the user prefer?"
  }'

See Memories and Retrieve for the full request and response shapes.

Control plane

Account and workspace management. Most of these back the dashboard; the workspace, key, and usage endpoints are also useful programmatically.

Method and path	What it does	Reference
`GET /v1/orgs/me`	Your organization: plan, status, limits.	Organization
`GET /v1/spaces` · `POST /v1/spaces`	Lists and creates memory spaces.	Spaces
`GET /v1/spaces/{id}` · `DELETE /v1/spaces/{id}`	Fetches and deletes a space.	Spaces
`GET /v1/spaces/{id}/members` · `POST .../members/invite` · `DELETE .../members/{member_id}`	Space membership.	Spaces
`GET /v1/api-keys` · `POST /v1/api-keys` · `DELETE /v1/api-keys/{id}`	Manages API keys.	API Keys
`GET /v1/projects` · `POST /v1/projects`	Manages projects.	Organization
`GET /v1/members` · `POST /v1/members/invite` · `DELETE /v1/members/{id}`	Manages organization members.	Organization
`GET /v1/usage` · `GET /v1/usage/breakdown`	Organization usage, and a per-operation breakdown.	Usage
`GET /v1/billing` · `POST /v1/billing/upgrade`	Views the plan, and changes to a free tier.	Billing
`POST /v1/billing/checkout` · `POST /v1/billing/portal` · `POST /v1/billing/cancel`	Stripe checkout, billing portal, and cancellation.	Billing

Try it out: list spaces and check usage

List spaces

curl https://api.anonalabs.com/v1/spaces \
  -H "Authorization: Bearer anona_live_YOUR_KEY"

Check usage

curl https://api.anonalabs.com/v1/usage/me \
  -H "Authorization: Bearer anona_live_YOUR_KEY"

See Spaces and Usage for the full request and response shapes.

Account sign-in (/auth/...) and MCP OAuth (/oauth/...) are browser flows used by the dashboard and by MCP clients. See Authentication and MCP rather than calling them directly.

API Essentials

Memory (data plane)

LLM Proxy (drop-in)

Account (control plane)

Data plane

Control plane

​Data plane

​Control plane

Data plane

Control plane