API and OpenAPI specification
The Neotoma REST API is defined in the OpenAPI spec. The table below lists each endpoint and the capability it provides.
The API is designed around deterministic state operations: store structured observations, retrieve snapshots with provenance, and manage typed relationships explicitly.
Minimal request examples
# Store structured entities
curl -X POST http://localhost:3080/store \
-H "Content-Type: application/json" \
-d '{"entities":[{"entity_type":"task","title":"Review schema changes","status":"open"}]}'
# Query entities
curl -X POST http://localhost:3080/entities/query \
-H "Content-Type: application/json" \
-d '{"filters":{"entity_type":"task"},"limit":10}'
# Retrieve snapshot with provenance
curl -X POST http://localhost:3080/get_entity_snapshot \
-H "Content-Type: application/json" \
-d '{"entity_id":"<entity_id>"}'Authentication requirements differ by endpoint and deployment mode. Local development workflows often run without OAuth while hosted or shared environments should enforce authenticated access.
Continue with schema management, data model walkthrough, and architecture.