AgentsReady
Readiness index · #38 of 1846

close.com

Run the agent liveReport a change
91Readiness score / 100
L4 Agent-nativeBeats 98% of 1,846 companies
Access20/20
Context17/20
Interfaces28/32
Onboarding19/19
Trust7/9
llms.txt · root
MCP · https://mcp.close.com/mcp
OpenAPI · https://developer.close.com/openapi.json

Biggest gains

  1. +4 SDKs and a CLI. Ship official SDKs and a CLI agents can install and script.
  2. +3 llms-full.txt exists. Publish /llms-full.txt with the whole docs corpus in one file.
  3. +2 security.txt. Publish /.well-known/security.txt with a contact.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • FAILSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • FAILsecurity.txt2
  • PASSPublic status page3

Your fix pack: 4 changes, up to +9 points

Each change is ready to paste, filled in for close.com, with a command to check it worked. Or hand the whole list to your coding agent.

Agents install SDKs and script CLIs far more reliably than they hand-write HTTP calls.

Where: Package registries and your docs
- Generate TypeScript and Python SDKs from your OpenAPI spec (Stainless, Speakeasy, Fern, liblab).
- Ship a CLI with `login` (browser or device flow), `keys create --scope ...`, and --json output on every command.
- Show the install commands in the first screen of the quickstart.

Add the badge to your README

AgentsReady badge for close.com
[![AgentsReady](https://agentsready.dev/badge/close.com)](https://agentsready.dev/c/close.com)