BuyWhere · Rate Limits

Buywhere Rate Limits

BuyWhere applies per-key rate limits keyed off the API key prefix: `bw_free_*` keys are limited to 60 requests/minute (and 1,000 calls/month per llms.txt); `bw_live_*` keys to 600 requests/minute; `bw_partner_*` keys are advertised as unlimited. Rate-limit responses use HTTP 429 and the documented MCP error code `rate_limited`. Per-minute and daily quotas are returned in the `/v1/auth/register` response under `rate_limit.rpm` and `rate_limit.daily`. Marked unreconciled because BuyWhere has not yet published a formal rate-limit reference page.

Buywhere Rate Limits is the machine-readable rate-limit profile for BuyWhere on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests_per_minute and requests_per_month.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.

Tagged areas include E-commerce, Shopping, Price Comparison, SEA, and Southeast Asia.

4 Limits Throttle: 429 Quota: 429
E-commerceShoppingPrice ComparisonSEASoutheast AsiaAI AgentsRate LimitingMCP

Limits

Free tier per-minute rate limit api-key
requests_per_minute · minute
60
Documented in the MCP guide under "Authentication".
Free tier monthly quota api-key
requests_per_month · month
1000
Documented in llms.txt as "Free tier: 1,000 API calls/month."
Live tier per-minute rate limit api-key
requests_per_minute · minute
600
Documented in the MCP guide as the production tier rate.
Partner tier rate limit api-key
requests_per_minute · minute
unlimited
Advertised as unlimited for platform data partners; subject to negotiated agreement.

Policies

MCP-aware error handling
MCP responses surface the `rate_limited` error code; REST responses use HTTP 429. Implement exponential backoff and respect `Retry-After`.
Compact mode reduces effective cost
`compact=true` on /products/search returns a minimal payload; agents that only need ranking attributes should prefer compact responses to lower bandwidth and processing.
Cache friendly
`meta.cached` indicates whether the response was served from cache. Stable queries (e.g., category listings) frequently return cached responses with sub-50ms latency.

Sources