# Tesla — API Agent Score

> Score: 48/100 (Grade: F) | Domain: tesla.com | Rubric: 1.0.0 | Checked: July 24, 2026

Tesla scored 48/100 (F), classified "not-ai-ready".

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

## Summary

- Overall: 48/100 (F)
- Classification: not-ai-ready

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 45/100 (F)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 61/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [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] Schema coverage & depth — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.
- [skip] Example coverage — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Changelog published — Newest official SDK activity 1 day(s) ago. Investigated: sdk 100%.
- [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%.
- [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 (elixir-tesla/tesla, 147 snippets). Investigated: docs 100%, sdk 100%, cli 50%, mcp 0%, wellknown 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 — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.tesla.com/docs/fleet-api/llms.txt, https://developer.tesla.com/llms.txt, https://developer.tesla.com/docs/llms.txt). Investigated: docs 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 1 pages appear to be client-side rendered SPA shells (___gatsby detected); agents using HTTP fetches will see no content. Investigated: docs 71%.
- [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 0 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

Tesla's API program shows strength in crawlability and doc parseability, but faces critical gaps in two areas that directly block partner activation: the absence of a self-service onboarding path and the lack of agent-ready discovery infrastructure. Without a public developer portal, quickstart, and runnable collections, partners cannot get hands-on independently — and AI agents building integrations have no reliable, machine-readable surface to work from. The immediate priority is establishing a self-service front door with executable examples, followed by layering in agent discovery signals so both human and AI consumers can find and act on your APIs without friction.