GridX · Rate Limits

Gridx Rate Limits

GridX's Calculate and Empower APIs are partner/enterprise APIs provisioned per utility deployment. Authentication uses short-lived JWT bearer tokens (roughly one-hour expiry) for the Customer Information and Usage endpoints, with a separate token flow for OpenADR. GridX does not publish specific request-per- minute, request-per-day, or quota values; any rate limiting, concurrency caps, and batch-processing constraints are governed by the deployment contract and are not reconciled in this artifact.

Gridx Rate Limits is the machine-readable rate-limit profile for GridX on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests, seconds, and jobs.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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

Tagged areas include Energy, Utilities, Rate Engine, Billing, and Rate Analytics.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
EnergyUtilitiesRate EngineBillingRate AnalyticsRate LimitingQuotasThrottling

Limits

API Request Limits deployment
requests
see provider / contract documentation
Not publicly published; governed by the utility deployment agreement.
Token Expiry account
seconds
~3600
JWT bearer tokens from the /token endpoint expire after approximately one hour and must be refreshed.
Batch Rate Analysis deployment
jobs
see provider / contract documentation
Empower batch rate-analysis throughput is contract-governed; not publicly documented.

Policies

Token-Based Authentication
Customer Information/Usage endpoints require a JWT bearer token; OpenADR uses a separate token flow.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/gridx-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.