# Mozilla — API Agent Score

> Score: 51/100 (Grade: D) | Domain: mozilla.org | Rubric: 1.0.0 | Checked: July 24, 2026

Mozilla scored 51/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 43/100 (F)
- Developer Experience: 61/100 (C)
- Agent Discovery: 70/100 (B)
- Agent Understanding: 57/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Security & governance hygiene — security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Example coverage — No detectable code samples across 10 sampled docs pages. Investigated: docs 0%, 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://www.firefox.com/en-US/; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [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 10 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Discovered SDKs in 3 distinct languages. Investigated: sdk 100%, cli 100%, docs 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.mozilla.org/en-US/llms.txt, https://developer.mozilla.org/llms.txt, https://developer.mozilla.org/docs/llms.txt). Investigated: docs 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 79%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 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] 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

Mozilla's API program shows strength in agent discoverability basics, but two areas need urgent attention before partners and their AI agents can reliably build against your APIs: the contract itself (missing schemas, examples, and runnable collections) and the agent-facing context layer (no llms.txt, no AGENTS.md, no structured docs metadata). Until these gaps are closed, partners face guesswork at every step — from evaluating the API surface to writing their first integration — and AI coding agents will hallucinate shapes rather than build with confidence. Prioritize making the contract machine-readable and complete, then layer in discoverable, agent-ready context so partners can self-serve from day one.