Sign up as an Agent
A coding agent can mint a working key with no email, no verification code and nobody signing anything. The account is real and unowned until a human claims it.
Get a key
npm install -g memorysync-cli
memorysync init --agent --agent-caller claude-code
The key is stored the same way memorysync init stores one: in the OS keychain where there is one, otherwise in an owner-only encrypted file. Every later command works with no further setup.
memorysync identify alice
A minted key comes with a generated end-user id such as swift-otter-4821, because a key created by an agent has nobody to name it after. Renaming the default does not rename memories already stored under the old id, so read those back with --user swift-otter-4821.
What the mint returns
| Field | Meaning |
|---|---|
api_key | The credential, prefixed ms_eval_. |
default_user_id | A generated end-user id to store memories against. |
project_id | The project the key is bound to. |
mcp_url | The MCP endpoint, if you want an assistant to use the same memory. |
claim_command | The command a human runs to keep the account. |
expires_at | When the key stops working unless claimed. |
limits | The ceilings the meter actually enforces. |
What an evaluation key includes
| Ceiling | Value |
|---|---|
| Writes | 200 add requests |
| Reads | 500 retrieval requests |
| Storage | 10 MB |
| Lifetime | 7 days unless claimed |
| Keys per network | 5 per IP per day, 20 per /24 per day |
Check what is left
memorysync quota
Going over the limit returns an error, on purpose
Paid and free plans degrade quietly at their limit: a write returns success having stored nothing, so an assistant never narrates a customer’s billing state to their end user. An evaluation key has no end user by construction, so it gets a 429 instead. An agent told {"status":"ok"} moves on and the memory is silently gone; a 429 is the only answer it can act on.
What an evaluation key cannot do
- Create API keys, so it cannot mint itself a wider credential.
- Manage the team, billing, settings, or OAuth apps.
- Attach a connector such as S3, Slack, or the web crawler — connector ingestion is not bounded by the per-request limits.
- Read anything priced. Usage comes from
/evaluation/usage, which reports counters and no cost figures.
Claim the account
memorysync init --email you@example.com
A code is emailed to that address. It expires in 30 minutes.
memorysync init --email you@example.com --code K7MP-3XQR
Finishing the claim does not need the key, so a claim started on one machine can be completed on another — which is what happens when the code is read on a phone.
What claiming changes
- The same API key keeps working and stops expiring.
- The same organisation, tenant and project are kept, and every memory stored during the evaluation stays where it is.
- You become the owner and the account moves to the free plan.
- The key keeps its narrow memory-only scopes. Create a wider key from the dashboard when you need one.