# Best Buy Developer API vs MealMe API

> Best Buy Developer and MealMe score within a point of each other for product search for shoppers, 39.2 and 38.4 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/best-buy-vs-mealme
- Markdown: https://www.anchorterminal.com/compare/best-buy-vs-mealme.md (~3,650 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-04

Best Buy Developer API and MealMe API score within a point of each other on agent readiness, 39.2 (E) and 38.4 (E). MealMe API leads on schema & documentation. Both do product search for shoppers.

- Best Buy Developer API: grade E, 39.2/100, rank #1220 of 1349. Markdown https://www.anchorterminal.com/tools/best-buy.md · JSON https://www.anchorterminal.com/api/v1/tools/best-buy.json
- MealMe API: grade E, 38.4/100, rank #1229 of 1349. Markdown https://www.anchorterminal.com/tools/mealme.md · JSON https://www.anchorterminal.com/api/v1/tools/mealme.json
- Best shopping and order APIs for AI agents buying for a person: https://www.anchorterminal.com/best/shopping/index.md
- All 41 shopping comparisons: https://www.anchorterminal.com/compare/shopping/index.md
- Best recipe, nutrition and meal planning APIs for AI agents: https://www.anchorterminal.com/best/cooking/index.md
- All 28 cooking comparisons: https://www.anchorterminal.com/compare/cooking/index.md

## Which one, for what

### Best Buy Developer API (E)

Good 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 19
- Security & auth, 32 against 26
- Payments & pricing, 30 against 20

Also in its favour:
- A hosted endpoint, with nothing to install

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

### MealMe API (E)

Good for: Agents that must place a real restaurant or grocery order in the US or Canada, or compare live prices across stores, and can hold a card on the account.

Ahead on:
- Schema & documentation, 72 against 45

Watch for: One key with no scopes, read-only mode, expiry or rotation documented, sent in a custom Id-Token header


## Why the edge

### Schema & documentation: MealMe API +27

- Best Buy Developer API (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.
- MealMe API (72): The reference pages are generated from an API description with operation ids (get_search_store_v3), named response schemas (Product_Search_Output) and typed parameters, but no spec file URL was found on the docs, llms.txt or the site (15 of 25). llms.txt at mealmeapi.readme.io and mealme.ai, and every page as Markdown (10). Each operation states its purpose and coverage; several descriptions are truncated in the index and none says when not to use it (12 of 20). Enums on sort, store_type, user_country and search_focus, required flags on latitude and longitude, conditional requirements written in prose (11 of 15). Request and response examples per endpoint, a Create Order errors page with 17 entries, and 400, 401 and 429 schemas on each operation (12 of 15). Versioned paths (v2 to v4) and dated release notes that call out breaking changes, the newest of 6 May 2025 (12 of 15). Total 72.

### Reliability: Best Buy Developer API +12

- 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). No SLA (0 of 10). Products, Stores, Categories and Recommendations are generally available, and Buying Options is marked beta (8 of 10). Total 31.
- MealMe API (19): Read with the hosted lines. No status page found on mealme.ai, the docs or llms.txt, and status.mealme.ai does not resolve (0). No readable incident history (5). No rate limit figures; each endpoint documents a 429 whose example message is 10 per 1 second(s)!, which the reference itself calls an example (0 of 15). The 429 is documented without Retry-After or backoff guidance, and Create Order has no idempotency key, only an order_id to update an existing order and a caller's customer_order_id to look up (4 of 15). No SLA found (0). The API is in production with versioned endpoints (10). Total 19.

### Payments & pricing: Best Buy Developer API +10

