Is Close agent-ready?

Close scores Band C on The Headless Index and rates AI-Aware on JAIRF (64.3/100). Its strongest area for agent use is headless operation; its weakest is MCP and agent posture.

Does Close publish an OpenAPI spec?

Yes. Close publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.

What is Close's Headless Index score?

Close scores 44/100 on the Headless Index thesis-fit rubric and sits in Band C in the Project & Task Management category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Project & Task Management

Close

Headless Index

44/100

denominator 80

JAIRF

64.3/100

AI-Aware

Verified

MAY 21, 2026

Methodology v1 · JAIRF v1.0.0

Close earns Band C in the Project & Task Management category of The Headless Index, with a thesis-fit score of 44/100 and a JAIRF rating of 64.3/100 (AI-Aware). Its strongest dimension is headless operation (15/20); its weakest scored dimension is MCP and agent posture (0/20). Close publishes a machine-readable OpenAPI specification, which is what lets an agent discover and operate it without human glue code.

Editorial verdict

Close is partially headless and partly UI-led. The Headless Index thesis-fit score of 44/100 puts it mid-table on the index, and JAIRF v1.0.0 puts it at 64.3/100 (Level 2, AI-Aware). 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 Close lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Close is sales CRM for inside sales teams with REST API for leads, contacts, opportunities, activities, custom fields, sequences, and webhooks. SDKs in Python, JavaScript.^[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documented at developer.close.com. OpenAPI references exist; schema discoverability is solid.^[2] 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: Leads, contacts, opportunities, activities, custom fields, sequences, smart views, and webhooks are programmable through REST. The Close dashboard handles sales-team workflows.^[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Close MCP server.^[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: integrators can build agent flows against Close, but the rough edge to plan around is MCP posture^[5]. 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 intent5/20

scored

Close is sales CRM for inside sales teams with REST API for leads, contacts, opportunities, activities, custom fields, sequences, and webhooks. SDKs in Python, JavaScript.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-05-20
+OpenAPI specPublished, 288 operations
·GraphQL endpointDiscovered at https://www.close.com/graphql, introspection disabled or scoped
−SDKs maintainedNone detected in vendor org

cite (3)

openapi.url@2026-05-21
graphql.url@2026-05-21
github.sdks@2026-05-21

Headless operation15/20

scored

Leads, contacts, opportunities, activities, custom fields, sequences, smart views, and webhooks are programmable through REST. The Close dashboard handles sales-team workflows.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-05-20
+API operations exposed288 operations in OpenAPI spec
·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 (8)

openapi.operations_count@2026-05-21
docs.pages_crawled@2026-05-21
docs.pages_crawled@2026-05-21
docs.topics_found.setup@2026-05-21
docs.topics_found.billing@2026-05-21
docs.topics_found.teams@2026-05-21
docs.topics_found.cli@2026-05-21
docs.topics_found.schema@2026-05-21

MCP & agent posture0/20

scored

No first-party Close MCP server.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-05-20
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (3)

mcp.registry_query@2026-05-21
mcp.github_search_query@2026-05-21
github.sdks@2026-05-21

Schema observability15/20

scored

REST documented at developer.close.com. OpenAPI references exist; schema discoverability is solid.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-05-20
+OpenAPIPublished at https://developer.close.com/openapi.json (OpenAPI 3.1.0, 288 operations)
·GraphQL introspectionGraphQL endpoint at https://www.close.com/graphql but introspection is disabled, scoped, or behind authentication

cite (2)

openapi.url@2026-05-21
graphql.url@2026-05-21

Webhooks & eventsUnknown

Unknown

Lead, contact, opportunity, and activity webhooks. Catalog matches inside-sales workflows.

signals (2)

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

cite (1)

docs.pages_crawled@2026-05-21

JAIRF · 6 dimensions

FCFoundational Compliance

55/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility

63.8/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience

69.2/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability

70/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity

70/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability

54.3/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:C band: scores 40-75 range

04 / Embed

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

Calibration

How THI compares to external scorers

Source	Score	Measures	Last checked
Fern Agent Score	not found	Documentation completeness and SDK shape (~22 checks)	—
CLIRank Agent Friendliness	not found	CLI readiness, docs quality, and overall agent affordances	—
Cloudflare Is It Agent Ready?	blocked	Cloudflare's manual agent-readiness heuristic per vendor URL	—
Jentic Scorecard	—	JAIRF-based scorecard requiring a public OpenAPI specification	—

THI 44 vs external median 0

No external scores available to calibrate against.

Peers in Project & Task Management

TrelloC

Headless Index 50/100

TaigaC

Headless Index 52/100

PlaneC

Headless Index 52/100

See full Project & Task Management ranking →

FAQ

Close and agent readiness

Is Close agent-ready?: Close scores Band C on The Headless Index and rates AI-Aware on JAIRF (64.3/100). Its strongest area for agent use is headless operation; its weakest is MCP and agent posture.
Does Close publish an OpenAPI spec?: Yes. Close publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.
What is Close's Headless Index score?: Close scores 44/100 on the Headless Index thesis-fit rubric and sits in Band C in the Project & Task Management category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.