# Exact — API Agent Score

> Score: 58/100 (Grade: D) | Domain: exactonline.nl | Rubric: 1.0.0 | Checked: August 4, 2026

Exact scored 58/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 51/100 (D)
- Developer Experience: 54/100 (D)
- Agent Discovery: 68/100 (C)
- Agent Understanding: 77/100 (B)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [warn] Schema coverage & depth — 0/58 (0%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 25%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [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

- [pass] Self-service developer portal — Self-service signup at https://start.exactonline.nl/; no free tier or sandbox language detected. Investigated: docs 100%.
- [warn] Description completeness — 86/112 operations lack a description. Investigated: sdk 23%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 17 sampled docs pages. Investigated: docs 0%.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/start_exactonline_nl, 2135 snippets). Investigated: docs 100%, sdk 25%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — Sitemap lastmod coverage 43% or newest entry older than 90 days. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://www.exact.com/developers/llms.txt, https://www.exact.com/llms.txt, https://www.exact.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "ExactOnlineError" with 8 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 79%.
- [warn] Docs structured data — JSON-LD on 7/17 assessed pages, but coverage is sparse or dateModified is missing. Investigated: docs 50%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [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

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: 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

Exactonline's API program shows relative strength in agent understanding and doc parseability, but faces critical gaps in two areas that will directly limit partner adoption: agents and partners cannot discover or reliably consume the APIs without manual intervention, and operational reliability signals — idempotency documentation and runnable collections — are absent, meaning both human developers and AI agents are forced to guess at integration correctness. The highest-priority work is making the API program self-serve and machine-readable end-to-end, followed by hardening the onboarding experience so partners reach a first successful call in minutes, not weeks.