Bureau of Ocean Energy Management · Rate Limits
Bureau Of Ocean Energy Management Rate Limits
Bureau Of Ocean Energy Management Rate Limits is the rate-limit profile for Bureau of Ocean Energy Management on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
The profile also includes 2 backoff/retry policies defined.
Tagged areas include Energy, Federal Government, Marine, Ocean, and GIS.
0 Limits
Read from the provider's live responses on 2026-09-05 — live unauthenticated calls against gis.boem.gov/server/re....
View Source
Limits
Bureau of Ocean Energy Management publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
REPLACES A SCAFFOLD. Until this pass this file declared per-tier limits (10 rpm free,
100 rpm professional, 1,000 rpm enterprise), an X-RateLimit-* header family and a 429
exhaustion code. None of it was observed and none of it is published — it came from the
2026-05-04 bulk sweep stamped `method: generated`. It is removed rather than left to be
read as BOEM's runtime contract.
THE TRUTH: BOEM documents no rate limits anywhere, and the services emit no rate-limit
signal. A full header capture on 2026-09-05 returned Cache-Control, ETag, Vary,
X-Content-Type-Options, Strict-Transport-Security, Connection, Keep-Alive and a TS01*
load-balancer cookie — no X-RateLimit-*, no RateLimit-*, no Retry-After.
An honest zero is the finding, and it is a real risk to a consumer: with no published limit
and no runtime signal, an agent has no way to learn it is being throttled except by a request
failing. The one real ceiling on the surface is not a rate limit at all — it is
maxRecordCount 10000 per feature query, a PAGE size, reported by every layer and paired with
`exceededTransferLimit` in the response body.
EnergyFederal GovernmentMarineOceanGISOffshoreEnvironmental
Policies
Conditional GET
responses carry ETag with must-revalidate. Poll with If-None-Match rather than refetching; it is the only cooperative behaviour the surface actually supports.
Unknown ceiling
no throttle is documented or signalled. Treat unexplained failures as possible server-side load shedding and back off exponentially with jitter, because nothing on the wire will tell you otherwise.
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.