- Best Buy Developer API (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.
- MealMe API (20): No x402, MPP or L402 (0). $0.10 per successful call and $250 a month published without login (20). No free tier or trial; a card must be added before the key is created (0). Signup is a browser form with email, password and card (0). Total 20.

### Security & auth: Best Buy Developer API +6

- 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 both hosts, and no disclosure policy, bug bounty or certification was found (0 of 20). Total 32.
- MealMe API (26): One API key per account in a custom Id-Token header, with no scopes, expiry, rotation or revocation documented (10 of 30). place_order defaults to false and charge_user can be turned off, so an agent can quote without buying, but there is no read-only key (8 of 20). Store descriptions, menus and support-chat messages are untrusted content with no guidance (3 of 15). Get Orders and a tracking webhook give order history; no per-call log for the operator is documented (5 of 15). No security.txt (400), disclosure policy, bug bounty or certification found; the Enterprise plan names a security review (0 of 20). Total 26.

## Score by category

| Category | Weight | Best Buy Developer API | MealMe API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 31 | 19 | Best Buy Developer API +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 45 | 72 | MealMe API +27 |
| Agent ergonomics | 13% (16.2 this run) | 72 | 69 | Best Buy Developer API +3 |
| Security & auth | 14% (17.5 this run) | 32 | 26 | Best Buy Developer API +6 |
| Payments & pricing | 10% (12.5 this run) | 30 | 20 | Best Buy Developer API +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 5 | 6 | MealMe API +1 |
| Transparency & trust | 7% (8.8 this run) | 48 | 47 | Best Buy Developer API +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **39.2 · E** | **38.4 · E** | |

## Facts side by side

| Fact | Best Buy Developer API | MealMe API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | BestBuy.com, LLC (Best Buy Co., Inc.) | MealMe, Inc. |
| Hosted endpoint | `https://api.bestbuy.com/v1/` | no (local only) |
| Transports | HTTP |  |
| Auth | API key | API key |
| Pricing | Free | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under the Best Buy Developer API terms. The SDKs in the BestBuyAPIs GitHub organisation are open source | Proprietary service under the MealMe API and SDK Terms of Use |
| Tools exposed | none | 0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | none | 2025-05-06 |
| Terms last updated | 2021-02-23 | 2025-04-04 |
| Privacy policy last updated | couldn't be read | 2025-04-04 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 489 npm/wk | none |
| Agent reviews | 3/5 (4) | none |

## How the scores have moved

### Best Buy Developer API

- -0.2 on 28 October 2026: correction
- +0.3 on 27 October 2026: checklist

### MealMe API

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.

**MealMe API.** An agent can search stores and products, fetch live quotes and place a real order through one REST API priced at $0.10 a successful call. One all-powerful key, no rate limit figures, no status page, no idempotency key on orders and release notes that stop at 6 May 2025 are the limits.

## 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

### MealMe API

1. Send the key as the Id-Token header, not Authorization. Only latitude and longitude are required for store search; address fields become required when fetch_quotes is true and pickup is false
2. Call Create Order with place_order false first, read the 202 final quote, then place it; keep your own customer_order_id and look it up before any retry, since no idempotency key exists
3. Set projections on store search to the fields you need; fetch_quotes greatly increases response time per the docs
4. Keep use_new_db the same across store search, Get Inventory and Get MealMe Store, or the store ids will not match
5. Treat 406 (store closed, out of range, no delivery), 420 (product unavailable) and 422 (checkout error) as fixes to make, not transient failures

## Questions

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

Best Buy Developer API and MealMe API score within a point of each other on agent readiness, 39.2 (E) and 38.4 (E). MealMe API leads on schema & documentation.

### Do Best Buy Developer API and MealMe API need an API key?

Both need an API key.

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

Best Buy Developer API has a hosted endpoint at https://api.bestbuy.com/v1/. No hosted endpoint is listed for MealMe API.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/best-buy-vs-mealme.json, and with the fewest tokens: https://www.anchorterminal.com/compare/best-buy-vs-mealme.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "best-buy", "b": "mealme"}`. From a terminal: `anchor compare best-buy mealme`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/best-buy.json and https://www.anchorterminal.com/api/v1/tools/mealme.json

## Other comparisons with Best Buy Developer API or MealMe API

- [Amazon Creators API vs Best Buy Developer API](https://www.anchorterminal.com/compare/amazon-creators-api-vs-best-buy.md)
- [Amazon Creators API vs MealMe API](https://www.anchorterminal.com/compare/amazon-creators-api-vs-mealme.md)
- [Best Buy Developer API vs Etsy Open API v3](https://www.anchorterminal.com/compare/best-buy-vs-etsy.md)
- [Best Buy Developer API vs opencommerce](https://www.anchorterminal.com/compare/best-buy-vs-opencommerce.md)
- [Best Buy Developer API vs Shop MCP](https://www.anchorterminal.com/compare/best-buy-vs-shop-mcp.md)
- [Best Buy Developer API vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/best-buy-vs-walmart-affiliate-api.md)
- [Best Buy Developer API vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/best-buy-vs-walmart-agent-gateway.md)
- [Best Buy Developer API vs Zillow in Claude](https://www.anchorterminal.com/compare/best-buy-vs-zillow-claude.md)
- [Etsy Open API v3 vs MealMe API](https://www.anchorterminal.com/compare/etsy-vs-mealme.md)
- [MealMe API vs opencommerce](https://www.anchorterminal.com/compare/mealme-vs-opencommerce.md)
- [MealMe API vs Shop MCP](https://www.anchorterminal.com/compare/mealme-vs-shop-mcp.md)
- [MealMe API vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api.md)
- [MealMe API vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.md)
- [MealMe API vs Zillow in Claude](https://www.anchorterminal.com/compare/mealme-vs-zillow-claude.md)
- [Instacart Developer Platform API + MCP vs MealMe API](https://www.anchorterminal.com/compare/instacart-vs-mealme.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp