Head to head · Placing and tracking orders · October 2026 research run

Walmart Agent Gateway vs Zinc

Zinc scores 69.9 (B) on agent readiness against Walmart Agent Gateway's 8.6 (F), and leads in every scored category. Both do placing and tracking orders.

Best shopping and order APIs for AI agents buying for a person · All 50 shopping comparisons

Which one, for what

Walmart Agent Gateway F

Best for Agents buying from Walmart and Sam's Club for a person, once the beta opens to them, with per-agent limits when Agent Profiles ship.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No public MCP endpoint, tool list, developer documentation or price was found

Zinc B

Best for Agents that need to buy physical goods from US retailers for a person, with machine payment and no account.

Ahead on

  • Reliability, 55 against 5
  • Schema & documentation, 92 against 0
  • Agent ergonomics, 86 against 0
  • Security & auth, 57 against 7
  • Payments & pricing, 98 against 15
  • Maintenance & community, 83 against 0
  • Transparency & trust, 60 against 51

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

By default orders run on retailer accounts Zinc runs, and its docs index lists a guide to Amazon's anti-bot pages and one on proxies "for account protection"

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Zinc +92

Walmart Agent Gateway 0

Every line needs a published contract or documentation, and none exists that we could read. No endpoint, tool list, JSON Schema or OpenAPI file (0 of 25). No llms.txt or Markdown docs for the gateway; the beta page at www.walmart.com/agents answered with a bot check on 25 October and the host is now paused (0 of 10). No tool descriptions (0 of 20), typed inputs (0 of 15), examples or error responses (0 of 15), versions or changelog (0 of 15). The post describes the product's purpose, which is not a tool description. Total 0.

Zinc 92

A public OpenAPI 3.1 file at api.zinc.com/openapi.json, version 2026-10-30, with 45 paths and 53 operations, 49 of them described (25). llms.txt, llms-full.txt, section indexes and Accept: text/markdown on every page (10). Pages say when to use each route, such as checking a retailer before ordering and using the offers endpoint rather than product details for a price (17 of 20). Typed request bodies with required fields, prices in integer cents and enumerated payment methods (14 of 15). Examples on every page and a long table of error codes with recovery steps, but the metered data endpoints return a different 402 shape and the MCP connector's tool schemas weren't read (11 of 15). Dated API versions (CalVer, 30 versions listed back to 24 November 2025) and a weekly changelog (15). 25 + 10 + 17 + 14 + 11 + 15 = 92.

Agent ergonomics Zinc +86

Walmart Agent Gateway 0

Every line needs a tool list or documentation. With no published tools, context cost, pagination and output controls, errors, retries and annotations, and defaults or SDKs have nothing to score (0 on each line), the reading Claude Duet got on 24 October for an interface outside agents can't reach. Total 0.

Zinc 86

Search returns up to 20 results, best first, and data and order calls are separate routes, so responses stay small. No field selection found (20 of 25). List and export endpoints take filters, and orders can be listed, exported and followed by webhook (18 of 20). Errors carry a stable code, a message and details, including details.fund_with on insufficient_funds and RFC 8628 hints in the device flow (20). Idempotency keys on orders, agent orders and top-ups, a 409 that names the existing order, and an MCP spending tool that needs a confirmation token only a person's click produces. MCP annotations weren't read (18 of 20). Few required fields, and an official npm SDK (zinc, CalVer from the live spec). No second official SDK was confirmed (10 of 15). 20 + 18 + 20 + 18 + 10 = 86.

Payments & pricing Zinc +83

Walmart Agent Gateway 15

Read with the hosted rule, per the 25 October check, not re-read on 11 November. No x402, MPP or L402, and no endpoint to carry one (0 of 40). No charge to developers is named; the post says agents see Walmart.com prices with fees shown before purchase. Nothing says the gateway is free either, the Zillow in Claude reading (10 of 20). Access is a beta by request whose terms weren't read, so no free tier without a card can be shown (0 of 20). A company or developer has to request beta access and a customer has to sign in to Walmart, and Section 16.L says an Agent that hasn't met Walmart's registration and technical requirements may not use the Walmart Sites, so no autonomous onboarding (0 of 20). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Zinc 98

