# Paragon — API Agent Score

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

Paragon scored 72/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 72/100 (B)
- Developer Experience: 54/100 (D)
- Agent Discovery: 76/100 (B)
- Agent Understanding: 83/100 (A)
- Agent Usability: 71/100 (B)

## Check Results

### API Design

- [warn] Schema coverage & depth — 11 of 361 public signatures use loose types (anyTypeRatio=0.030). Investigated: sdk 91%.
- [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] Quickstart present — Quickstart at https://docs.useparagon.com/getting-started/installing-the-connect-sdk with a runnable first-call sample. Investigated: docs 100%.
- [warn] Description completeness — 69/148 operations lack a description. Investigated: sdk 53%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 0/1 sitemap doc pages (0%); 1 missing. Investigated: docs 50%, sdk 0%.
- [warn] Registry & SDK presence — No official SDKs discovered via npm, PyPI, or GitHub. Investigated: sdk 50%, docs 0%, cli 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "BaseSDKError" with 49 subclasses. Investigated: sdk 100%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [pass] Docs structured data — JSON-LD Article markup on 20/20 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 8% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [warn] Pagination documented & consistent — Only 2/12 list method(s) return an auto-paginating iterable; 10 return a raw page. Investigated: sdk 17%.
- [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

Useparagon's API program shows strength in agent understanding and discovery fundamentals, but two areas are holding back partner outcomes: developer onboarding is slow and self-serve (partners cannot get hands-on without friction), and agents lack the runnable context and structured instructions they need to integrate reliably. Prioritize closing the onboarding gap and establishing executable, agent-ready artifacts first — these directly determine whether partners and their AI agents can reach a first successful integration without a sales conversation or support escalation.