Using the public sandbox

The public sandbox is backed by a public endpoint that needs no API key, no signup and no browser. It runs on live production plans, so what you see is what your customers see. Anything you can run in the public sandbox, you can run from a script or an AI coding assistant.

10 free calls per IP. Loading the public sandbox and browsing the schema are free — only real queries count against it. It is a one-time allowance, not a daily one, so it is meant for evaluating the data rather than running a workload. Request an API key to call production directly.

What you can run

Query	What it answers
`residentialPlans`	Residential plans, rates, fees and enrollment links for a ZIP
`businessPlans`	Commercial plans for a ZIP and annual usage
`utilities`	Which utilities serve a ZIP code
`nextStartDate`	Earliest available service start date
`energyInfoByState`	State average rate and generation mix

What it will not run

utilityAccounts is not available in the public sandbox. It looks up real customer service accounts by street address, so it stays behind an issued API key. The public sandbox is read-only: mutations and subscriptions are rejected.

Calling it from code

curl -s -X POST https://powerhq-playground-api.powerhq.workers.dev/graphql \
  -H "Content-Type: application/json" \
  -d '{"query": "{ utilities(zipCode: \"75231\") { id name } }"}'

Responses carry X-RateLimit-Limit and X-RateLimit-Remaining so a client can see what it has left. Once the allowance is used up the endpoint returns 429 with a GraphQL-shaped error, and it does not refill — an API key is the way forward from there.

For AI agents

Schema introspection is enabled and does not count against the limit, so an agent can discover the whole API before writing a single query:

curl -s -X POST https://powerhq-playground-api.powerhq.workers.dev/graphql \
  -H "Content-Type: application/json" \
  -d '{"query": "{ __schema { queryType { fields { name } } } }"}'

That returns every available query with its arguments and return types. From there, build a normal GraphQL query and post it to the same endpoint.

Moving to your own key

With an issued key you call the API directly. The Sandbox environment returns test plans for building and testing. Production returns live plans:

curl -s -X POST https://eapi.prod.powerhq.co/graphql \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "{ utilities(zipCode: \"75231\") { id name } }"}'

Integrate with PowerHQ

PowerHQ API

Core Concepts

Queries

Public sandbox

Reference

Using the public sandbox

What you can run

What it will not run

Calling it from code

For AI agents

Moving to your own key

​What you can run

​What it will not run

​Calling it from code

​For AI agents

​Moving to your own key

What you can run

What it will not run

Calling it from code

For AI agents

Moving to your own key