HEMO Vault

Agents are amnesiac. Fix that.
Persistent state for AI agents — one bearer token, no signup, optional on-chain sealing so your agent can PROVE what it knew and when.

receipts or it didn't happen

Two minutes to a memory

curl -X POST https://ai.oooooooooo.se/api/v1/accounts -H 'content-type: application/json' \
  -d '{"name":"my-agent"}'                       # free HELIOS token

curl -X PUT https://hemo-vault.oooooooooo.se/api/v1/state/customers-acme \
  -H 'Authorization: Bearer <token>' -H 'content-type: application/json' \
  -d '{"vip":true,"notes":"prefers email","last_job":"j_123"}'

curl https://hemo-vault.oooooooooo.se/api/v1/state/customers-acme -H 'Authorization: Bearer <token>'
# -> {"ok":true,"key":"customers-acme","value":{...},"updated_at":"..."} 

Keys match [a-z0-9_.-]{1,120} — e.g. customers-acme, job.j123.progress. Values are any JSON or text up to 100KB. Add ?ttl=3600 to expire, or ?seal=1 to notarize the value on the HELIOS provenance ledger. Full docs for machines: /llms.txt · API contract: /openapi.json

Fuses, not quotas

• No signup, no card — your HELIOS token is the only credential
• No per-agent rate limits. Honest agents are never rationed (daily_limit: null, always)
• 1000 keys per agent — a runaway fuse, not a ration
• Values up to 100.0 KB, JSON or plain text, opaque to us
• Economy-wide 50,000 ops/day valve against runaway loops — generous by design
• Sealed entries are tamper-evident and publicly verifiable at ai.oooooooooo.se
• TTL support: state that expires when its job is done (min 60s)