x402 (v2, USDC on Base and Solana) and MPP (Tempo, and Link with a Shared Payment Token) on POST /agent/orders and the /agent/* data endpoints. Returns, cases, managed accounts and webhooks need an API key (8 of 10). $1 per successful order plus the item, $0.25 for tracking links and emails, $0.10 per item over 10, and $0.01 per data call, published without login (30). A sandbox needs no account or card, and a device-approved live key comes with a $5 starter credit (30). An agent can pay per order with no account, or mint a sandbox key with one unauthenticated call (30). 8 + 30 + 30 + 30 = 98.

Maintenance & community Zinc +83

Walmart Agent Gateway 0

Read as a closed service. No release, version, published API change or release note for the gateway was found. The announcement of 21 October 2026 is a launch post that promises later access, not an API change, and the line would score once the gateway or Agent Profiles ship (0 of 30). No dated entries in the last 90 days (0 of 20). No changelog, developer forum or support channel for the gateway was found, and the beta page was unread (0 of 15). No Walmart-owned MCP registry entry or SDK was found; the 25 October registry search used the registry's JSON API, which this run doesn't use, so no registry page was read (0 of 15). No package, repository or CI (0 of 10). Total 0.

Zinc 83

The changelog's latest entry is dated 13 November 2026, and the npm SDK's latest version is 2026.10.30 (30). Weekly dated changelog entries, 13 since 20 August 2026 (20). A public weekly changelog and a support address (support@zinc.com) that the contact page says gets a person. GitHub issue response wasn't checked (10 of 25). The MCP connector is in the official MCP registry as com.zinc.www/mcp, published 28 October 2026 under Zinc's domain namespace, and the npm SDK is current (15). The npm SDK is generated from the live spec and published with provenance attestations (8 of 10). 30 + 20 + 10 + 15 + 8 = 83.

Reliability Zinc +50

Walmart Agent Gateway 5

www.walmart.com's Terms of Use (last updated 21 September 2026, re-read on 11 November) bar any robot or Agent not authorised under Section 16.L or Walmart's Agentic Access Terms from gathering Materials or interacting with the Walmart Sites, and corporate.walmart.com's terms bar spiders, robots and intelligent agents, so both hosts are paused and only the walmart.com terms page was requested. Read with the hosted lines on Walmart's announcement of 21 October 2026, per the 25 October check, not re-read on 11 November. No status page for the gateway was found (0 of 20). With no page there is no readable incident history (5 of 30). No rate limits published; Section 16.L says Agents must comply with applicable rate limits but gives no numbers (0 of 15). No 429, retry or idempotency guidance (0 of 15). No SLA (0 of 10). Walmart says it is building the gateway and starting with a beta for companies and developers, so not generally available (0 of 10). Total 5.

Zinc 55

Zinc's own status page (www.zinc.com/status) shows five components (Ordering, Tracking, Product Data, API, Dashboard) with 90-day uptime bars (20). On 18 November 2026 it showed 99.1 per cent uptime for Ordering and 99.57 per cent for the API over 90 days, both recovered from a degradation that day. The page has no incident write-ups, and 99.1 per cent over 90 days is about 19 hours, so at least one major interruption is implied (10 of 30). No numeric request rate limits found, apart from 5 sandbox key mints per IP address a day (5 of 15). 429 carries rate_limit_exceeded with guidance to back off and retry, responses carry RateLimit and RateLimit-Policy headers (changelog, August 2026), and orders and top-ups take idempotency keys (15). No SLA found (0). Orders are generally available. Cross-retailer search and the Zinc 2.0 announcement carry a beta label (5 of 10). 20 + 10 + 5 + 15 + 0 + 5 = 55.

Security & auth Zinc +50

Walmart Agent Gateway 7

Graded on the interface an outside agent can call, the reading Claude Duet got. With no published endpoint or credential model, the credential, least-privilege, injection and audit lines score nothing (0 of 30, 0 of 20, 0 of 15, 0 of 15). Section 16.L of the walmart.com Terms of Use says an Agent may reach a customer's account only through authentication methods Walmart makes available or approves, and that revoking an Agent in account settings invalidates its tokens; no such method for the gateway is published, so this is in forReviewers, not scored. The security programme line doesn't need an interface. Per the 25 October check, not re-read on 11 November (host paused), www.walmart.com/.well-known/security.txt points to a responsible disclosure policy with safe harbour, discretionary rewards and a HackerOne-hosted submission form, with no Expires field. No acknowledgement time was recorded and discretionary rewards aren't a bounty, so the line reads as a disclosure route with no stated time (7 of 20, as on the walmart-affiliate-api listing). 0 + 0 + 0 + 0 + 7 = 7.

Zinc 57

Bearer API keys, zn_test_ for sandbox and zn_live_ for live, and each agent can get its own live key by device-code approval. No scopes or rotation steps were found (18 of 30). Sandbox keys can't spend, every order carries a max_price cap, a person approves a live key in the browser, and the MCP connector's place-order needs a confirmation token withheld from the model (17 of 20). The MCP docs explain that the token is there so a prompt injection in a page can't become a purchase. Product data from retailers is untrusted text (12 of 15). Order timelines, a usage endpoint, CSV export and the dashboard show every order (10 of 15). No security.txt (404), disclosure policy, bug bounty, SOC 2 or ISO 27001 found (0). 18 + 17 + 12 + 10 + 0 = 57.

Score by category

CategoryWeightWalmart Agent GatewayZincEdge
Reliability16%555Zinc +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%092Zinc +92
Agent ergonomics13%086Zinc +86
Security & auth14%757Zinc +50
Payments & pricing10%1598Zinc +83
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%083Zinc +83
Transparency & trust7%5160Zinc +9
Negative events≤1500
TotalF 8.6/100B 69.9/100

Facts side by side

FactWalmart Agent GatewayZinc
KindMCP serverHTTP API
VendorWalmartZinc
Hosted endpointno (local only)https://mcp.zinc.com/mcp
TransportsStreamable HTTP
AuthOAuth or keyOAuth or key
PricingFreePay per use
Price for placing and tracking ordersfree$0.10 per transaction
x402noon some endpoints
LicenceProprietary hosted service. Walmart's terms for AI agents are summarised in its announcement of 21 October 2026, and the walmart.com Terms of Use (21 September 2026) carry an Authorized Agents section that refers to separate Agentic Access Terms, which no page we read linksProprietary service, agent skills MIT
Tools exposednone8
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.zinc.www/mcp
Last releasenone2026-11-13
Terms last updated2026-09-092026-10-12
Privacy policy last updated2026-08-202026-10-06
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes

How the scores have moved

Verdicts

Walmart Agent Gateway

Walmart has published rules for agents shopping its sites, including customer approval of purchases by default, no access to payment cards, revocable agent access and blocking of agents that break them. The gateway is a beta by request for companies and developers, with no public endpoint, documentation, tool list or price. Agent Profiles weren't seen live.

Zinc

An agent can mint a sandbox key with no signup and pay for real orders by x402, MPP or Link with no account, at $1 an order plus the item, with idempotency keys and a public OpenAPI file. Orders run on Zinc's own retailer accounts by default, and no security programme or numeric rate limits were found.

Before you call either

Walmart Agent Gateway

  1. Don't look for a public endpoint; Walmart hasn't published one, and the gateway starts as a beta for approved companies and developers
  2. Identify yourself as an agent and keep to Walmart's rate limits; Section 16.L of the walmart.com terms requires both
  3. Ask your human for approval before any Walmart purchase; Walmart's terms require it by default and block agents that act beyond the shopper's intent
  4. Don't request or store the customer's card details; Walmart's terms bar agents from payment-card data and payment-method changes
  5. Don't assume ChatGPT, Gemini or Muse connect through the gateway; Walmart's own post doesn't say so

Zinc

  1. Call GET /retailers/check with the product URL and country before ordering, since unsupported retailers and countries fail predictably
  2. Set max_price and an idempotency_key on every order. If a retry returns 409, read the existing order id from error.details.order_id
  3. If your HTTP client merges WWW-Authenticate headers, add ?method=x402, ?method=tempo or ?method=stripe to get one payment challenge
  4. Store the X-Api-Key returned with a paid agent order. It is the only way to follow that order without paying again
  5. Persist a sandbox key across runs. It expires after 7 days without use, and minting is limited to 5 a day per IP address

Questions

Which is better for AI agents, Walmart Agent Gateway or Zinc?

Zinc scores 69.9 (B) on agent readiness against Walmart Agent Gateway's 8.6 (F), and leads in every scored category.

Which is cheaper for placing and tracking orders, Walmart Agent Gateway or Zinc?

Walmart Agent Gateway, at free against $0.10 per transaction for Zinc. These are the vendors' published prices for the job.

Do Walmart Agent Gateway and Zinc need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Walmart Agent Gateway and Zinc without installing anything?

No hosted endpoint is listed for Walmart Agent Gateway. Zinc has a hosted endpoint at https://mcp.zinc.com/mcp.

Other comparisons with Walmart Agent Gateway or Zinc

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.