Skip to main content
Quick Summary: Requests are counted per key, per hour, in three buckets: reads, writes and bulk. Every response carries RateLimit-* headers so you always know where you stand.
Current status: limits are measured but not yet enforced. The numbers below are provisional; they will be finalized from real usage data and announced to all credential holders before enforcement is switched on. Build your integration against the headers now and enforcement will never surprise you.

​
Buckets and provisional allowances

A per-key allowance override is possible for legitimate high-volume integrations — talk to your SkillsDB contact.

​
The headers

If SkillsDB cannot count a request, the request is still served: the response carries RateLimit-Degraded: true in place of the three headers above, and nothing is counted against your allowance. Treat it as “allowance unknown” and keep your usual pace. Once enforcement is on, exceeding an allowance returns 429 rate-limit-exceeded with Retry-After. Windows are fixed UTC hours.