Where your content can be stored
Everything in Antimatter that can hold the text of a prompt or an answer. Nothing else does. No log line prints a prompt, and the site has no analytics script.
Response cache
A hash of the request and the answer it got. Not the prompt.
- A request sends
x-antimatter-cache: on. Non streaming requests only, never on your own provider key. - 10 minutes, then swept. The prefix index beside it holds hashes only, 30 minutes.
- Do not send the header. Entries expire on their own, and erasure deletes yours. An entry written before 2 October 2026 names no account, so erasure cannot find it. It ages out on its window instead.
Semantic cache
An embedding of the prompt and the answer.
- Off on this deployment, because no embedding model is configured.
- 30 minutes, then swept.
- Leave it off on the key. Erasure deletes your rows.
Resumable streams
The streamed answer, so a dropped connection can pick up where it left off. Not the prompt.
- A keyed streaming request sends
x-antimatter-resumable: 1. - 10 minutes after the last write, then swept.
- Do not send the header. Erasure deletes them.
Flight recorder capture
The full request body and the full answer, for replay and debugging, up to 128 KiB each.
- You turn capture on for a key on the dashboard. It is off for every key until then, and never applies to anonymous or keyless traffic.
- 24 hours by default, set per key from 1 hour to 30 days. A change to the window, shorter or longer, applies to what is already stored.
- Delete a capture, or erase the account. Turning capture off stops new captures. The ones already taken stay until their window ends.
Shadow tests
For each replay of a captured request to a candidate model: whether the answers agreed, what it cost, how long it took and any error. Never a copy of the prompt or of either answer.
- You start a shadow test for a key on the dashboard or through the API. It replays only requests the key already captures, while their capture lasts.
- Results 90 days after the replay. A stopped test goes 90 days after it stopped, unless a switch from it still stands.
- Stop the test, or erase the account. A switch stays on the key until you revert it.
Playground threads
Your messages in /chat and the reply to each, and, signed in, the pictures you make there with the words that made them.
- Always, while you use /chat. The page saves the thread so it is there when you come back.
- Signed in: until you delete the thread. Anonymous: 30 days after the last message.
- Delete the thread in /chat, or erase the account. The API never writes here.
Batch jobs
The uploaded JSONL file, each line's request and each line's answer.
- You create a batch through /v1/files and /v1/batches.
- No window yet. Kept until the account is erased.
- Deleting the input file removes the upload, but each line's copy of its request and its answer stay with the batch until erasure. A batch made with an organization's key stays with the organization.
Saved prompts
The prompts you keep: every version's messages, its model and note, and the labels that point at a version.
- You save a prompt on the dashboard's Keys tab.
- Until you delete the prompt or erase the account. A version is never changed once written.
- Delete the prompt on the dashboard, or erase the account. A usage row keeps only the prompt's id and version number.
Vector stores
The files you upload for file search, the text they are cut into, its embeddings, and the attributes you set on them.
- You upload a file with purpose assistants and attach it to a vector store through /v1/vector_stores.
- Until you delete the store or the file. A store with expires_after loses its files that many days after it was last used.
- Deleting a store removes its text and embeddings. The uploaded file stays in /v1/files until you delete it. Erasing the account deletes every store it made.
Memory spaces
The facts your keys ask to be remembered, or that a model read from a conversation they sent, each with its embedding, and the history of every change to them with the words before and after.
- A key writes to /v1/memories, a chat request sends x-antimatter-memory-write, or an agent run uses its memory tool. A conversation queued for reading is kept only until it is read.
- Until you delete the memory or its space. Its history is kept 365 days, and until the space is deleted.
- Forget a memory or delete a space on /memory or through the API. Erasing the account deletes every space it made, with its memories, vectors and history.
Tools market calls
For each call of a market tool: which tool, whether it succeeded, what it cost and how long it took. The arguments you send go to the provider's server and its answer comes back to you; Antimatter keeps neither.
- You call a tool through /mcp/tools, /v1/tools or a hosted agent run.
- 90 days after the call, then swept.
- Erasing the account detaches its calls, which stay only as anonymous measurements until they are swept.
Agent passports
For each agent you gave a passport: its name and description, the endpoints you listed, its public address, where its registration stands on chain (the token, its owner and the transactions), the signed records of what was measured for it, and the feedback other clients gave it on the registry. A record holds counts and sums by day and the hashes of sealed receipts, never a prompt or an answer.
- You open a passport for an agent on the dashboard. From then on it is public at its own address.
- Until you delete the passport, or until the account is erased.
- Delete the passport on the dashboard, or erase the account. A registration on a chain cannot be erased. The token stays on the registry, and its owner can transfer it.
Test suites
Your test cases and their checks, and every run's results: each model's answer to each case, whether it passed, its cost and its latency.
- You create a suite on the Suites page or through /v1/evals.
- Until you delete the suite, or until the account is erased.
- Deleting a suite removes its cases, runs and results. Routing on it stops at once.
Telegram
The recent conversation with the bot: your messages and its replies. A photo you send goes to the model and is not stored. The history notes only that there was one. Also the chat's settings: the image model you picked, whether the cost line shows, and the model and billed cost of the last reply.
- You link a Telegram chat to your account.
- The last 12 messages, each for at most 24 hours after it was sent, and each cut at 8,000 characters. The settings until you unlink.
/newor/unlinkin the chat, or erase the account.
Notification devices
For each device you turn notifications on for: the address its browser's push service gave it, the keys that encrypt what is sent to it, and a label such as "Safari on iPhone".
- You turn notifications on from Billing, in a browser or the installed app.
- Until you turn them off or remove the device, the push service says it is gone, or 8 deliveries in a row fail.
- Turn notifications off, remove the device on Billing, or erase the account.
Shares, saved prompts, presets
What you chose to save or share.
- You save or share it.
- Until you delete or revoke it.
- Delete or revoke it, or erase the account.
Hosted agent runs
A run's conversation: its input, the model's answers, what its tools returned and any picture it made, and your agent's definition. A remote MCP server's headers are kept only encrypted.
- You start a run of one of your agents.
- 30 days after the run ends, then swept.
- Erasure deletes the runs and the definitions.