◎ Discry Score
pipedrive.com
crm · API
D
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 89 (B)
Discry your API →
CRM · RANK #7 OF 13

Pipedrive is Poor to agents.

Discry independently scored how well an AI agent can discover and understand the Pipedrive API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 45/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Pass
llms.txtAn llms.txt index that points agents to the docs that matter.Fail
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Partial
SitemapA sitemap so agents can enumerate the docs surface.Pass

Comprehension

55% of score · 50/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Partial
Realistic examplesRunnable, real-world request/response examples.Partial
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Partial
Error-recovery guidanceDocumented failure modes and how to recover from them.Partial
Answer-first formatThe answer leads; preamble does not bury it.Partial
Capability boundariesClear limits — what the API can and cannot do.Partial
Naming consistencyConsistent, predictable naming across endpoints.Partial
Heading hierarchyClean heading structure agents can navigate.Partial
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Partial
Token efficiencyDocs are concise enough to fit an agent context window.Partial

What we found

  • Pipedrive's robots.txt is minimal (just wildcard allow + sitemap reference) with no AI-specific directives — neither blocking nor explicitly welcoming agents.
  • OpenAPI specs are publicly available for both v1 and v2 APIs (openapi.yaml and openapi-v2.yaml) and directly linked from the API reference page — easy for agents to discover.
  • Strong MCP ecosystem presence with servers on Smithery, Glama, and PulseMCP — community-built but well-maintained.
  • No llms.txt, llms-full.txt, or AGENTS.md exists — agents must rely entirely on the OpenAPI spec or scraping HTML docs for API understanding.
  • The sitemap is comprehensive with detailed changelog and documentation URLs, but documentation pages are JavaScript-rendered with limited markdown parseability.

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Add llms.txt covering the core Pipedrive API concepts (deals, persons, organizations, activities, pipelines) with descriptions and links.
  2. 02Add explicit AI bot directives to robots.txt to signal openness to agent crawling.
  3. 03Add AGENTS.md to the pipedrive/client-nodejs or pipedrive/client-php repos.
  4. 04Create llms-full.txt combining key API reference content into markdown.
  5. 05Add markdown delivery option for API documentation pages to improve LLM parseability.

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

API token (query parameter)OAuth2✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

API token authentication via query parameter or OAuth2 for marketplace apps. JSON error responses with success flag and error message. Rate limits documented (per plan tier). Cursor-based and offset pagination supported. No idempotency key mechanism documented.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free