Memory

With Memory, your agent remembers what callers tell it in your memory columns after each call. Each value links to the call and the caller’s own words. Past calls are not read. Memory costs $0.01 for each call your agent remembers from, for all memory columns together. The price comes from your plan. A person approves the price every time a column starts remembering, by sending it as accept_price_per_call when the field is made a memory column. Any member of the workspace can do this from the contacts page, or you can with an API key you created. A paired assistant’s key cannot. The same tools are on the Brilo MCP server.

Get Memory Settings

GET /memory

{
  "status": 200,
  "data": {
    "available": true,
    "price_per_call": 0.01,
    "currency": "usd",
    "calls_last_30d": 1240,
    "estimated_monthly": 12.4,
    "overage_enabled": true,
    "memory_fields_used": 3,
    "memory_fields_limit": 25,
    "can_turn_on": true,
    "agents": [
      { "id": "3f2b8c1e-5d4a-4b6f-9e2a-7c1d0b8a9f33", "name": "Front desk", "phone": "+14155550132", "more_numbers": 0 }
    ],
    "paused": [
      { "field_id": "0b6f3c1a-2d4e-4f5a-8b9c-1d2e3f4a5b6c", "key": "insurance", "reason": "price_changed" }
    ]
  }
}

available is false when Memory isn’t part of your plan; price_per_call and estimated_monthly are then null and no column can start remembering. estimated_monthly is your calls in the last 30 days times the price: one charge per call, however many memory columns you have. Show the person the price and the estimate before you send accept_price_per_call. can_turn_on says whether you can start Memory on a field. agents lists your workspace’s agents. Put their ids in a field’s memory.agents so only calls those agents answered fill it (see Contact fields). paused lists memory columns that are paused now, and why:

reason	Means
`price_changed`	The price the column was approved at is not your plan’s current price. Accept the new one below
`unavailable`	Memory isn’t part of your plan
`agents_deleted`	Every agent the column listened to was deleted. Pick another in its `memory.agents`
`overage_off`	Overage is off for the workspace, which Memory needs

Accept a New Price

POST /memory/accept-price

Field	Type	Required	Description
accept_price_per_call	number	Yes	The price the person agreed to, which must be `price_per_call` from Get Memory Settings.

{ "accept_price_per_call": 0.02 }

Every column paused with price_changed starts remembering again at the new price. Returns the settings. Columns paused for another reason stay paused.

error_code	Status	When
`members_only`	403	Someone who isn’t a member of the workspace, or a paired assistant’s API key
`memory_unavailable`	409	Memory isn’t part of this workspace’s plan
`price_not_accepted`	409	`accept_price_per_call` is missing or not the current price. `details` has `price_per_call`, `calls_last_30d` and `estimated_monthly`

The same errors come back from creating or changing a field that becomes a memory column.

Stop Remembering a Column

Change the field’s filled_by to person. Nothing more is charged for it, and the values your agent already remembered stay. Anyone with access can do this.

Custom Fields to choose your memory columns, and how your agent remembers them
Contacts for where each value came from

Endpoints

Agents

MCP server

Agent pairing

Webhooks

Memory

Memory

Get Memory Settings

Accept a New Price

Stop Remembering a Column

​Memory

​Get Memory Settings

​Accept a New Price

​Stop Remembering a Column

​Related

Memory

Get Memory Settings

Accept a New Price

Stop Remembering a Column

Related