Rehydrate

POST /v1/rehydrate expands archived memory, compact pointers, or anchor payloads only when the host asks for more evidence.

Use rehydrate when compact context tells the Agent the correct route, but the host needs fuller evidence before execution.

Why Rehydrate Exists

Aionis tries to keep Agent context short. That means some evidence should travel as a pointer:


compact route contract -> rehydrate pointer -> raw evidence only when needed

This prevents large old payloads from entering every prompt while preserving a path back to evidence.

Request


curl -s http://127.0.0.1:3001/v1/rehydrate \
  -H 'content-type: application/json' \
  -d '{
    "tenant_id": "default",
    "scope": "checkout-migration",
    "reason": "The Agent needs the raw verifier note before applying the patch.",
    "memory_ids": ["mem_123"],
    "mode": "partial",
    "include_linked_decisions": true
  }'

SDK


const hints = rehydrateHintsFromGuide(guide);
 
if (hints.length > 0) {
  const evidence = await aionis.rehydrate({
    reason: "Need raw evidence before exact use.",
    memory_ids: hints.map((hint) => hint.memory_id),
    mode: "partial",
    include_linked_decisions: true,
  });
}

Modes

Mode	Use when
`summary_only`	You only need a compact description.
`partial`	You need the most relevant payload and linked decisions.
`full`	You need fuller raw payload.
`differential`	You need an adjudicated comparison or delta.

Target Forms

You can rehydrate by:

Field	Use case
`memory_ids`	Most common guide-derived memory IDs.
`node_ids`	Lower-level node references.
`client_ids`	Client-provided write IDs.
`anchor_id`	Anchor payload reference.
`anchor_uri`	URI-style payload reference.

Boundary

Rehydrate is not a search endpoint. It expands known evidence pointers. If the Agent needs new recall, call /v1/guide or your retrieval backend first.