Physical infrastructure beta

Physical energy infrastructure data for pipeline constraints and basis risk.

OilPriceAPI is testing a beta data surface for developers, analysts, logistics teams, and AI agents that need more than a spot price. The goal is to expose the physical constraints behind regional volatility: pipeline notices, capacity pressure, LNG feedgas, storage signals, and power-risk context.

Request beta access Review current API docs

This is a crawl-stage validation page. Beta examples are sample data until source coverage, rights, freshness, and endpoint scope are confirmed.

Sample graph context

Permian to Waha watch

beta sample

Upstream node

Permian associated gas

Midstream edge

Capacity notice corridor

Market hub

Waha basis-risk context

Downstream pull

LNG feedgas demand

{
  "beta": true,
  "node": {
    "id": "sample-permian-waha",
    "type": "market_hub",
    "name": "Waha Hub",
    "region": "Permian Basin"
  },
  "signals": [
    {
      "type": "pipeline_constraint",
      "status": "watch",
      "description": "Capacity notice detected on a linked corridor",
      "data_vintage": "sample",
      "source": "beta sample"
    },
    {
      "type": "basis_risk",
      "status": "elevated",
      "description": "Regional bottleneck context requested",
      "confidence": "research"
    }
  ],
  "next_step": "request_beta_access"
}

Crawl-stage workflows

Search intent we are validating first.

Pipeline constraint alerts

Explore whether critical notices, maintenance windows, compressor outages, and capacity constraints can add context to regional price moves.

Basis-risk context

Connect Waha, Permian, LNG feedgas, and storage signals to the physical bottlenecks that can pressure regional basis spreads.

Data-center power risk

Evaluate gas infrastructure, storage, and grid-adjacent constraints that matter to AI campus and industrial power planning.

Agent-ready access

Shape compact JSON for software teams and AI agents that need source, vintage, confidence, and stale-data metadata.

What beta access means

Manual validation before graph infrastructure.

Sample data first

Qualified beta requests may receive static JSON examples or manually prepared datasets while coverage is validated.

Workflow fit before scope

We will ask which workflow matters: pipeline notices, basis spreads, LNG feedgas, storage, data-center power, or agent tooling.

Source and vintage included

Every future response shape should make source, data vintage, confidence, and stale-data state explicit.

Production API later

Persistent graph tables, MCP tools, and production endpoints wait until demand and willingness to pay are proven.

Help shape the first physical infrastructure endpoint.

Request beta access if you can name the first query your team or agent needs to answer. We are prioritizing workflows with clear source requirements and a concrete business use.

Request beta access Try current price API