πππ‘πππ APIπππ‘πππ.πππ β
Search and retrieve Baxtel data center listings by region. Get power capacity (MW), coordinates, operator, status, and facility type for US data centers.
What is the πππ‘πππ API?
The Baxtel API covers 2 endpoints that expose structured data for data center facilities across US geographic regions. Use list_data_centers to browse facilities by state or metro area β returning operator name, size class, and operational status β then call get_data_center with a facility slug to retrieve power capacity in megawatts, WGS84 coordinates, year built, facility category, nearby sites, and linked documents.
curl -X GET 'https://api.parse.bot/scraper/658b7f08-058f-4af3-a0a2-ebea9d21c0ea/list_data_centers?page=1®ion=austin' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects β the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed Β· autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this APIβs typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API β it wonβt change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Baxtel SDK β bounded, re-runnable; every call capped."""
from parse_apis.api import Baxtel, DataCenterNotFound
client = Baxtel()
# List data centers in Austin, TX metro area
for facility in client.region("austin").list_facilities(limit=3):
print(facility.name, facility.company, facility.status)
# Drill-down: get full details for the first facility
item = client.region("austin").list_facilities(limit=1).first()
try:
detail = client.data_centers.get(slug=item.slug)
print(detail.name, detail.power_mw, detail.status)
print(detail.location.state, detail.location.metro)
print(detail.latitude, detail.longitude)
except DataCenterNotFound as e:
print(f"not found: {e.slug}")
# Navigate from summary to detail via .details()
summary = client.region("dallas").list_facilities(limit=1).first()
full = summary.details()
print(full.name, full.operator, full.year_built)
for site in full.nearby_sites[:2]:
print(site.distance, site.name)
print("exercised: region.list_facilities / data_centers.get / summary.details")
List data center facilities in a geographic region (state or metro/city). Returns name, operating company, size class, operational status, and facility type for each facility. City/metro-level regions return complete facility tables; state-level regions return top facilities with a total count. Results are paginated at 50 per page.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for paginated results. Each page returns up to 50 facilities. |
| regionrequired | string | Region slug identifying the geographic area (e.g. 'austin', 'dallas', 'houston', 'texas'). Use city/metro slugs for complete listings. |
{
"type": "object",
"fields": {
"page": "current page number",
"region": "display name of the region",
"facilities": "array of facility summaries with name, slug, company, size, status, type",
"region_slug": "slug used in the request",
"total_pages": "total number of pages",
"total_in_table": "number of facilities listed in the HTML table",
"total_in_region": "total number of facilities in the region (from map data)"
},
"sample": {
"data": {
"page": 1,
"region": "Austin",
"facilities": [
{
"name": "LOGIX Austin (1905 E 6th)",
"size": "Small",
"slug": "logix-austin-1905-e-6th",
"type": "Carrier",
"status": "Operational",
"company": "LOGIX Fiber Networks"
},
{
"name": "CyrusOne Austin I",
"size": "Small",
"slug": "cyrusone-austin-i",
"type": "Carrier-Neutral",
"status": "Operational",
"company": "CyrusOne"
}
],
"region_slug": "austin",
"total_pages": 2,
"total_in_table": 94,
"total_in_region": 94
},
"status": "success"
}
}About the πππ‘πππ API
Listing Facilities by Region
The list_data_centers endpoint accepts a region slug β such as austin, dallas, houston, or texas β and returns a paginated table of facilities, up to 50 per page. Each entry in the facilities array includes the facility name, slug, operating company, size class, status, and type. The response also exposes total_in_table (facilities found in the tabular listing) and total_in_region (the broader count derived from map coverage), so you can distinguish between the two counts when deciding how to paginate. City and metro slugs return complete facility tables; state-level slugs return the top facilities.
Retrieving Full Facility Details
Pass a facility slug obtained from list_data_centers to get_data_center for the full record. The response includes power_mw (total power capacity in megawatts, or null when not disclosed), latitude and longitude in WGS84, status values such as Operational, Under Construction, Announced, or Planned, and a category field distinguishing facility types like Hyperscale Data Center or Carrier-Neutral. The location object breaks the address hierarchy into metro, state, region, and country. Related documents β permits, press releases, or spec sheets β are returned as a documents array with title and URL.
Coverage and Scope
Coverage is US-focused. The API reflects Baxtel's indexed inventory of data center facilities and is particularly useful for Texas metros such as Austin, Dallas, and Houston, where hyperscale and colocation activity is dense. Facility slugs are stable identifiers that persist across calls, making them suitable as foreign keys when storing records locally.
The πππ‘πππ API is a managed, monitored endpoint for πππ‘πππ.πππ β not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when πππ‘πππ.πππ changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official πππ‘πππ.πππ API β it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes β contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Map all data centers in a Texas metro by iterating
list_data_centerspages and plottinglatitude/longitudefromget_data_center - Monitor construction pipelines by filtering
statusvalues for Under Construction or Announced across a state region - Compare power capacity across facilities using the
power_mwfield to identify large-scale hyperscale deployments - Build a colocation shortlist filtered by
category(e.g. Carrier-Neutral) for network-adjacent deployments - Track operator footprints by aggregating the
operatorfield across all facilities returned for a metro - Enrich internal asset databases with
year_built,power_mw, andlocationfields keyed by facility slug - Identify document trails (permits, announcements) via the
documentsarray returned byget_data_center
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call β most fall between 1 and 10 credits β shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Baxtel offer an official developer API?+
What does `list_data_centers` return at the state level versus a city level?+
dallas, austin) return complete facility tables with pagination. State-level slugs (e.g. texas) return only the top facilities surfaced in the listing, so total_in_table may be smaller than total_in_region. Use metro slugs when you need full coverage of a market.When is `power_mw` null in `get_data_center` responses?+
power_mw field is null when a facility has not disclosed its power capacity on Baxtel. This is common for smaller colocation sites and facilities in early announced or planned stages. The status and category fields are still populated for those records.Does the API cover data centers outside the United States?+
Can I filter facilities by power capacity or status directly in `list_data_centers`?+
list_data_centers endpoint does not expose filter parameters for power_mw or status β those fields are only returned in the summary response. Filtering requires fetching full records via get_data_center and applying logic client-side. You can fork the API on Parse and revise it to add server-side filtering if needed.