Data Center API Access: Developer Integration Guide

What the API does

Use the API to request modeled site scores in your own workflow. Compare candidate sites or add a screen to an internal review. The result is a starting point for more work. It is not a decision to buy land, bind insurance or approve a project.

The API does not give raw database access. It does not confirm spare power, local support or a permit outcome. A nearby grid asset is a location fact, not a utility commitment. Keep the evidence limits with each result you share.

Authentication and batch limits

Sign in with an eligible subscription to manage API keys. Create or revoke a key in the controls below. Store it securely on your server. Do not put it in public browser code or a shared report.

The documented endpoint is POST /api/v1/score. Send an X-API-Key header and JSON site inputs. Current documented limits are 500 sites per call and 5,000 sites per day. Check your account access and the endpoint docs before you plan a production integration.

Use the results with care

Screen a shortlist before ordering expert studies. Add site context to a broker's deal file. Help an insurance team plan its next review. None of these uses replaces engineering, legal advice, utility confirmation or underwriting judgment.

Store the site identity, score date and limits with the result. A screen is not proof that a parcel is viable. Missing facts are not good news. Handle failed requests openly; do not publish an incomplete result.

Getting started

Sign in, check access, read the example and create a key. Start with a small batch. Check the response and make sure your team knows the evidence limits. Keep score requests separate from any configured subscription monitoring. A one-time API call does not start continuous change detection.

Review pricing or ask support which option fits your work before sending sensitive deal files. You can read this public guide without signing in. Account controls stay protected.

A scoring request example

Set API_BASE_URL to the published site origin and replace YOUR_API_KEY with your own key on your server. This is an illustrative site input, not a project result.

curl -X POST "$API_BASE_URL/api/v1/score" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{"sites":[{"name":"Example site","city":"Phoenix","state":"AZ","latitude":33.44841,"longitude":-112.07404,"capacity_mw":80}]}'

Review pricing · Contact support

Sign in required

API access requires a subscription account.

Free tools show nearby infrastructure facts. Paid API access integrates modeled viability outputs; continuous change detection is provided through configured subscription monitoring.