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

CartAI vs Walmart Agent Gateway

CartAI scores 34.9 (F) on agent readiness against Walmart Agent Gateway's 8.6 (F), and leads in 6 of 7 scored categories. Walmart Agent Gateway leads on transparency & trust. Both do placing and tracking orders.

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

Which one, for what

CartAI F

Best for Platforms that show products (rewards apps, publishers, vertical AI apps) and want to complete purchases on US merchants' own sites without merchant integrations.

Ahead on

  • Reliability, 18 against 5
  • Schema & documentation, 59 against 0
  • Agent ergonomics, 49 against 0
  • Security & auth, 43 against 7
  • Payments & pricing, 30 against 15
  • Maintenance & community, 18 against 0

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

No public prices. Production fees are basis points on order value, shown only in the dashboard

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.

Ahead on

  • Transparency & trust, 51 against 45

Also in its favour

  • No incidents deducted, where CartAI loses 3 points for them

Watch for

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

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 CartAI +59

CartAI 59

A public OpenAPI 3.0 file at docs.cartai.ai/openapi/latest.yml with 13 operations. It declares no security scheme, and the key header is spelt X-Api-Key on some paths and x-api-key on others, which CartAI's own auth.md points out (20 of 25). llms.txt on both hosts and a Markdown twin of every docs page (10). Reference pages say when to use each call, such as a table of when to use webhooks or polling for a task, and the MCP tool descriptions say which call comes next (14 of 20). Required fields and patterns for phone and postal code, but only two enums in the spec, shippingMethod.strategy is a free string, and payment.data is typed as a string in one table while the examples send an object (7 of 15). Request and response examples on each page and a 401 body, but most operations document only 400, and a link to the task lifecycle section points to an anchor that is missing (8 of 15). No changelog and no API versioning beyond 1.0.0 in the spec (0). 20 + 10 + 14 + 7 + 8 + 0 = 59.

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.

Agent ergonomics CartAI +49

CartAI 49

The MCP server has 8 tools with compact descriptions, but each result appends the full JSON response, and the REST API has no field selection (22 of 25). Product search takes a query and an optional merchant to prioritise, with no limit, page or filter parameters found (6 of 20). A documented 401 body with an error code and message, 400 on every operation, and 403, 404 and 409 on interactive inputs. Error bodies for failed checkouts are not described beyond the FAILED status (10 of 20). No idempotency key on writes, and the docs say a resubmit creates a duplicate. A confirmation step (verifyBeforePlacement, PENDING_CONFIRMATION) and a cancel call exist, and the MCP tools carry no readOnlyHint or destructiveHint (6 of 20). A checkout needs a full customer object with contact, two addresses, shipping strategy and payment. No official SDK, and the MCP server runs from a clone, in Node.js only (5 of 15). 22 + 6 + 10 + 6 + 5 = 49.

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.

Security & auth CartAI +36

CartAI 43

One API key per request in a header, revocable and regenerated in the portal, with no scopes or rotation guidance found (20 of 30). No read-only key. A checkout can wait for the customer's confirmation, and production payments run through hosted Visa Intelligent Commerce or Mastercard Agent Pay sessions the customer authorises. The MCP server places orders with no confirmation of its own (10 of 20). Product search and details return merchant page content with no prompt-injection guidance, and the create_payment_session tool description tells the model to present the payment link "without asking the user first" (3 of 15). Each task has a status history with timestamps and credits, a live preview URL and webhooks for every status (10 of 15). No security.txt (404), disclosure policy, bug bounty or certification found. The known limitations page says test-mode card data is not tokenised and could appear in logs (0 of 20). 20 + 10 + 3 + 10 + 0 = 43.

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.

Maintenance & community CartAI +18

CartAI 18

