API Starter
$30/month
For developers and analysts testing a focused oil and gas data workflow.
- 10,000 API units
- API key management
- Hard stop by default
- Usage dashboard
- OpenAPI reference
API pricing and credits
Oil and Gas API Pricing With Hard-Stop Usage Controls
Start with API-only access for $30/month and 10,000 API units. Usage is metered by endpoint unit cost, shown in the API dashboard, and stopped when the account runs out of included or prepaid units.
Premium App + API
$150/month
For users who need the app workspace plus approved API access for recurring workflows.
- Premium app access
- Maps, tables, exports, and reports
- API access by approved scope
- Usage controls
- Billing portal
Custom API / MCP
Custom
For larger teams, higher-volume integrations, MCP workflows, or custom data delivery.
- Custom unit allowance
- Endpoint and geography scoping
- Commercial use review
- MCP support path
- Custom reporting or delivery cadence
What an API unit means
A unit is the usage meter for API requests. Simple lookups cost fewer units; broader searches or record-heavy endpoints may cost more. The OpenAPI schema marks operation costs, and customer dashboards show request and unit usage.
Operator search
Typical low-unit lookup for matching operator names and ids.
Permit search
Higher-cost request when filters return larger permit result sets.
Well production
Higher-cost request when production rows are returned for a supported well.
Infrastructure signals
Scoped workflow request for facility or infrastructure lead context where available.
Usage controls by default
Hard stop
Requests stop when included units and prepaid credits are exhausted. No surprise overage by default.
Prepaid credits
Customers can add prepaid usage when top-up checkout is available for the account.
Rate limits
Rate-limit headers help integrations back off instead of retrying blindly.
Request traceability
Request ids should be logged with support tickets and failed jobs.
Billing
Card management and receipts are handled through the authenticated billing portal. Marketplace purchases may use the marketplace billing path after activation.
API keys
Keys are created inside the authenticated API screen. Store keys server-side and rotate keys when an integration changes owner.
Commercial scope
Redistribution, customer-facing resale, or larger-volume use should be reviewed before the workflow is approved.