Datasets & API

Louisiana AI Data Index.

Source-linked Louisiana ecosystem and infrastructure records in JSON and CSV, plus a separately labeled global AI real-estate evidence guide, OpenAPI, docket data, methodology, and citation format. Built for journalists, policy groups, universities, vendors, and diligence teams.

Ecosystem JSON Real-estate evidence JSON Download CSV Download JSON Cite the index

$ curl https://louisianai.com/api/v1/ecosystem

{

"version": "2026.08.01.2",

"core_count": 9,

"activity_count": 8,

"activities": [...]

}

Current facts · source-backed excerpt

The quotable version.

$65.6B+ disclosed-capex floor across 4 core Louisiana AI infrastructure records
5,760 MW of published site power; undisclosed figures are not estimated
10-17 GW Entergy system-wide large-load pipeline cited in 2026 coverage
Meta Hyperion has a confirmed 5GW build-out in Richland Parish
Four LPSC control dockets normalize the current power/regulatory story
Project Sucre, Meta Hyperion, and Richland Parish Data Center are canonicalized as one campus
Act 730 is the statutory anchor for Louisiana data-center sales/use tax relief
The public registry covers Meta, Amazon/STACK, Hut 8, Applied Digital, and emerging central/north Louisiana projects
Topic hubs separate power, water, workforce, incentives, and permitting claims
Every load-bearing project page carries source links and confidence labels
Public exports ship in CSV, JSON, OpenAPI, RSS, and JSON Feed formats

Quarterly snapshot

What changed this quarter.

01Added LPSC docket tracker for U-37425, U-37882, U-37853, and X-37921.
02Canonicalized Project Sucre, Meta Hyperion, and Richland Parish Data Center aliases.
03Expanded machine-readable distributions with dedicated docket CSV and JSON.

Citation format: LouisianAI, Louisiana AI Infrastructure Index, accessed May 15, 2026, https://louisianai.com/datasets.

Downloadable datasets

6 datasets, versioned weekly.

JSON

ai-real-estate-impact.json

Global AI/data-center real-estate evidence with a separately labeled Louisiana diligence lens

2026.08.01.1 · Live JSON

ai-ecosystem.json

Verified Louisiana AI nodes plus dated companies, events, funding, procurement, and public use cases

2026.08.01.2 · Live JSON

projects.json

Every tracked LA infrastructure project

v8.14 · 132 KB CSV

projects.csv

Spreadsheet form, same payload

v8.14 · 89 KB CSV

lpsc-dockets.csv

All hyperscaler-relevant dockets

2026.05.15 · 18 KB JSON

lpsc-dockets.json

Plain-English LPSC docket tracker

2026.05.15 · 24 KB

API endpoints

RESTful, versioned, rate-limited.

GET/api/v1/real-estate-impactGlobal AI real-estate evidence guide with Louisiana scope guardrails

GET/api/v1/ecosystemVerified statewide AI nodes and lifecycle-aware activity registry

GET/api/v1/projectsAll tracked projects · filter by parish, operator, status

GET/api/datasets/lpsc-dockets/jsonSource-linked LPSC data center docket tracker

GET/api/datasets/lpsc-dockets/csvCSV version of the LPSC docket tracker

GET/api/v1/projects/{id}One project profile + canonical public profile path

GET/api/v1/parishes/{slug}Parish dossier + project list

GET/api/v1/operators/{slug}Operator dossier + filings timeline

GET/api/v1/briefsBrief feed · paginated

GET/api/v1/sources/{id}Single source record

GET/api/v1/permitsPermit and regulatory events · explicit not-in-public-record states

GET/api/v1/water-environmentalWater and environmental posture by project

GET/api/v1/evidenceSource-linked evidence records with confidence grades

GET/api/v1/timelineSource-governed tracker chronology events

GET/api/v1/coverageCoverage matrix across diligence surfaces

Full OpenAPI spec: /openapi.json

Versioning, snapshots, diffs, GeoJSON, and webhooks

Pin a version. Diff two dates. Register a webhook.

Every dataset carries a contract version and a data-as-of date. The infrastructure registry also ships dated, field-level snapshots, a diff endpoint between any two captures, a GeoJSON distribution (records without a published coordinate pair are listed as unlocated, never guessed), a data-status report in the shared freshness vocabulary. Webhook registration and the HMAC payload format are available; delivery is not active.

# Which versions and snapshots exist?

$ curl https://louisianai.com/api/datasets/versions

# GeoJSON for maps (4 located records today)

$ curl https://louisianai.com/api/datasets/infrastructure/geojson

# Freshness accounting per dataset

$ curl https://louisianai.com/api/data-status

# What changed between two captures?

$ curl "https://louisianai.com/api/datasets/infrastructure/diff?from=2026-09-23&to=current"

# Register a webhook (delivery not active; secret shown once)

$ curl -X POST https://louisianai.com/api/webhooks \

-H "Content-Type: application/json" \

-d '{"target_url":"https://example.com/hooks","events":["infrastructure.snapshot.published"]}'

# Unsubscribe

$ curl -X DELETE "https://louisianai.com/api/webhooks?id=<id>&secret=<secret>"

GET/api/datasets/versionsVersion manifest: contract version, data-as-of, record counts, snapshot history

GET/api/datasets/infrastructure/geojsonGeoJSON FeatureCollection; unlocated records listed explicitly

GET/api/datasets/infrastructure/diffField-level diff between two snapshots · from=YYYY-MM-DD&to=YYYY-MM-DD|current

GET/api/data-statusRecord counts, min/max lastVerified, review-due and unverified counts per dataset

POST/api/webhooksRegister a webhook · delivery inactive, secret returned once, SHA-256 hash stored

GET/api/webhooksWebhook contract: events, payload shapes, HMAC signature scheme

DEL/api/webhooks?id=&secret=Unsubscribe · constant-time secret check against the stored hash

Webhook payloads are signed with HMAC-SHA256: receivers recompute sha256=HMAC(secret, "<timestamp>.<body>") against the x-louisianai-signature header. Delivery is not active. Subscriptions are stored, but subscribers must re-register before signed delivery can launch because signing secrets are stored only as hashes.