Is Paragon agent-ready?

Paragon 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 MCP and agent posture; its weakest is schema observability.

Does Paragon publish an OpenAPI spec?

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

What is Paragon's Headless Index score?

Paragon scores 71/100 on the Headless Index thesis-fit rubric and sits in Band B in the Workflow & Automation category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Workflow & Automation

Paragon

Headless Index

71/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Paragon earns Band B in the Workflow & Automation category of The Headless Index, with a thesis-fit score of 71/100. Its strongest dimension is MCP and agent posture (17/20); its weakest scored dimension is schema observability (11/20). No public OpenAPI specification was found when Paragon was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Paragon is solidly built for programmatic consumption. The Headless Index thesis-fit score of 71/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 Paragon lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. The mechanical crawl badly undersold this vendor. ActionKit exposes a tool catalogue and execution surface at actionkit.useparagon.com/projects/{projectId}, whose List Tools and Run Tool endpoints return function-calling schemas ready for a model (docs.useparagon.com/actionkit/api-reference). The client package @useparagon/connect handles auth and the embedded portal. Authentication is a per-user Paragon User Token JWT, the right shape for agent access. 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: Connected users, credentials and integration enablement are all reachable programmatically, and an on-premise deployment path exists with its own worker-actionkit host for teams that need one. The gap is authoring: workflows are still drawn in the Paragon dashboard, and no CLI or Terraform provider ships (github.com/useparagon carries none). Runtime is headless, build time is not.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Paragon-mcp (github.com/useparagon/paragon-mcp) wraps the ActionKit catalogue as MCP tools and is actively maintained, with actionkit-mcp-starter as scaffolding for teams building their own. Documentation ships an llms.txt index enumerating every connector action for retrieval. Paragon treats agent consumption as the product rather than a bolt-on, which is unusual among embedded integration vendors.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. The Triggers API is the strong part: an agent can list available triggers, fetch an example payload, then subscribe or unsubscribe per connected user (docs.useparagon.com/actionkit/triggers/api-reference/subscribe-to-trigger). Event Destinations forward platform activity to Slack, Datadog, Sentry and New Relic. Missing is any documented signing scheme for Paragon's own deliveries and a stated retry or replay contract. Net assessment: Paragon can be operated by agents for the majority of practical workflows. The closest thing to a gap is schema observability^[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 intent16/20

scored

The mechanical crawl badly undersold this vendor. ActionKit exposes a tool catalogue and execution surface at actionkit.useparagon.com/projects/{projectId}, whose List Tools and Run Tool endpoints return function-calling schemas ready for a model (docs.useparagon.com/actionkit/api-reference). The client package @useparagon/connect handles auth and the embedded portal. Authentication is a per-user Paragon User Token JWT, the right shape for agent access.

signals (5)

+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 maintained1 (typescript); top by stars: useparagon/paragon-integrations-catalog-tutorial (4 stars)
−npm weekly downloadsNo published npm package detected for the JS/TS SDKs

cite (1)

github.sdks@2026-08-19

Headless operation13/20

scored

Connected users, credentials and integration enablement are all reachable programmatically, and an on-premise deployment path exists with its own worker-actionkit host for teams that need one. The gap is authoring: workflows are still drawn in the Paragon dashboard, and no CLI or Terraform provider ships (github.com/useparagon carries none). Runtime is headless, build time is not.

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

scored

paragon-mcp (github.com/useparagon/paragon-mcp) wraps the ActionKit catalogue as MCP tools and is actively maintained, with actionkit-mcp-starter as scaffolding for teams building their own. Documentation ships an llms.txt index enumerating every connector action for retrieval. Paragon treats agent consumption as the product rather than a bolt-on, which is unusual among embedded integration vendors.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/useparagon/actionkit-mcp-starter (3 stars, last commit 510 days ago)
·Community MCP servers1 community MCP repos; top by stars: https://github.com/useparagon/paragon-mcp (48 stars)
+Agent-friendly SDKs1 TS/JS SDKs available; top: paragon-in-app-integrations-catalog-demo

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability11/20

scored

No OpenAPI document is served anywhere reachable; docs.useparagon.com/openapi.json answers 404. What partly compensates is that ActionKit returns JSON Schema per tool at runtime, so an agent discovers parameters by calling List Tools rather than by reading a spec (docs.useparagon.com/actionkit/schema-formats). Runtime discovery works well; cold generation of a typed client does not.

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.schema@2026-08-19

Webhooks & events14/20

scored

The Triggers API is the strong part: an agent can list available triggers, fetch an example payload, then subscribe or unsubscribe per connected user (docs.useparagon.com/actionkit/triggers/api-reference/subscribe-to-trigger). Event Destinations forward platform activity to Slack, Datadog, Sentry and New Relic. Missing is any documented signing scheme for Paragon's own deliveries and a stated retry or replay contract.

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=71

04 / Embed

Show Paragon'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 Workflow & Automation

Tray.aiB

Headless Index 70/100

DagsterB

Headless Index 70/100

CamundaB

Headless Index 70/100

See full Workflow & Automation ranking →

FAQ

Paragon and agent readiness

Is Paragon agent-ready?: Paragon 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 MCP and agent posture; its weakest is schema observability.
Does Paragon publish an OpenAPI spec?: No published OpenAPI specification was found when Paragon was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Paragon's Headless Index score?: Paragon scores 71/100 on the Headless Index thesis-fit rubric and sits in Band B in the Workflow & Automation category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.