# PDFfiller — API Agent Score

> Score: 62/100 (Grade: C) | Domain: pdffiller.com | Rubric: 1.0.0 | Checked: July 29, 2026

PDFfiller scored 62/100 (C), classified "partially-ready".

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

## Summary

- Overall: 62/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 59/100 (D)
- Developer Experience: 66/100 (C)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 68/100 (C)
- Agent Usability: 56/100 (D)

## Check Results

### API Design

- [warn] Schema coverage & depth — 18/86 (21%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 53%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.pdffiller.com/en/login/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 71/71 operations carry a description. Investigated: sdk 100%.
- [pass] Changelog published — Newest official SDK activity 5 day(s) ago. Investigated: sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [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/developers_pdffiller, 4 snippets). Investigated: docs 100%, sdk 42%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://docs.pdffiller.com/llms.txt, https://docs.pdffiller.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "ProjectException" with 4 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — 1 of 1 pages appear to be client-side rendered SPA shells (root detected); agents using HTTP fetches will see no content. Investigated: docs 57%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [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 — An SDK-wide auto-paginator is present. (grep-derived). Investigated: sdk 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.

## Executive Summary

Pdffiller's API program shows strength in basic reachability and crawlability, but two areas are holding back partner success: the API design lacks visible security and governance practices that partners need to trust the platform, and the program's discoverability and usability for both human developers and AI agents is severely underdeveloped. Prioritize making the API safe, understandable, and executable first — partners and their agents cannot self-serve today without significant friction.