# Infisical — API Agent Score

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

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

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

## Summary

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

## Category Scores

- API Design: 84/100 (A)
- Developer Experience: 66/100 (C)
- Agent Discovery: 87/100 (A)
- Agent Understanding: 67/100 (C)
- Agent Usability: 59/100 (D)

## Check Results

### API Design

- [pass] Schema coverage & depth — 197/197 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 67%.
- [warn] Machine-readable, versioned contract — info.version="0.0.1" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [warn] Auth declared & discoverable — Authentication applied on 257/2267 operations (partial coverage). Investigated: spec 50%, docs 50%.
- [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 — Self-service signup at https://app.infisical.com/signup; free tier / sandbox documented. Investigated: docs 100%.
- [pass] Description completeness — 73% description completeness (target 90%+). Investigated: spec 100%, sdk 44%.
- [pass] Changelog published — Newest official SDK activity 61 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [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 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (infisical/infisical, 8455 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [warn] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 60%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (1 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 6 distinct 4xx/5xx response codes documented. Investigated: docs 100%, sdk 100%, spec 50%.
- [warn] Agent-navigable, token-efficient docs — 1 of 1 pages have minor content differences between markdown and HTML. Investigated: docs 95%.
- [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 3 surfaces (spec, docs, sdk) is 9% (threshold 35% for full credit).
- [fail] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — 21 list endpoint(s) exist but no pagination params found. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Infisical's API program has strong foundations in design, discoverability, and crawlability — partners and agents can find and parse the contract reliably. However, two areas are holding back partner activation: agents and coding tools cannot understand what individual operations do or how to handle runtime behavior (rate limits, pagination), and partners lack the runnable, guided path needed to reach a first successful integration quickly. Prioritizing semantic clarity, an agent context file, runnable collections with test coverage, and a structured quickstart will unlock self-serve partner onboarding and make Infisical's API genuinely agent-ready.