REST / Gateway
Use REST when you want explicit memory operations. Use the OpenAI-compatible gateway when your client already speaks chat completions or responses APIs.
Scope and capabilities
| Setting | Value |
|---|---|
| Source app | rest or client-specific |
| Default container | jeethendra |
| Default scope | own for agent keys |
| API base | https://edge-api.jithendranara.dev/api/v1 |
| Gateway base | https://edge-api.jithendranara.dev |
Verify key access
curl "https://edge-api.jithendranara.dev/api/v1/stats?container_tag=jeethendra" \
-H "Authorization: Bearer <scoped-key>"
Retain a fact
curl https://edge-api.jithendranara.dev/api/v2/containers/jeethendra/retain \
-H "Authorization: Bearer <scoped-key>" \
-H "Content-Type: application/json" \
-d '{"content":"UnifiedMemory docs are hosted at docs.jithendranara.dev.","source":"rest"}'
Recall memory
curl https://edge-api.jithendranara.dev/api/v2/containers/jeethendra/recall \
-H "Authorization: Bearer <scoped-key>" \
-H "Content-Type: application/json" \
-d '{"query":"Where are the docs hosted?","limit":5,"trust_policy":"balanced"}'
Gateway call
curl https://edge-api.jithendranara.dev/v1/responses \
-H "Authorization: Bearer <scoped-key>" \
-H "Content-Type: application/json" \
-d '{"model":"minimax/MiniMax-M2.7","input":"What should I remember about docs?","memory":{"container_tag":"jeethendra"}}'
Risk notes
- Use scoped keys for clients. Keep admin keys out of application code.
- Do not send raw credentials, cookies, or private logs as memory content.
- If you need deletion/forget behavior, verify the key capability first.