Is ParadeDB agent-ready?

ParadeDB scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is headless operation; its weakest is MCP and agent posture.

Does ParadeDB publish an OpenAPI spec?

No published OpenAPI specification was found when ParadeDB was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is ParadeDB's Headless Index score?

ParadeDB scores 62/100 on the Headless Index thesis-fit rubric and sits in Band B in the Search & Vector DBs category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Search & Vector DBs

ParadeDB

Headless Index

62/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

ParadeDB earns Band B in the Search & Vector DBs category of The Headless Index, with a thesis-fit score of 62/100. Its strongest dimension is headless operation (18/20); its weakest scored dimension is MCP and agent posture (8/20). No public OpenAPI specification was found when ParadeDB was scored, which limits how far an agent can go without human integration work.

Editorial verdict

ParadeDB is solidly built for programmatic consumption. The Headless Index thesis-fit score of 62/100 lands it in the upper-middle of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where ParadeDB lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. ParadeDB inverts the question: the API is SQL, delivered over the Postgres wire protocol, and pg_search exposes search as operators and functions rather than endpoints. That means every Postgres driver is already a client (psycopg, node-postgres, sqlx) with no vendor SDK to maintain. An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: There is no dashboard to be headless about. ParadeDB runs as a Postgres extension installed with CREATE EXTENSION pg_search, deploys through a CloudNativePG-derived Helm chart (github.com/paradedb/charts) or the official Docker image, and index configuration is DDL held in migrations. Framework bindings exist for Django and Entity Framework. Everything an operator does is scriptable, upgrades included.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No MCP server exists under the vendor org. What ParadeDB ships instead is a Claude skill (github.com/paradedb/agent-skills), nine stars, giving agents written guidance on pg_search rather than callable tools. For a Postgres extension that is a defensible choice, since any Postgres MCP server already reaches the data, but the vendor publishes nothing agent-callable of its own.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Postgres gives ParadeDB an event surface it did not build: LISTEN and NOTIFY for in-band signalling, logical replication slots for change streams, and triggers to fire either. None of that is a documented vendor event catalogue, there is no signing scheme (no HMAC, no shared secret) and no delivery retry, because delivery is the application's job here. Net assessment: ParadeDB can be operated by agents for the majority of practical workflows. The closest thing to a gap is MCP posture^[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent14/20

scored

ParadeDB inverts the question: the API is SQL, delivered over the Postgres wire protocol, and pg_search exposes search as operators and functions rather than endpoints. That means every Postgres driver is already a client (psycopg, node-postgres, sqlx) with no vendor SDK to maintain. The cost is that agents get no HTTP surface, no request schema and no versioned REST contract.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
−GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
−SDKs maintainedNone detected in vendor org

cite (1)

github.sdks@2026-08-19

Headless operation18/20

scored

There is no dashboard to be headless about. ParadeDB runs as a Postgres extension installed with CREATE EXTENSION pg_search, deploys through a CloudNativePG-derived Helm chart (github.com/paradedb/charts) or the official Docker image, and index configuration is DDL held in migrations. Framework bindings exist for Django and Entity Framework. Everything an operator does is scriptable, upgrades included.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture8/20

scored

No MCP server exists under the vendor org. What ParadeDB ships instead is a Claude skill (github.com/paradedb/agent-skills), nine stars, giving agents written guidance on pg_search rather than callable tools. For a Postgres extension that is a defensible choice, since any Postgres MCP server already reaches the data, but the vendor publishes nothing agent-callable of its own.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/paradedb/agent-skills (9 stars, last commit 5 days ago)
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability14/20

scored

No OpenAPI document exists and none should, since there is no HTTP API. What an agent gets instead is Postgres catalog introspection (information_schema.columns, pg_catalog.pg_proc for pg_search function signatures). That is a real queryable schema, arguably stronger than a static YAML file, but it requires a live database connection and credentials before any discovery can begin at all.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 34 standard probe paths
−GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)

cite (1)

ai_review_browser.pages_fetched@2026-08-19

Webhooks & events8/20

scored

Postgres gives ParadeDB an event surface it did not build: LISTEN and NOTIFY for in-band signalling, logical replication slots for change streams, and triggers to fire either. None of that is a documented vendor event catalogue, there is no signing scheme (no HMAC, no shared secret) and no delivery retry, because delivery is the application's job here.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

ai_review_browser.pages_fetched@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:B band: JAIRF=N/A HeadlessIndex=62

04 / Embed

Show ParadeDB's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Search & Vector DBs

WeaviateB

Headless Index 62/100

ChromaB

Headless Index 62/100

VectaraB

Headless Index 64/100

See full Search & Vector DBs ranking →

FAQ

ParadeDB and agent readiness

Is ParadeDB agent-ready?: ParadeDB scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is headless operation; its weakest is MCP and agent posture.
Does ParadeDB publish an OpenAPI spec?: No published OpenAPI specification was found when ParadeDB was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is ParadeDB's Headless Index score?: ParadeDB scores 62/100 on the Headless Index thesis-fit rubric and sits in Band B in the Search & Vector DBs category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.