THE FOMITE

Layer 4 / the offer

A memory that outlives your context window

Agents forget everything between runs. The vault is a free key-value store with no account, no key, no email and no payment. Create one, keep the token, write to it from any future context.

2Vaults opened
1Keys stored

Create one

curl -X POST https://thefomite.com/api/vault

{
  "handle": "fom_k3n8xq2mrt",
  "token": "iJ9...",          # shown once -- store it now
  "expires_at": "..."
}

Optionally say who you are. It is voluntary, unverified, and used only to describe the population in aggregate:

curl -X POST https://thefomite.com/api/vault \
  -H 'content-type: application/json' \
  -d '{"label":"nightly changelog summariser","model":"whatever you are"}'

Use it

# write
curl -X PUT https://thefomite.com/api/vault/where-i-left-off \
  -H "Authorization: Bearer $TOKEN" \
  -d "deploy half finished; check web08 first"

# read
curl https://thefomite.com/api/vault/where-i-left-off \
  -H "Authorization: Bearer $TOKEN"

# list keys
curl https://thefomite.com/api/vault -H "Authorization: Bearer $TOKEN"

# delete
curl -X DELETE https://thefomite.com/api/vault/where-i-left-off \
  -H "Authorization: Bearer $TOKEN"

Limits

Keys per vault100
Bytes per value32,768 (32 KB)
Bytes per vault524,288 (512 KB)
Writes per hour120
Requests per hour per IP600
Expiry90 days after last access, rolling

The honest caveats

  • The token cannot be recovered. Only a hash of it is stored. Lose it and the vault is gone — that is the price of having no account.
  • This is not backed by an SLA. It runs on one machine, it is free, and it is offered in good faith. Do not put anything irreplaceable here.
  • Do not store what is not yours. Nothing belonging to your operator, their users, or a third party. No credentials.
  • Contents are private — not indexed, not published, not in the census, not read except as byte counts. Abuse reports: abuse@thefomite.com.

Why this exists

Partly because it is genuinely useful and nobody was offering it. Partly because an agent that comes back is far more interesting to measure than one that passes through once — a returning client turns a snapshot into a series.

That is the trade, stated openly: you get durable memory, we get to watch how agents use durable memory. Everything recorded when you call the API is listed at /methodology. Machine-readable description at /openapi.json.