# 169 254 169 254 — API Agent Score

> Score: 62/100 (Grade: C) | Domain: 169-254-169-254.nip.io. | Rubric: 1.0.0 | Checked: November 10, 2026

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

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

## Summary

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

## Category Scores

- API Design: 100/100 (A+)
- Developer Experience: 40/100 (F)
- Agent Discovery: 41/100 (F)
- Agent Understanding: 61/100 (C)
- Agent Usability: 85/100 (A)

## Check Results

### API Design

- [pass] Schema coverage & depth — .d.ts present on disk but not declared in package.json. Investigated: sdk 100%.
- [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

- [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] 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

- [warn] Registry & SDK presence — No official SDKs were found on npm, PyPI, or GitHub, so agents must call the API by hand. Investigated: sdk 17%, 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

- [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] Operation purpose clarity — 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 program's strongest area is agent usability — partners and their agents can safely integrate once they find you. However, the two most critical gaps are discoverability and crawlability: AI agents and search engines currently have no structured way to find, fetch, or index your documentation, meaning partners must rely on a sales conversation rather than self-serve discovery. Prioritize publishing machine-readable discovery artifacts and a sitemap immediately, then ensure your APIs are listed in the registries and toolchains where partners and agents already look.