# TomTom — API Agent Score

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

TomTom scored 68/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 72/100 (B)
- Developer Experience: 58/100 (D)
- Agent Discovery: 58/100 (D)
- Agent Understanding: 78/100 (B)
- Agent Usability: 72/100 (B)

## Check Results

### API Design

- [warn] Schema coverage & depth — 37/42 (88%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 90%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%.
- [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] Changelog published — Newest official SDK activity 20 day(s) ago. Investigated: sdk 100%.
- [warn] Description completeness — 42/50 operations carry a description. Investigated: sdk 84%.
- [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

- [warn] Registry & SDK presence — 3/4 registry-metadata components present; missing: repository link. Investigated: sdk 92%, docs 0%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Crawlable / AEO — Sitemap present (340 entries) but carries no lastmod values. 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) — Single base error "SDKError" with 2 subclasses. Investigated: sdk 100%.
- [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] 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 0 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%.
- [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

TomTom's API program shows strength in core schema design and general API readability, but has meaningful gaps in two areas that directly affect partner activation speed and AI-agent compatibility. The most urgent priorities are: (1) making the API surface discoverable and actionable for AI agents — currently missing machine-readable discovery artifacts and agent instruction files — and (2) ensuring partners can self-serve from first discovery through to a validated, running integration without a sales conversation. Closing these gaps will reduce partner onboarding friction, expand reach to AI-native developers and agent frameworks, and protect TomTom's position as a preferred mapping and location API for the next wave of agentic applications.