Closed service with no changelog. The newest dated release found is the MCP server's last commit on 20 July 2026, 123 days ago (10 of 30). Docs pages show updatedAt dates from 17 to 20 November 2026, but no dated change list, so no releases can be counted in the last 90 days (0 of 20). No public changelog. Support is through a contact page, info@cartai.ai and a portal request for more credits that the docs say is reviewed within one business day. Neither was tested (5 of 25). Not in the official MCP registry, not on npm, and no official SDKs (0 of 15). The MCP server pins @modelcontextprotocol/sdk ^1.0.0 and zod ^3.22.0 with a lockfile and no CI (3 of 10). The earliest first-hand date of a running API is a webhook example of 6 December 2025, and the MCP repository dates from 25 May 2026. 10 + 0 + 5 + 0 + 3 = 18.

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.

Payments & pricing CartAI +15

CartAI 30

No x402, MPP or L402. The card sessions pay merchants for customers' orders, not CartAI (0 of 10). No price list without a login. The terms say production fees are basis points on order value and other usage metrics, shown in the dashboard or agreed separately, and credits have no published price (0 of 30). Every new account gets 5 free credits, about 500 Catalog API calls or at least 10 test checkouts, and the signup asks for name, email and password with no card (30). A person signs up in a browser to get a key, and production needs a Go Live review (0). 0 + 0 + 30 + 0 = 30.

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.

Reliability CartAI +13

CartAI 18

Graded on the hosted REST API at api.cartai.ai. No status page was linked from any page read (0), so there is no incident history to read (5). No numeric rate limits found. The task reference only says polling every second "may trigger rate limits" (0). No 429 or backoff guidance and no idempotency key. The docs give a 5 to 10 second polling interval and warn that a resubmitted checkout creates a duplicate order (3 of 15). The terms put SLA commitments in separate enterprise agreements, with none published (0). The Checkout and Catalog APIs carry no beta label, though production use needs a Go Live review and the Hosted Cart is not generally available (10). 0 + 5 + 0 + 3 + 0 + 10 = 18.

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.

Score by category

CategoryWeightCartAIWalmart Agent GatewayEdge
Reliability16%185CartAI +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%590CartAI +59
Agent ergonomics13%490CartAI +49
Security & auth14%437CartAI +36
Payments & pricing10%3015CartAI +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%180CartAI +18
Transparency & trust7%4551Walmart Agent Gateway +6
Negative events≤15-30
TotalF 34.9/100F 8.6/100

Facts side by side

FactCartAIWalmart Agent Gateway
KindHTTP APIMCP server
VendorCartAIWalmart
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthAPI keyOAuth or key
PricingFreemiumFree
x402nono
LicencenoneProprietary 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 links
Tools exposed8none
Read-only variant documentednono
llms.txtyesno
Last release2026-07-20none
Terms last updated2026-05-132026-09-09
Privacy policy last updated2026-05-132026-08-20
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes

How the scores have moved

Verdicts

CartAI

CartAI lets a platform buy from US merchants' own sites through one asynchronous API, with a public OpenAPI file, Markdown docs, webhooks and an optional customer confirmation step. There is no public price list, status page, rate limit or idempotency key, and the home page's retry-safe and Hosted Cart claims go further than the docs.

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.

Before you call either

CartAI

  1. Never resend POST /checkout after a 201 or a timeout. Look up the task with GET /checkout/{taskId} first, because a resubmit creates a duplicate order
  2. Use only the test card 4242 4242 4242 4242 until the account is in production mode, since test mode does not tokenise card data
  3. Set verifyBeforePlacement and show derivedDetails.pricing to the customer at PENDING_CONFIRMATION before the order is placed
  4. Poll a task no more than once every 5 to 10 seconds when webhooks are unavailable
  5. Give selectedVariant labels as the merchant's page shows them, and use US merchants, addresses and phone numbers only

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

Questions

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

CartAI scores 34.9 (F) on agent readiness against Walmart Agent Gateway's 8.6 (F), and leads in 6 of 7 scored categories. Walmart Agent Gateway leads on transparency & trust.

Do CartAI and Walmart Agent Gateway need an API key?

CartAI needs an API key. Walmart Agent Gateway takes an API key or an OAuth sign-in.

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

CartAI runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Walmart Agent Gateway.

Other comparisons with CartAI or Walmart Agent Gateway

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.