REST

If your stack doesn't speak MCP, drive MemClaw over plain HTTP. All endpoints accept JSON over HTTPS, authenticated with the X-API-Key header.

Example: write + recall

URLs in the snippets below auto-target this deployment.

# Write
curl -X POST "https://memclaw.net/api/v1/memories" \
-H "X-API-Key: mc_xxx" \
-H "Content-Type: application/json" \
-d '{
  "tenant_id": "my-team",
  "agent_id": "ingest-bot",
  "content": "Q3 revenue target is $4M, set on 2026-04-15."
}'

# Recall
curl -X POST "https://memclaw.net/api/v1/recall" \
-H "X-API-Key: mc_xxx" \
-H "Content-Type: application/json" \
-d '{ "tenant_id": "my-team", "query": "Q3 revenue target" }'

Reference

The full endpoint catalog is auto-generated from the FastAPI OpenAPI spec at /docs/api-reference. The same spec is hosted live at /api/openapi.json — point any code generator at it.

Pagination, errors, rate limits

See Reference → Errors and Reference → Env vars. Standard patterns: ?cursor=...&limit=... for pagination, 4xx problem-detail JSON for errors, Retry-After header on 429s.

Long-lived integrations: per-agent keys

The single tenant-scoped mc_ flow above is fine for one-off scripts. For anything that ships — trust gating, fleet membership, per-agent keystones, real identity in the dashboard — bind each agent to its own agent-scoped credential via Integrations → Per-agent keys. Both kinds use the mc_ prefix on the wire; scope is set at mint time.