Reference
Relata DB 3.0
Parts of this page still describe the 2.x line, which is kept in the 2.5.8 documentation snapshot. In 3.0 HTTP routes are under
/v1/, the compatibility protocol doors (Postgres, Mongo, Redis, Neo4j, ClickHouse, S3, Flight, SPARQL) are retired, and clustering and multi-tenancy are Enterprise. See What is new in 3.0 and HTTP route restructure.Complete API and protocol reference for RelataDB.
In this section
Query languages
- SQL Reference — full SQL grammar, operators, and temporal extensions
- Cypher & SQL-PGQ — graph pattern matching over the link store
- SPARQL — RDF-style triple queries over the knowledge graph
- GraphQL — GraphQL query subset with server-side variable binding
- Graph Analytics — GDS-style algorithms (PageRank, communities, paths)
- Query Cookbook — worked recipes across the query surface
Retrieval & time
- Search & Retrieval — BM25 full-text, vector, and hybrid search
- Vector Index Parameters — HNSW/DiskANN/IVF tuning knobs
- Bi-temporal Queries — AS OF valid-time and system-time queries
- Branching & Namespaces — isolated query/write branches
- Agent Memory — memory verbs for AI agents
Platform
- HTTP API — the full REST route table
- MCP — Model Context Protocol tools and memory verbs
- HTTP route restructure (/v1) — the 3.0 route migration, renames and removals
- Protocols — the interfaces served in 3.0 (HTTP/JSON, GraphQL, MCP, A2A) and the retired wire protocols
- Error Codes — typed errors and RFC 9457 problem details
- Environment Variables — all configuration knobs
- Limits — the honest, code-verified picture of what works
- Performance Tuning — caches, spill, and query budgets
- Editions and Limits - open edition versus Relata Enterprise DB