# Target — API Agent Score

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

Target scored 61/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 83/100 (A)
- Developer Experience: 55/100 (D)
- Agent Discovery: 67/100 (C)
- Agent Understanding: 78/100 (B)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — Medium parameter complexity (avg 3.8 params/op; nested/body schemas present). Investigated: spec 83%, sdk 0%.
- [warn] Machine-readable, versioned contract — info.version="1.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [fail] Example coverage — 0% example coverage. Investigated: spec 0%, docs 0%, sdk 0%.

### Developer Experience

- [pass] Description completeness — 100% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [pass] Changelog published — Newest official SDK activity 1 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Quickstart present — Quickstart page reachable (10 variants scanned starting at https://developer.target.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [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] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [warn] Registry & SDK presence — 3/4 registry-metadata components present; missing: keywords. Investigated: sdk 88%, docs 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.target.com/llms.txt, https://developer.target.com/docs/llms.txt). Investigated: docs 33%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 4 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 1 of 1 pages appear to be client-side rendered SPA shells (root 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%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [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] 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

Target's API program shows strong fundamentals in machine-readable contract quality, schema design, and documentation discoverability — a solid foundation for partner integrations. However, two areas are holding back partner activation: agents and developers cannot reliably build against the APIs because examples, runnable collections, and rate-limit signals are missing or incomplete, and the program lacks the self-service infrastructure (developer portal, code samples, agent instruction files) that lets partners go from discovery to working integration without friction. Closing these gaps should be the immediate priority to unlock self-serve partner onboarding and agent-assisted workflows at scale.