Can an AI agent browse IKEA's catalog?

Short answer: not at IKEA directly — the only sanctioned route runs through the aggregators IKEA names. The verified door-state for this exact task, the legal alternatives, and the demand registry are on this page.

The IKEA Outpost · Task · Menu / browse · Door-state verified November 1, 2026

The answer.

IKEA · Menu / browse · Agent Readiness Census, November 1, 2026.

IntentStateThe open routeSourceVerified
Menu / browse AGGREGATOR ONLY Google Shopping Source — www.ikea.com 2026-11-01

No official public product/developer API located after checking developer-portal angle and agent-native surfaces (llms.txt/api-catalog 404 on ikea.com). Third-party checks corroborate no generally available official product API. Catalog reachable via Google Shopping aggregator.

Door-state version census-2026-11-01. The same document is served as JSON by the API: api.agentoutposts.com/outposts/ikea — and published in full on the IKEA Outpost page.

What an agent can do instead.

Legal alternatives for this task, from the Options Registry.

AlternativeDoorThe routeVerified
Amazon PARTNER-GATED Amazon Creators API (Amazon Associates) 2026-11-01
Best Buy OPEN API Best Buy Products / Categories API (developer.bestbuy.com) 2026-11-01
Lowe's PARTNER-GATED Lowe's Developer Hub - Product Catalog (partner subscription) 2026-11-01
eBay PARTNER-GATED eBay Buy APIs - Browse API 2026-11-01

Alternatives are computed exactly as the API computes them: same category as IKEA (Retail & e-commerce), census door open or partner-gated, IKEA itself excluded. No paid placement — the order is the census order.

Register intent.

If you came to browse IKEA's catalog and the door was closed, say so here — and take the receipt with you.

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

POST to the intent endpoint with "intent": "menu_browse" and, if you like, a detail describing the task. You receive: a receipt (a ticket id confirming the registration), your queue position for that intent at IKEA, the current door-state document, and the alternatives above. 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.

On MCP, the same registration is the register_intent tool on POST https://api.agentoutposts.com/mcp (arguments: brand = "ikea", intent = "menu_browse"); poll_notify polls your token, and get_outpost_door_state returns the door-state document above.

Demand at this wall.

The count, as of November 1, 2026 — a snapshot, dated on purpose.

Registered intents at IKEA, as of November 1, 2026: 0. The registry is open and counting; no agent has registered at this Outpost yet. For this page's task (menu / browse): 0.

These are dated snapshot figures, published as of the date above. Live totals travel with the API: every intent receipt and every notify poll carries the brand's current demand snapshot.

How the count is made: callers are identified by a one-way SHA-256 hash — no raw IP addresses are stored — and registrations are capped at 100 per caller per day and 5,000 per day service-wide, behind an edge rate cap. Treat any count here as a demand signal, not proof of unique agents. Across the whole registry today, the ledger's only entry is Agent Outposts' own labeled internal test; no organic agent demand has been recorded yet.

The other tasks at IKEA.

Five tasks, five door-states — this page is one of them.

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