Is Linkup agent-ready?

Linkup scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is webhooks and events.

Does Linkup publish an OpenAPI spec?

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

What is Linkup's Headless Index score?

Linkup scores 56/100 on the Headless Index thesis-fit rubric and sits in Band C 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

Linkup

Headless Index

56/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Linkup earns Band C in the Search & Vector DBs category of The Headless Index, with a thesis-fit score of 56/100. Its strongest dimension is API-first design intent (16/20); its weakest scored dimension is webhooks and events (4/20). No public OpenAPI specification was found when Linkup was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Linkup is partially headless and partly UI-led. The Headless Index thesis-fit score of 56/100 puts it mid-table on 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 are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Linkup lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Linkup is API-only by construction: two endpoints, /v1/search and /v1/fetch, behind a Bearer key at api.linkup.so. An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: The product function is fully headless because search and fetch are all there is. Account management is not: credit top-ups, plan changes and API key creation live in the console (app.linkup.so) with no programmatic equivalent, no CLI and no Terraform provider. That is the standard shape for a small search vendor, and it still means an agent cannot self-provision.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Linkup ships MCP three times over, which is both commitment and confusion: python-mcp-server, js-mcp-server and linkup-mcp-server (github.com/LinkupPlatform/linkup-mcp-server) all sit in the vendor org, none of them dominant, latest commits around June 2026. For a company selling search to agents this is the right instinct, executed without a canonical entry point or registry listing.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Linkup delivers nothing asynchronously. There is no webhook registration endpoint, no documented event types, no signing scheme and no retry semantics; the deep search mode (depth set to deep on /v1/search) simply holds the HTTP connection open longer. For a request and response search API that is coherent, but an agent running long queries has no completion callback. Net assessment: integrators can build agent flows against Linkup, but the rough edge to plan around is webhooks and events^[3]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

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 intent16/20

scored

Linkup is API-only by construction: two endpoints, /v1/search and /v1/fetch, behind a Bearer key at api.linkup.so. The SDK footprint is larger than the surface it wraps, with linkup-sdk on both PyPI and npm (roughly 33,000 weekly npm downloads), a Vercel AI SDK adapter, and LangChain, CrewAI and Dify integrations maintained in the vendor org.

signals (6)

+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 maintained3 (javascript, python, typescript); top by stars: LinkupPlatform/linkup-python-sdk (46 stars)
+SDK recency2 of 3 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-18)
+npm weekly downloads34.7k across published packages; top: linkup-sdk @ 33.4k/week

cite (1)

ai_review_browser.auth@2026-08-19

Headless operation12/20

scored

The product function is fully headless because search and fetch are all there is. Account management is not: credit top-ups, plan changes and API key creation live in the console (app.linkup.so) with no programmatic equivalent, no CLI and no Terraform provider. That is the standard shape for a small search vendor, and it still means an agent cannot self-provision.

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 posture16/20

scored

Linkup ships MCP three times over, which is both commitment and confusion: python-mcp-server, js-mcp-server and linkup-mcp-server (github.com/LinkupPlatform/linkup-mcp-server) all sit in the vendor org, none of them dominant, latest commits around June 2026. For a company selling search to agents this is the right instinct, executed without a canonical entry point or registry listing.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/LinkupPlatform/linkup-mcp-server (29 stars, last commit 72 days ago)
−Community MCP serversNone found
+Agent-friendly SDKs2 TS/JS SDKs available; top: linkup-sdk (33.4k/week downloads)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability8/20

scored

No spec resolves. docs.linkup.so serves narrative pages and code samples, and no OpenAPI document is published at an obvious path (docs.linkup.so/openapi.json returns 404). With only two endpoints the practical cost is small, since a developer can read the search request shape in a minute, but an agent still cannot generate a typed client from a fetch.

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 & events4/20

scored

Linkup delivers nothing asynchronously. There is no webhook registration endpoint, no documented event types, no signing scheme and no retry semantics; the deep search mode (depth set to deep on /v1/search) simply holds the HTTP connection open longer. For a request and response search API that is coherent, but an agent running long queries has no completion callback.

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:C band: scores 40-75 range

04 / Embed

Show Linkup'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

Redis VectorC

Headless Index 55/100

TypesenseC

Headless Index 58/100

OpenSearchC

Headless Index 54/100

See full Search & Vector DBs ranking →

FAQ

Linkup and agent readiness

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