Head to head · Product search for shoppers · October 2026 research run

Best Buy Developer API vs CartAI

Best Buy Developer API scores 40.4 (E) on agent readiness against CartAI's 34.9 (F), and leads in 3 of 7 scored categories. CartAI leads on schema & documentation, security & auth, maintenance & community and transparency & trust. Both do product search for shoppers.

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

Which one, for what

Best Buy Developer API E

Best for Product, price and store-availability search for US electronics, for agents that compare and then hand the purchase to the person.

Ahead on

  • Reliability, 31 against 18
  • Agent ergonomics, 72 against 49
  • Payments & pricing, 45 against 30

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where CartAI loses 3 points for them

Watch for

Ordering, fulfilment, order lookup and cancellation are only in the Commerce API, which is invite-only with documentation shared after approval

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

  • Schema & documentation, 59 against 45
  • Security & auth, 43 against 32
  • Maintenance & community, 18 against 5
  • Transparency & trust, 45 against 40

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

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.

Agent ergonomics Best Buy Developer API +23

Best Buy Developer API 72

The show parameter returns only named fields, and pageSize sets the page up to 100 (22 of 25). Pagination by page or cursorMark, facets, sort and a filter syntax with operators (20 of 20). Errors carry an HTTP code and a message, but 403 covers both an invalid key and an exhausted limit (10 of 20). The public APIs only read, so retries are safe, and there are no idempotency keys because no public call writes (12 of 20). XML is the default format for three APIs, and the official JavaScript and PHP SDKs date from 2021 and 2017 (8 of 15). Total 72.

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.

Payments & pricing Best Buy Developer API +15

Best Buy Developer API 45

No x402, MPP or L402 (0 of 40). The public APIs have no stated price, and the limits are published, but no page says the API is free (10 of 20). A key needs only an email address and no card (20 of 20). A person signs up and activates the key from an email, and Commerce access needs an invitation (0 of 20). Total 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Schema & documentation CartAI +14

Best Buy Developer API 45

No OpenAPI or similar contract. A Postman collection is linked from the docs (8 of 25, the earlier partial held). No llms.txt or Markdown docs for agents were found (0 of 10). The reference explains each API's purpose and attributes, with little on when not to use them (12 of 20). Query terms go in the path in a custom syntax, and attributes are listed with types but no enums or constraints (8 of 15). Examples in curl and JavaScript throughout, and an error table for 400, 403, 404, 405, 500, 501 and 503 (12 of 15). URLs carry v1 and beta, but there is no public changelog and the documentation source was last changed on 26 April 2021, unchanged in a clone on 10 November 2026 (5 of 15, the earlier partial held). Total 45.

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.

Reliability Best Buy Developer API +13

Best Buy Developer API 31

No status page was found for the API or the developer site (0 of 20), and so no incident history (5 of 30). The terms publish 5 calls a second and 50,000 a day (15 of 15). Over-limit calls return 403, the same code as a bad key, with an email to the key holder and no Retry-After. The docs suggest the in operator to avoid per-second errors, which is the only guidance (3 of 15, the earlier partial held). No SLA (0 of 10). Products, Stores, Categories and Recommendations are generally available, and Buying Options is marked beta (8 of 10, the earlier partial held). Total 31.

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.

Maintenance & community CartAI +13

Best Buy Developer API 5

No dated API change was found. The documentation source was last committed on 26 April 2021 (0 of 30). No releases or dated entries in the last 90 days (0 of 20). A contact form and a GitHub organisation, with no changelog or forum that answers (3 of 15). The official SDKs are bestbuy 2.4.1, committed on 10 February 2021 per the JavaScript SDK repository, and a PHP SDK last changed in 2017, so they are not current (2 of 15). The JavaScript SDK pins axios ^0.21.1 (0 of 10). Total 5.

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.

Security & auth CartAI +11

Best Buy Developer API 32

One API key per developer with no scopes, passed as the apiKey query parameter, which is the documented and only option (20 less 10 for a secret in the URL, 10 of 30). The public APIs are read-only, and ordering sits behind a separate invite-only key (15 of 20). Responses include product names and descriptions written by Best Buy and its suppliers, and no guidance on treating them as data was found (5 of 15). No call log for the key holder was found. Best Buy emails the holder when a limit is exceeded (2 of 15). security.txt returned 404 on developer.bestbuy.com on 10 November, and no disclosure policy, bug bounty or certification was found (0 of 20). Total 32.

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.

Score by category

CategoryWeightBest Buy Developer APICartAIEdge
Reliability16%3118Best Buy Developer API +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4559CartAI +14
Agent ergonomics13%7249Best Buy Developer API +23
Security & auth14%3243CartAI +11
Payments & pricing10%4530Best Buy Developer API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%518CartAI +13
Transparency & trust7%4045CartAI +5
Negative events≤150-3
TotalE 40.4/100F 34.9/100

Facts side by side

FactBest Buy Developer APICartAI
KindHTTP APIHTTP API
VendorBestBuy.com, LLC (Best Buy Co., Inc.)CartAI
Hosted endpointhttps://api.bestbuy.com/v1/no (local only)
TransportsHTTPstdio
AuthAPI keyAPI key
PricingFreeFreemium
x402nono
LicenceProprietary service under the Best Buy Developer API terms. The SDKs in the BestBuyAPIs GitHub organisation are open sourcenone
Tools exposednone8
Read-only variant documentednono
llms.txtnoyes
Last releasenone2026-07-20
Terms last updated2021-02-232026-05-13
Privacy policy last updatedcouldn't be read2026-05-13
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Best Buy Developer API

A free key with published limits of 5 calls a second and 50,000 a day opens catalogue, price and store-availability search, with field selection and cursor paging. Ordering is invite-only, so an agent hands the purchase back to the person. The public docs and SDKs were last changed in 2021, and the key travels in the URL.

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.

Before you call either

Best Buy Developer API

  1. Add format=json to Products, Stores and Categories calls. XML is the default for those three
  2. Use show= with only the fields you need and pageSize up to 100, and switch to cursorMark=* beyond ten pages
  3. Batch SKU lookups with the in operator to stay under 5 calls a second. A 403 can mean the limit, not a bad key
  4. Send the person to the product URL to buy. The Commerce API that places orders needs a partner invitation
  5. Cache responses for no more than 72 hours and refresh prices before quoting them, as the terms require

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

Questions

Which is better for AI agents, Best Buy Developer API or CartAI?

Best Buy Developer API scores 40.4 (E) on agent readiness against CartAI's 34.9 (F), and leads in 3 of 7 scored categories. CartAI leads on schema & documentation, security & auth, maintenance & community and transparency & trust.

Do Best Buy Developer API and CartAI need an API key?

Both need an API key.

Can an agent call Best Buy Developer API and CartAI without installing anything?

Best Buy Developer API has a hosted endpoint at https://api.bestbuy.com/v1/. CartAI runs on your own machine, with no hosted endpoint listed.

Other comparisons with Best Buy Developer API or CartAI

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.