Quickstart

1. Sign in and get a key

Sign in to the Hunta console. Every account gets its own isolated memory store (the Solo tier is free for one seat, no card).

Mint a key from the Keys page. Two kinds matter:

• An agent key is scoped to propose and recall. An agent holding it can suggest memories and read sealed facts, but can never write canon directly. This is the key you give to harnesses.
• An owner key carries write scope for direct writes. Keep it for yourself and for trusted tooling.

2. Write and recall

export GATHER_URL=https://mcp.hunta.ai
export GATHER_TOKEN=<your-key>

# write a memory
curl -sS -X POST "$GATHER_URL/v1/memories" \
  -H "Authorization: Bearer $GATHER_TOKEN" -H "Content-Type: application/json" \
  -d '{"text":"Our design partner is Acme Corp."}'

# recall it (sealed facts only, with provenance)
curl -sS -X POST "$GATHER_URL/v1/memories/search" \
  -H "Authorization: Bearer $GATHER_TOKEN" -H "Content-Type: application/json" \
  -d '{"query":"design partner","limit":5}'

With an agent key, the write lands as a candidate in your staging queue instead of going straight to canon. You review and promote candidates in the console (Queue), or set curation policy to automate it. Recall never returns unreviewed candidates.

3. Prove the isolation

curl -sS -X POST "$GATHER_URL/v1/admin/verify-isolation?nonce=my-first-proof" \
  -H "Authorization: Bearer $GATHER_TOKEN" > receipt.json

npx -y @hunta/verify receipt.json

This runs live adversarial probes against your tenant boundary and returns an Ed25519-signed receipt, then verifies it against Hunta's published key. See Verify the attestation for what the probes mean and how the trust model works.

Next

• Connect over MCP so your agents use memory as a native tool.
• Install the Claude Code plugin for auto-recall on every prompt.
• Create a Tribe to share one attested store with your team.