# Pipedrive — API Agent Score

> Score: 74/100 (Grade: B) | Domain: pipedrive.com | Rubric: 1.0.0 | Checked: July 24, 2026

Pipedrive scored 74/100 (B), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/pipedrive)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 74/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 100/100 (A+)
- Developer Experience: 75/100 (B)
- Agent Discovery: 67/100 (C)
- Agent Understanding: 79/100 (B)
- Agent Usability: 56/100 (D)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — OpenAPI 3.0.1 declared (3.0.x; 3.1 adds JSON Schema 2020-12 alignment but is not required for full credit). Investigated: spec 100%, docs 100%.
- [pass] Schema coverage & depth — 291/291 (100%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%, spec 83%.
- [pass] Auth declared & discoverable — authentication documented in the docs site at https://pipedrive.readme.io/docs/core-api-concepts-authentication. Investigated: spec 100%, docs 100%, wellknown 0%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.pipedrive.com/en/register (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Description completeness — 93% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — changelog documented in the docs site at https://developers.pipedrive.com/changelog. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developers.pipedrive.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/pipedrive_readme_io, 592 snippets). Investigated: docs 100%, sdk 92%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — 1 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.pipedrive.com/llms.txt, https://developers.pipedrive.com/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 7 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%, sdk 0%.
- [pass] Operation purpose clarity — 99% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 57%.
- [warn] Docs structured data — OpenGraph/meta tags only across 1 assessed pages — no JSON-LD for answer engines to cite. Investigated: docs 50%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 26 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — sandbox documented in the docs site at https://developers.pipedrive.com/sandbox. Investigated: spec 100%, docs 100%, sdk 50%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Pipedrive's API program shows strength in core design and documentation structure, but two areas are holding back partner and agent success: agents lack the context files and runnable examples they need to integrate reliably, and operational reliability signals (idempotency, rate-limit handling) are underdocumented — creating integration risk for partners building production workflows. Prioritize giving agents an executable, trustworthy context layer first, then close the reliability documentation gaps to reduce partner support burden and failed integrations.