# llms.txt — API Agent Score

> Score: 50/100 (Grade: D) | Domain: llmstxt.org | Rubric: 1.0.0 | Checked: November 10, 2026

llms.txt scored 50/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 50/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 40/100 (F)
- Agent Discovery: 87/100 (A)
- Agent Understanding: 69/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Security & governance hygiene — No security.txt found at /.well-known/security.txt or /security.txt, so there's no machine-readable security contact for agents or researchers. Investigated: wellknown 0%.
- [fail] Example coverage — No code samples detected across 3 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — 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

- [fail] Self-service developer portal — No self-service signup detected — no signup link on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved — so an agent can't onboard on its own. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [fail] Code samples in docs — No code samples detected across 3 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (llmstxt/llmstxt_llms_txt, 51 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 3/7 sitemap doc pages (43%); 4 missing — Missing: https://llmstxt.org/core.html, https://llmstxt.org/domains.html, https://llmstxt.org/nbdev.html, https://llmstxt.org/changes.html. Investigated: docs 76%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/9 pages return markdown). Investigated: docs 75%.
- [pass] Crawlable / AEO — robots.txt lets all monitored AI crawlers reach the docs paths. Investigated: wellknown 100%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 8/9 pages support .md URLs (89%); inconsistent support. Investigated: docs 95%.
- [warn] Docs structured data — Only OpenGraph/meta tags across 3 assessed pages — no JSON-LD for AI answer engines to cite. Investigated: docs 50%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. Investigated: wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [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

- [fail] Runnable collection with test scripts — No public Postman workspace found for the org, so there's no runnable collection an agent can execute against. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Your API discovery and agent-readability foundations are strong — agents can find and parse your documentation without friction. However, two areas are holding back partner adoption: onboarding is entirely self-service-free (no signup path, no quickstart, no code samples), meaning partners cannot get hands-on without direct intervention, and your APIs lack the runnable, executable context that both human developers and AI coding agents need to integrate correctly and confidently. Prioritize closing the onboarding gap and providing executable examples first, then shore up the security and agent-instruction signals to meet partner and enterprise compliance expectations.