# 127 0 0 1 — API Agent Score

> Score: 78/100 (Grade: B) | Domain: 127-0-0-1.local.gd | Rubric: 1.0.0 | Checked: November 10, 2026

127 0 0 1 scored 78/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 97/100 (A+)
- Developer Experience: 80/100 (A)
- Agent Discovery: 47/100 (F)
- Agent Understanding: 88/100 (A)
- Agent Usability: 85/100 (A)

## Check Results

### API Design

- [warn] Schema coverage & depth — 7 of 103 public signatures use loose types (anyTypeRatio=0.068). Investigated: sdk 93%.
- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%.
- [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

- [warn] Description completeness — 13/56 operations lack a description. Investigated: sdk 77%.
- [skip] Self-service developer portal — No surface produced evidence for this capability in this run.
- [skip] Quickstart present — No surface produced evidence for this capability in this run.
- [skip] Code samples in docs — 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

- [warn] Registry & SDK presence — No official SDKs were found on npm, PyPI, or GitHub, so agents must call the API by hand. Investigated: sdk 58%, docs 0%, cli 0%.
- [fail] llms.txt present, valid & comprehensive — No llms-full.txt was found at any candidate origin, so agents can't grab your full docs in one fetch. Investigated: docs 0%, sdk 0%.
- [fail] Crawlable / AEO — No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Operation purpose clarity — Surface uses a single dominant casing convention (camelCase). Investigated: sdk 100%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — 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] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.
- [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.

## Executive Summary

Your API design, developer experience, and agent usability are all in strong shape — partners who find your API can build against it confidently. The critical gap is discoverability: AI agents and search engines have no structured entry point to your documentation, meaning partners who don't already know you exist will never find you, and AI-powered tools cannot index or act on your APIs without manual intervention. Closing the documentation discovery and crawlability gaps should be the immediate priority, as everything else depends on partners and agents being able to find the front door first.