# Onfleet — API Agent Score

> Score: 52/100 (Grade: D) | Domain: onfleet.com | Rubric: 1.0.0 | Checked: July 24, 2026

Onfleet scored 52/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 70/100 (B)
- Agent Discovery: 79/100 (B)
- Agent Understanding: 58/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [fail] Example coverage — No README found. Investigated: sdk 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://onfleet.com/signup; free tier / sandbox documented. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 10 day(s) ago. Investigated: sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [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.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/onfleet_reference, 771 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 86%.
- [warn] Docs reachable, not hard auth-gated — 50 JavaScript redirect(s) detected across 50 sampled pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 50 pages exceed 100K chars (max 317K). Investigated: docs 65%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: 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] 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

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [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.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Onfleet's API program shows real strengths in documentation discoverability and crawlability, but partners and their AI agents face serious friction in three areas that matter most: the API contract itself lacks the schema depth and examples agents need to build against reliably, there is no runnable collection or agent-readable instruction file to anchor integrations, and onboarding has no quickstart to get partners to a first successful call quickly. Fixing the contract quality and adding executable, agent-ready context should be the immediate priority — these gaps block both human partners and the AI agents they are increasingly using to build integrations.