Pricing & Metering — Reference
Reference structure for documentation and quoting. Not a rate card: no number here is binding until finance and counsel have signed it off.
Subscription tiers
| Plan | Price | Included | Notes |
|---|---|---|---|
| Developer | $0/month | 10,000 calls, sandbox only, limited datasets | No SLA. |
| Growth | $99–$299/month | 100,000 calls, production API, webhooks, usage reports | |
| Business | $500–$2,500/month | 1M+ calls, advanced APIs, higher rate limits, support | |
| Enterprise | Contract | Volume pricing, partner APIs, bulk datasets, SLA, dedicated credentials | Access negotiated per contract. |
| Strategic / Utility | Contract | Trading, settlement, DER, grid, market integration, private endpoints, dedicated infrastructure | Production credentials only, under contract. |
Per-call metering
Every billable call is priced by the class of operation it is, not by its path, and drawn from the account's prepaid usage wallet:
| Billing class | Reference price | Example operation |
|---|---|---|
| Basic call | $0.001 | GET /plans, GET /customers/{id}, GET /usage/{id}, GET /enrollments, GET /enrollments/funnel |
| Address serviceability | $0.005 | GET /utilities/lookup |
| Market query | $0.01 | (not yet offered) |
| Forecast calculation | $0.025 | GET /usage/{id}/forecast |
| Quote | $0.05 | (not yet offered) |
| Enrollment transaction | $0.25 | POST /enrollments, POST /enrollments/{id}/transition (each move) |
| Complex optimization | $0.50+ | trade execution, under contract |
Catalog reads (GET /utilities) are not billed. A call refused for any
reason — including a usage limit — is not billed either.
Why documentation drives adoption, not the reverse
The intended growth loop: more documentation → more integrations → more calls → more revenue, not less documentation → fewer people understand the API → fewer integrations. Use cases, capabilities and example requests are published openly (API Overview), and the full reference is open to every signed-in developer, sandbox accounts included. The implementation, models and infrastructure stay proprietary.