# Fix list: Best Buy Developer API From Anchor Terminal's listing at https://www.anchorterminal.com/tools/best-buy, the October 2026 research run, assessed 14 October 2026. Grade E, 39.1 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on Best Buy Developer API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Reliability, 31 out of 100, up to 13.8 more on the total Why it scored 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). No SLA (0 of 10). Products, Stores, Categories and Recommendations are generally available, and Buying Options is marked beta (8 of 10). Total 31. The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 2. Security & auth, 32 out of 100, up to 11.9 more on the total Why it scored 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 both hosts, and no disclosure policy, bug bounty or certification was found (0 of 20). Total 32. The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 3. Schema & documentation, 45 out of 100, up to 8.9 more on the total Why it scored 45: No OpenAPI or similar contract. A Postman collection is linked from the docs (8 of 25). 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 (5 of 15). Total 45. The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## 4. Payments & pricing, 30 out of 100, up to 8.8 more on the total Why it scored 30: 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. The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## 5. Maintenance & community, 5 out of 100, up to 8.3 more on the total Why it scored 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 on npm from February 2021 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. The API still answered on 14 October 2026. The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## 6. Agent ergonomics, 72 out of 100, up to 4.6 more on the total Why it scored 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. The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 7. Transparency & trust, 47 out of 100, up to 4.6 more on the total Made of editorial 32, provenance 62. Why it scored 47: Closed service with dated terms that state limits, caching and termination clearly (15 of 30). The Best Buy privacy policy, updated 1 January 2026, names Best Buy Co., Inc. and categories of service providers, but gives no general retention period and nothing specific to API data (12 of 30). No deprecation policy, and the terms allow ending the service at any time with or without notice (0 of 20). Service providers are named by type, with no subprocessor list or data locations (5 of 20). Total 32. The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - Terms of service: read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points (5.1 of 10) - Privacy policy: published, but our reader couldn't read it (7 of 10) - Status page: not found (0 of 10) - Changelog: not found (0 of 10) - security.txt: not found (0 of 10) ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - unchecked: whether a new key is activated automatically. The signup at developer.bestbuy.com/login needs a person and was not completed. - unchecked: the Commerce API documentation, terms and sandbox, which are shared only after an invitation. - unchecked: Best Buy checkout inside ChatGPT, Google AI Mode and Wizard. Press reports describe these, but no Best Buy developer page documents an interface an outside agent can use. - The docs link an affiliate programme page at developer.bestbuy.com/affiliate-program, which returned 404 on 14 October 2026. - The terms mention a Reviews API in the call limits, but the developer site does not list one. ## Weaknesses - Ordering, fulfilment, order lookup and cancellation are only in the Commerce API, which is invite-only with documentation shared after approval - The API key is sent as the apiKey query parameter, so it appears in URLs and logs - The public documentation repository was last changed on 26 April 2021 and the JavaScript SDK 2.4.1 dates from February 2021 - No status page, changelog, security.txt or disclosure programme was found - Over-limit calls return 403, the same code as an invalid key, with no Retry-After ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - 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 ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.