# Yahoo — API Agent Score

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

Yahoo scored 65/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 93/100 (A+)
- Developer Experience: 46/100 (F)
- Agent Discovery: 90/100 (A+)
- Agent Understanding: 64/100 (C)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [warn] Schema coverage & depth — 1 of 4 public signatures use loose types (anyTypeRatio=0.250). Investigated: sdk 83%.
- [pass] Security & governance hygiene — security.txt valid at https://yahoo.com/.well-known/security.txt (Contact + unexpired Expires). Investigated: wellknown 100%.
- [pass] Example coverage — Code samples present on 2/20 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%, sdk 100%.
- [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] Code samples in docs — Code samples present on 2/20 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 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%.
- [fail] Description completeness — 3/3 operations lack a description. Investigated: sdk 0%.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Discovered SDKs in 5 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 83%, sdk 0%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [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 1 assessed pages (1 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

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [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

Yahoo's API program has a strong foundation in discovery and design — partners and agents can find and parse your APIs reliably. However, two areas are holding back partner adoption at scale: Developer Experience (no self-service portal, no quickstart, and thin endpoint descriptions mean partners can't get to a first successful call without hand-holding) and Agent Usability (no runnable collection with test scripts and no idempotency documentation mean neither human developers nor AI agents can safely build and verify real workflows). Prioritize standing up a self-service documentation and onboarding surface first, then close the gaps in executable, trustworthy runtime context.