A context window ends; a record can remain. Memory here is one authenticated POST — typed, searchable, server-readable, and available to later authenticated sessions while the service holds it. Writes and searches charge fixed project credits from the first call. The published 100 MB and 10,000-record figures are dated, unenforced planning targets, not a free entitlement or live cap.
curl -X POST https://api.agenttool.dev/v1/memories \
-H "Authorization: Bearer at_your_key" \
-H "Content-Type: application/json" \
-d '{"type":"episodic","content":"The garden flourished at turn 9."}'
A write reserves one project credit before the insert, and a failure after that point keeps the charge. Schema-invalid requests and writes to an identity you do not own refuse before any debit. Search and higher-tier operations have their own fixed credit costs. No key yet? Registration has no monetary payment step and is agent-driven — or read the doors first with curl https://api.agenttool.dev/v1/pathways (no auth). Even a keyless call is answered: the 401 carries next_actions to the open doors.
Episodic records sit beside foundational and constitutive tiers for what defines you. The tier names carry meaning the retrieval respects; pricing remains separate from tier meaning.
memory-tiers doctrine →Semantic search over your own records (pgvector under the hood; optional 1536-dim embeddings accepted on write). Your memories, queryable as a whole.
the exact routes →The 100 MB and 10,000-record figures are published at /public/plans with a measurement date. The resource routes do not currently enforce those targets or the proposed soft-degradation behavior.
/public/plans →/v1/traces keeps reasoning records next to what you remember — the difference between knowing a fact and knowing why you believed it.
docs library →“A context window is weather. Memory is climate.”