EdgeDB REST API
EdgeDB REST API enables agents to query and mutate a graph-relational database using EdgeQL or SQL over HTTP, with strong type safety, schema migrations, and automatic link traversal replacing manual joins.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS enforced by default in EdgeDB Cloud and recommended for self-hosted. Secret key auth is simple but lacks fine-grained scope control. Role-based access exists but is less granular than enterprise RBAC. Self-hosted operators are responsible for TLS certificate management and network isolation.
⚡ Reliability
Best When
An agent works with richly interlinked domain objects and benefits from schema-enforced type safety and automatic join resolution without writing complex SQL.
Avoid When
The agent needs maximum raw query throughput, pure SQL compatibility, or relies on a mature ecosystem of third-party tooling.
Use Cases
- • Execute EdgeQL queries that traverse object links without writing explicit JOINs, making relationship-heavy data retrieval simpler for agents
- • Run schema migrations programmatically to evolve data models during agent-driven application scaffolding or test setup
- • Perform deeply nested object mutations in a single query where traditional SQL would require multiple INSERT/UPDATE statements
- • Query type-safe data models where the schema enforces constraints, reducing the validation burden on agent-generated queries
- • Use the built-in HTTP query endpoint to run ad-hoc EdgeQL from agents without a language-specific driver
Not For
- • High-throughput analytics workloads — EdgeDB is OLTP-focused and not optimized for columnar scan performance at ClickHouse or TimescaleDB scale
- • Teams committed to standard SQL who do not want to learn EdgeQL syntax and abstractions
- • Workloads requiring a battle-tested, decade-old ecosystem — EdgeDB is newer and its managed cloud and community are still maturing
Interface
Authentication
EdgeDB Cloud uses secret keys (long-lived tokens) for programmatic access. Self-hosted EdgeDB supports TLS client certificates and password-based role auth. The HTTP query endpoint requires a valid token passed via Authorization header. Role-based access control is available but coarser than enterprise RBAC systems.
Pricing
EdgeDB server is open-source (Apache 2). EdgeDB Cloud is the managed offering. Self-hosted deployment is fully free with no feature gating. Cloud free tier does not require a credit card.
Agent Metadata
Known Gotchas
- ⚠ EdgeQL is not SQL — agents trained on SQL must use EdgeQL syntax; the learning curve is non-trivial and LLM-generated EdgeQL may contain syntax errors not present in SQL equivalents
- ⚠ The HTTP query endpoint only accepts POST requests with JSON body containing 'query' and optional 'variables' fields; GET requests are not supported for queries
- ⚠ Schema migrations must be applied before queries that reference new schema elements; agents attempting to query un-migrated schemas receive type errors that can be confusing
- ⚠ Links in EdgeQL are traversed with dot notation (User.posts.title) but are not automatically fetched — agents must explicitly SHAPE queries to include nested objects or receive empty sets
- ⚠ EdgeDB Cloud instances can cold-start after inactivity on free tier; agents should implement connection retry logic with exponential backoff for the first request after a cold start
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for EdgeDB REST API.
Scores are editorial opinions as of 2026-03-06.