# Ford — API Agent Score

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

Ford scored 57/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 52/100 (D)
- Developer Experience: 86/100 (A)
- Agent Discovery: 83/100 (A)
- Agent Understanding: 40/100 (F)
- Agent Usability: 53/100 (D)

## Check Results

### API Design

- [warn] Schema coverage & depth — 24/58 (41%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 48%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%.
- [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 — Signup page at https://www.ford.com/signup/; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [warn] Description completeness — 35/76 operations lack a description. Investigated: sdk 54%.
- [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.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms-full.txt reachable at https://ford.com/llms-full.txt. Investigated: docs 100%, sdk 0%.
- [warn] Registry & SDK presence — No MCP server, tool manifest, or list-tools capability is discoverable (server entrypoint: absent, tool manifest: unknown, list-tools: unknown). Investigated: sdk 50%, docs 0%, cli 0%.
- [pass] Crawlable / AEO — Sitemap with 100% lastmod coverage; newest entry < 90 days old. Investigated: wellknown 100%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 0%.
- [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] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [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

Ford's API program shows real strength in discovery and documentation quality, giving partners a solid front door. However, two areas are holding back partner and agent integration outcomes: agents cannot reliably parse or recover from errors (no machine-readable error bodies, no agent instructions file), and partners cannot confidently run real workflows (no idempotency guidance, no runnable collection with test scripts). Fixing error semantics and agent context first will unblock AI-assisted integrations immediately; adding runnable, tested collections will compress the time partners need to reach production-ready workflows.