This document gives a compact overview of the HTTP surface of the ANDB v1 prototype. The authoritative route list is Gateway.RegisterRoutes in src/internal/access/gateway.go (25 path registrations). A tabular summary also lives in the root README.md.
Detailed endpoint behavior is documented in:
docs/api/admin.mddocs/api/ingest.mddocs/api/query.md
By default the server listens on:
http://127.0.0.1:8080
This can be overridden with the ANDB_HTTP_ADDR environment variable.
Health
GET /healthz
Core (documented in ingest/query docs)
POST /v1/ingest/eventsPOST /v1/query
Admin (see docs/api/admin.md; unauthenticated in default dev — do not expose publicly)
GET /v1/admin/topologyGET /v1/admin/storagePOST /v1/admin/s3/exportPOST /v1/admin/s3/snapshot-exportPOST /v1/admin/dataset/deletePOST /v1/admin/dataset/purge
Canonical object CRUD (GET list / filter + POST create or replace per resource)
/v1/agents,/v1/sessions,/v1/memory,/v1/states,/v1/artifacts,/v1/edges,/v1/policies,/v1/share-contracts
Proof traces
GET /v1/traces/{object_id}
Internal — Agent SDK algorithm bridge (POST only)
/v1/internal/memory/recall,/v1/internal/memory/ingest,/v1/internal/memory/compress,/v1/internal/memory/summarize,/v1/internal/memory/decay,/v1/internal/memory/share,/v1/internal/memory/conflict/resolve
Current JSON endpoints expect:
- request
Content-Type: application/json - JSON response bodies
The current prototype uses path-based versioning for API routes:
/v1/...
Health routes are currently unversioned.
The current API layer is intentionally small. Its job in v1 is to stabilize:
- ingest request shape
- query request shape
- response categories for structured evidence
It is not yet a full production API with authentication, pagination, rate limiting, or comprehensive admin surfaces. In particular, /v1/admin/* has no API-key or token check in the stock server; use network isolation or a reverse proxy for production.