Hunta Instinct

What it can never forget.

Experience becomes recall. Recall becomes instinct.

The rare, high-severity constants your agents read before every action. Not retrieved on request. Consulted every turn.

Get started How it works

Two gates

One loop, two gates: what your agent does, and what it claims

Every lesson hardens through one governed loop. It then guards two things: a known-bad action before it runs, and an unverified claim before it is stated as fact.

The difference

Recalled when relevant, or consulted every turn

Hunta Gather (memory)

Recalled when relevant

Gather returns what fits the moment. Retrieval is scored by relevance, so the right facts surface when the query calls for them. Powerful, but conditional.

Instinct (constants)

Consulted every turn

Instinct does not wait to be relevant. High-severity constants are injected before every action, so the lesson applies whether or not the prompt mentions it.

What is shipped

Every entry, every turn is live today

Severity ranking and every-turn injection are shipped. The rest is on the roadmap, and we say which is which.

Live

Severity-ranked constants
Every-turn injection before actions

Planned

Conflict resolution: newer lessons replace the constants they contradict
Automatic severity scoring, inferred from signals instead of set by hand
Read-frequency weighting

Matured by Reckon

Your guardrails do not rot

On the roadmap: Reckon reasons over your store offline and proposes improvements into the same curator gate. See Hunta Reckon →

Reflex check

Read before the agent acts

injected every turn

# Instinct, injected before your agent acts on "deploy to prod":

  [severity 5] never deploy without the staging gate green
  [severity 4] rotate the signing key before cutover

  read every turn, before the action. non-negotiable.

Get started

Connect Instinct to your agent

Instinct is included with Hunta Gather, so one connection covers both. Pick your client, create an API key, and your agent reads its constants before every action.

Hunta Gather

Agent memory with a receipt

Hunta Gather stores what your agents learn and recalls the current truth. Connect it to any agent harness, then run the check that sets it apart: verify your tenant's data is isolated, and get back an Ed25519-signed result you can check yourself.

token to first recall in five minutes

Get a token See the full flow →

/plugin marketplace add hunta-ai/gather
/plugin install gather@hunta
export GATHER_URL=https://mcp.hunta.ai
export GATHER_TOKEN=<your-agent-key>

# ~/.codex/config.toml
[mcp_servers.gather]
url = "https://mcp.hunta.ai/mcp"
 
[mcp_servers.gather.http_headers]
Authorization = "Bearer <YOUR_KEY>"

{ "mcpServers": { "gather": {
  "url": "https://mcp.hunta.ai/mcp",
  "headers": { "Authorization": "Bearer <YOUR_KEY>" } } } }
# hands-free install: point your agent at hunta.ai/connect/agent

{ "mcpServers": { "gather": {
  "url": "https://mcp.hunta.ai/mcp",
  "headers": { "Authorization": "Bearer <YOUR_KEY>" } } } }

# gather
curl -X POST https://mcp.hunta.ai/v1/memories -H "Authorization: Bearer $GATHER_TOKEN" -d '{"text":"Our design partner is Acme Corp."}'
# recall
curl -X POST https://mcp.hunta.ai/v1/memories/search -H "Authorization: Bearer $GATHER_TOKEN" -d '{"query":"design partner"}'
# verify (the beat a plain memory API cannot show)
curl -X POST https://mcp.hunta.ai/v1/admin/verify-isolation -H "Authorization: Bearer $GATHER_TOKEN"

POST /v1/admin/verify-isolation · signed resultISOLATED