# AFAS — API Agent Score

> Score: 72/100 (Grade: B) | Domain: afas.nl | Rubric: 1.0.0 | Checked: August 4, 2026

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

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

## Summary

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

## Category Scores

- API Design: 83/100 (A)
- Developer Experience: 75/100 (B)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 79/100 (B)
- Agent Usability: 60/100 (C)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — info.version="8.8.11" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 88%, docs 75%.
- [warn] Schema coverage & depth — 11 of 48 public signatures use loose types (anyTypeRatio=0.229). Investigated: sdk 83%, spec 58%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [warn] Auth declared & discoverable — securitySchemes declared but never applied. Investigated: docs 50%, spec 25%, wellknown 0%.
- [pass] Example coverage — 49% example coverage. Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://klant.afas.nl/login?url=%2fkennisportaal; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Description completeness — 55% description completeness. Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Quickstart present — Quickstart page reachable (10 variants scanned starting at https://docs.afas.help/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/afas_help, 442 snippets). Investigated: docs 100%, sdk 67%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://docs.afas.help/llms.txt, https://docs.afas.help/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 7 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%, sdk 50%.
- [pass] Operation purpose clarity — 92% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 71%.
- [warn] Docs structured data — OpenGraph/meta tags only across 1 assessed pages — no JSON-LD for answer engines to cite. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 11% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 35 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 25%, docs 25%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Afas's API design and description quality are strong foundations for a partner program, but two areas are holding partners back: agents and coding tools lack the structured context they need to integrate without guesswork, and there is no runnable, test-backed artifact to accelerate or validate partner integrations. Prioritize publishing an agent instructions file and a runnable collection with idempotency documentation first — these unlock both human and AI-driven partner onboarding at scale.