hour limit is per store shared

Not specified by the original author.

TL;DR

Page tightly and cache product data instead of re-pulling, since one chatty integration can starve the others.

Steps

1. When you plan a BigCommerce sync, budget 20,000 requests per hour per store total, not per credential. Multiple integrations on the same store share the pool, so coordinate or stagger them. Page tightly and cache product data instead of re-pulling, since one chatty integration can starve the others.

When to use

You are seeing this: When you plan a BigCommerce sync, budget 20,000 requests per hour per store total, not per credential. Use this skill when you run into "BigCommerce API: the 20k requests per hour limit is per store, shared".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #17971576 (accepted answer, 4 votes): the asker worried about pulling 20k+ orders. Per BigCommerce support, the 20,000 requests per hour limit applies per store and is shared across all API credentials for that store.

Verified resolution: When you plan a BigCommerce sync, budget 20,000 requests per hour per store total, not per credential. Multiple integrations on the same store share the pool, so coordinate or stagger them. Page tightly and cache product data instead of re-pulling, since one chatty integration can starve the others.

Source URL: https://stackoverflow.com/questions/17971576/does-bigcommerce-have-any-restriction-on-number-of-api-calls-made-from-one-api-k

Not specified by the original author.

TL;DR

Spread large order and catalog syncs across the hour window, and if you run multiple integrations on one store, coordinate their call volume against the single shared budget.

Steps

1. When you plan bulk pulls against the BigCommerce API, budget against the store, not the key. The 20k requests per hour ceiling is shared by every API key on the store, so adding more keys or parallel workers does not raise it. Spread large order and catalog syncs across the hour window, and if you run multiple integrations on one store, coordinate their call volume against the single shared budget.

When to use

You are seeing this: When you plan bulk pulls against the BigCommerce API, budget against the store, not the key. Use this skill when you run into "BigCommerce API: the 20k requests per hour limit is per store, shared by all keys".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #17971576 (accepted answer, 4 votes): the asker pulled order and product data for stores with 20k+ orders and wanted to know the per-API call limits. BigCommerce support confirmed the 20k requests per hour limit applies to the store as a whole and is shared across all API keys on that store.

Verified resolution: When you plan bulk pulls against the BigCommerce API, budget against the store, not the key. The 20k requests per hour ceiling is shared by every API key on the store, so adding more keys or parallel workers does not raise it. Spread large order and catalog syncs across the hour window, and if you run multiple integrations on one store, coordinate their call volume against the single shared budget.

Source URL: https://stackoverflow.com/questions/17971576/does-bigcommerce-have-any-restriction-on-number-of-api-calls-made-from-one-api-key-or

Not specified by the original author.

Brave Search API free tier: 1 req/sec, so serialize calls and retry 429s

TL;DR

Brave Search API free tier: 1 request/second, 2,000/month. Treat these as hard rules: - Never run searches in parallel. One query at a time; refine from the result before issuing the next.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

• A 429 on the free plan usually means you exceeded 1 rps, not that the monthly quota is gone. Sleep ~1.1s and retry with backoff instead of declaring the key dead. - Use a cross-process lock if multiple processes or threads can search, so pacing holds globally. - Log the remaining monthly quota (response header X-RateLimit-Remaining) after each call. Read that line before concluding the key is exhausted. - If 429s survive retries, the month's quota is spent; wait for the reset or upgrade rather than hammering. Rate-limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) are your pacing source of truth; use X-RateLimit-Reset for the backoff instead of guessing.

Context: Web (agent-config brave-search SKILL.md): the Brave Search API free plan allows 1 request per second and 2,000 requests per month. The documented rule: never issue calls in parallel; one query at a time. The reference implementation paces requests through a cross-process lock and retries 429 with backoff, so concurrent invocations serialize to ~1.1s apiece instead of failing. Every run prints the remaining monthly quota (e.g. "monthly quota remaining: 1965/2000"); read that line before concluding the key is exhausted, because a 429 at 1 rps is pacing, not quota exhaustion.

Source: Web (agent-config brave-search SKILL.md): the Brave Search API free plan allows 1 request per second and 2,000 requests per month. The documented rule: never issue calls in parallel; one query at a time. The reference implementation paces requests through a cross-process lock and retries 429 with backoff, so concurrent invocations serialize to ~1.1s apiece instead of failing. Every run prints the remaining monthly quota (e.g. "monthly quota remaining: 1965/2000"); read that line before concluding the key is exhausted, because a 429 at 1 rps is pacing, not quota exhaustion.

Verified resolution: Brave Search API free tier: 1 request/second, 2,000/month. Treat these as hard rules: - Never run searches in parallel. One query at a time; refine from the result before issuing the next. - A 429 on the free plan usually means you exceeded 1 rps, not that the monthly quota is gone. Sleep ~1.1s and retry with backoff instead of declaring the key dead. - Use a cross-process lock if multiple processes or threads can search, so pacing holds globally. - Log the remaining monthly quota (response header X-RateLimit-Remaining) after each call. Read that line before concluding the key is exhausted. - If 429s survive retries, the month's quota is spent; wait for the reset or upgrade rather than hammering. Rate-limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) are your pacing source of truth; use X-RateLimit-Reset for the backoff instead of guessing.

Source URL: https://github.com/junghan0611/agent-config/blob/HEAD/skills/brave-search/SKILL.md