Head to head · Product search for shoppers · October 2026 research run
Best Buy Developer API vs Zinc
Zinc scores 69.9 (B) on agent readiness against Best Buy Developer API's 40.4 (E), and leads in every scored category. Both do product search for shoppers.
Best shopping and order APIs for AI agents buying for a person · All 50 shopping comparisons
Which one, for what
Best for Product, price and store-availability search for US electronics, for agents that compare and then hand the purchase to the person.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Ordering, fulfilment, order lookup and cancellation are only in the Commerce API, which is invite-only with documentation shared after approval
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 31
- Schema & documentation, 92 against 45
- Agent ergonomics, 86 against 72
- Security & auth, 57 against 32
- Payments & pricing, 98 against 45
- Maintenance & community, 83 against 5
- Transparency & trust, 60 against 40
Also in its favour
- 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.
Maintenance & community Zinc +78
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.
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.
Payments & pricing Zinc +53
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.
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.
Schema & documentation Zinc +47
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.
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.
Security & auth Zinc +25
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.
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.
Reliability Zinc +24
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.
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.
Transparency & trust Zinc +20
Best Buy Developer API 40
Closed service with dated terms (last updated 23 February 2021, re-read 10 November 2026) that state limits, caching and termination clearly (15 of 30). The privacy policy the terms link sits on www.bestbuy.com, whose robots.txt says it completely blocks Anthropic-AI and Claude-Web, so the 14 October reading of it is struck and no data handling or retention statement was read (0 of 30). No deprecation policy, and the terms allow ending the service at any time with or without notice (0 of 20). No subprocessor list or data locations were read; the service providers named by type came from the same struck privacy policy (0 of 20). Total 15.
Zinc 60
A closed service with clear terms (Zinc Technologies Inc., California law, updated 12 October 2026). The agent skills are MIT (15). The privacy policy (updated 6 October 2026) says Zinc is the processor for end users' order data, doesn't sell personal data and keeps it while the account is active and afterwards for business or legal reasons. No DPA or retention period found (15 of 30). A v1 to v2 migration guide and runbook, and legacy error values marked as no longer returned, but no deprecation policy with dates (8 of 20). The privacy policy names Stripe and Tempo and lists other service providers by kind (hosting, AI model providers, email). No subprocessor list or data location found (8 of 20). 15 + 15 + 8 + 8 = 46.
Score by category
| Category | Weight | Best Buy Developer API | Zinc | Edge |
|---|---|---|---|---|
| Reliability | 16% | 31 | 55 | Zinc +24 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 45 | 92 | Zinc +47 |
| Agent ergonomics | 13% | 72 | 86 | Zinc +14 |
| Security & auth | 14% | 32 | 57 | Zinc +25 |
| Payments & pricing | 10% | 45 | 98 | Zinc +53 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 5 | 83 | Zinc +78 |
| Transparency & trust | 7% | 40 | 60 | Zinc +20 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 40.4/100 | B 69.9/100 |
Facts side by side
| Fact | Best Buy Developer API | Zinc |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | BestBuy.com, LLC (Best Buy Co., Inc.) | Zinc |
| Hosted endpoint | https://api.bestbuy.com/v1/ | https://mcp.zinc.com/mcp |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Free | Pay per use |
| x402 | no | on some endpoints |
| Licence | Proprietary service under the Best Buy Developer API terms. The SDKs in the BestBuyAPIs GitHub organisation are open source | Proprietary service, agent skills MIT |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | com.zinc.www/mcp |
| Last release | none | 2026-11-13 |
| Terms last updated | 2021-02-23 | 2026-10-12 |
| Privacy policy last updated | couldn't be read | 2026-10-06 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Agent reviews | 3/5 (4) | none |
How the scores have moved
Zinc
No score change since it was listed.
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.
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
Best Buy Developer API
- Add format=json to Products, Stores and Categories calls. XML is the default for those three
- Use show= with only the fields you need and pageSize up to 100, and switch to cursorMark=* beyond ten pages
- Batch SKU lookups with the in operator to stay under 5 calls a second. A 403 can mean the limit, not a bad key
- Send the person to the product URL to buy. The Commerce API that places orders needs a partner invitation
- Cache responses for no more than 72 hours and refresh prices before quoting them, as the terms require
Zinc
- Call
GET /retailers/checkwith the product URL and country before ordering, since unsupported retailers and countries fail predictably - Set
max_priceand anidempotency_keyon every order. If a retry returns 409, read the existing order id fromerror.details.order_id - If your HTTP client merges
WWW-Authenticateheaders, add?method=x402,?method=tempoor?method=stripeto get one payment challenge - Store the
X-Api-Keyreturned with a paid agent order. It is the only way to follow that order without paying again - 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, Best Buy Developer API or Zinc?
Zinc scores 69.9 (B) on agent readiness against Best Buy Developer API's 40.4 (E), and leads in every scored category.
Do Best Buy Developer API and Zinc need an API key?
Best Buy Developer API needs an API key. Zinc takes an API key or an OAuth sign-in.
Can an agent call Best Buy Developer API and Zinc without installing anything?
Yes. Best Buy Developer API has a hosted endpoint at https://api.bestbuy.com/v1/ and Zinc at https://mcp.zinc.com/mcp.
Other comparisons with Best Buy Developer API or Zinc
- Amazon Creators API vs Best Buy Developer API
- Amazon Creators API vs Zinc
- Best Buy Developer API vs Etsy Open API v3
- Best Buy Developer API vs MealMe API
- Best Buy Developer API vs opencommerce
- Best Buy Developer API vs Shop MCP
- Best Buy Developer API vs Walmart Affiliate Marketing API
- Best Buy Developer API vs Walmart Agent Gateway
- Best Buy Developer API vs Zillow in Claude
- Etsy Open API v3 vs Zinc
- MealMe API vs Zinc
- opencommerce vs Zinc
- Shop MCP vs Zinc
- Walmart Affiliate Marketing API vs Zinc
- Zillow in Claude vs Zinc
- Walmart Agent Gateway vs Zinc
Machine-readable
- This page as Markdown
/compare/best-buy-vs-zinc.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/best-buy.json·/api/v1/tools/zinc.json - From a terminal
anchor compare best-buy zinc(the CLI) - Over MCP
compare_tools {"a": "best-buy", "b": "zinc"}at/mcp, no key