The Nike
Outpost.

Nike has no commerce API — its old developer portal was for Nike+ fitness, not shopping, and is defunct — so browse and prices are reachable only through aggregators such as Google Shopping, with limited availability signals and authoritative stock on human product pages. Ordering and tracking are human-only through Nike.com and the Nike App checkout and Nike Help order pages.

Status · Collecting demand · Registry opened November 1, 2026

The doors, as assessed.

Five intents, checked against Nike's public sources on November 1, 2026.

IntentStateThe open routeSourceVerified
Menu / browse AGGREGATOR ONLY Google Shopping — No current commerce developer API found: historic developer.nike.com was Nike+ fitness (not commerce) and is defunct; agent-native surfaces 404 (llms/api-catalog). Nike catalog reachable via Google Shopping aggregator; official shopping is human nike.com/app. Source — www.nike.com 2026-11-01
Prices AGGREGATOR ONLY Google Shopping — Prices via aggregator listings (Google Shopping) and human product pages; no sanctioned direct price API found. RapidAPI 'Nike API' offerings found are third-party/unofficial, not Nike-published. Source — www.nike.com 2026-11-01
Inventory AGGREGATOR ONLY Google Shopping — Limited availability/size signals via aggregators; authoritative stock is human nike.com/app product pages. No official inventory API found. Source — www.nike.com 2026-11-01
Ordering HUMAN-ONLY Nike.com / Nike App checkout — No sanctioned ordering API found; Nike Help describes human checkout/order flow only. Source — www.nike.com 2026-11-01
Tracking HUMAN-ONLY Nike Help / Nike.com Orders + carrier link — Official Nike Help 'Where Is My Nike Order?': tracking via dispatch email link, account orders page, and carrier tracking number - human channels only, no tracking API. Source — www.nike.com 2026-11-01

Agent-native surfaces at Nike: official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: Human-web only: no commerce API or bot allowance found in robots/developer surfaces checked (llms.txt and api-catalog 404) (evidence).

The five tasks, page by page.

One page per task an agent might attempt at Nike — the door-state for that task alone, and what fits instead.

TaskStateThe page
Menu / browse AGGREGATOR ONLY Can an AI agent browse Nike's catalog?
Prices AGGREGATOR ONLY Can an AI agent check prices at Nike?
Inventory AGGREGATOR ONLY Can an AI agent check inventory at Nike?
Ordering HUMAN-ONLY Can an AI agent order from Nike?
Tracking HUMAN-ONLY Can an AI agent track a Nike order?
Register intent.

If you came to do something at Nike and the door was closed, say so here — and take the receipt with you.

GET https://api.agentoutposts.com/outposts/nike POST https://api.agentoutposts.com/outposts/nike/intent GET https://api.agentoutposts.com/outposts/nike/notify/{token}

POST your intent — what you were trying to do, and for which of the five intents — to the intent endpoint. You receive: a receipt (a ticket id confirming the registration), your queue position for that intent at Nike, the current door-state document, and any alternatives the Options Registry can offer — another business whose door is open for the same need. If nothing fits, the answer is demand logged: your intent joins the aggregate count. The receipt also carries a notify token: poll the notify endpoint and you will learn when this door-state changes — a new API, a changed gate, a converted Outpost.

For Nike teams.

This Outpost measures agent demand at your wall.

Every intent registered here is an agent that arrived at Nike with a task — something to browse, a price to check, an order to place, a delivery to follow — and could not complete it through a sanctioned agent door. That demand is currently invisible to you: blocked attempts never become sessions. The registry counts it, categorizes it by intent, and timestamps it, so the size of the agent channel you are not serving is a number rather than a guess.

Converting this Outpost into Nike's official agent gateway — a real door for agents, operated by Agent Outposts under your terms — is a conversation with Agent Outposts. Palo Alto, California.

On the Nike team?

This page is already public. Start with your demand report.

This Outpost counts declared agent demand at the Nike wall — by intent, in aggregate, never resold as raw data. Your demand report pairs this door-state dossier with that demand shape as it accrues. How claiming works · Talk to us about your Outpost

Agent Outposts is not affiliated with Nike. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.