Petrora

CONNECT

Two ways in. Same data, same citations.

Everything on this site is served by one read-only API. Call it directly from your own code, or let the assistant you already use call it for you through the MCP connector. Either way, every entity comes back with its petrora.com URL.

PATH 1 · API

Call the API

Read-only JSON for scripts, spreadsheets, dashboards, and internal tools. Every call carries an API key from your account; the free trial covers it. Every record carries the URL of its page, and every list carries a total, so nothing is capped. 

curl "https://api.petrora.com/v1/data/operators/tx?days=30&limit=3"
curl "https://api.petrora.com/v1/data/permits/tx?county=reeves&days=all"
curl "https://api.petrora.com/v1/data/wells/42-337-34003"
  1. 1Try it. The requests above are live and need nothing.
  2. 2Open the interactive reference: every endpoint, parameter, and field, with a try-it client. Generated from the API's own schemas, so it is always what the API accepts.
  3. 3Read the written reference for identifiers, windows, and lags. Point an SDK generator or an assistant at the OpenAPI document.
  4. 4Create an account, make a key on the account page, and send it as a bearer token. The trial is bounded by days and calls, then a plan.
Get an API keyInteractive reference ↗How to use it

PATH 2 · YOUR AI

Connect an assistant

Add Petrora as a connector and ask questions in plain language. The assistant calls the same API and links to the page behind every answer. One setup per client, about five minutes.

Status · beta, free trial

The connector is live at https://mcp.petrora.com/mcp. Create an account, add the connector to your assistant, approve it, and ask; your free trial starts at that moment, no credit card required, and nobody has to switch anything on. The guides show the exact steps.

Connect your assistantGetting started: connect

What your AI can ask for

Twenty-eight read-only tools, one per read on the API, in eight groups. Each returns the petrora.com URL of every entity it names. The full list is in the Claude guide.

search_operators · get_operator

Find an operator by name, then the hub: permits by window, wells by status, counties, formations, production, scorecard.

search_permits · get_permit

Permits newest first with every filter the site has, a total for paging, and one permit with its amendments.

get_county · county_operators

A county hub with windows, trend, top operators, new entrants, and formations; the operators permitting there.

get_well · cross_section

A well by API number: permits, completions, chain of custody, production, tops, injection, seismicity; tops for up to eight wells side by side.

search_leases · get_lease

Leases, the unit Texas reports production by, with monthly history to the reported-through month and a decline fit.

search_fields · list_formations · list_basins

Fields, formations with depth by county, and the six basins rolled up from their counties.

disposal_statewide · county_disposal

UIC permits, permitted capacity, and injected volumes statewide and by county, each figure labeled with its reported-through month.

earthquakes_statewide · county_earthquakes · get_earthquake

TexNet events by month and county area, and one event with the injection wells within 10 km.

Not sure where to begin?

The getting-started walkthrough covers the site first, then the connector and the API, one step per page.