# APILayer — API Agent Score

> Score: 65/100 (Grade: C) | Domain: apilayer.com | Rubric: 1.0.0 | Checked: July 24, 2026

APILayer scored 65/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 89/100 (A)
- Developer Experience: 54/100 (D)
- Agent Discovery: 60/100 (C)
- Agent Understanding: 74/100 (B)
- Agent Usability: 51/100 (D)

## Check Results

### API Design

- [warn] Auth declared & discoverable — securitySchemes declared but never applied. Investigated: spec 89%, docs 89%.
- [warn] Schema coverage & depth — Only 65% of operations have documented schemas. Investigated: spec 83%, sdk 56%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" 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 0%.
- [pass] Example coverage — 100% example coverage across params + responses. Investigated: spec 100%, sdk 50%.

### Developer Experience

- [pass] Description completeness — 42% description completeness. Investigated: spec 100%, sdk 20%.
- [warn] Changelog published — Human-readable changelog referenced: https://docs.apilayer.com/changelog/docs/aviationstack. Investigated: spec 50%, docs 50%.
- [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%.
- [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.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/apilayer_fixer, 59 snippets). Investigated: docs 100%, sdk 50%, cli 0%.
- [warn] Crawlable / AEO — Sitemap lastmod coverage 59% or newest entry older than 90 days. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 0%, sdk 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: docs 100%, spec 50%.
- [warn] Operation purpose clarity — 27% of operations are agent-inferable. Investigated: spec 61%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [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] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [warn] Pagination documented & consistent — 1 list endpoint(s) exist but no pagination params found. Investigated: spec 20%, docs 20%.
- [warn] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 17%, docs 17%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.

## Executive Summary

Apilayer's API design is solid, giving partners a reliable contract to build against — but two areas are holding back partner adoption: developer experience and agent readiness. There is no self-service portal where partners can onboard themselves, and the program lacks the machine-readable discovery signals (llms.txt, AGENTS.md) that AI agents need to find and act on your APIs without human intervention. Prioritizing a branded, self-serve documentation portal and adding the missing agent-readiness artifacts will unlock both partner self-service and the growing wave of AI-agent-driven integrations.