API Starter Credits
$50
For developers and analysts testing a focused oil and gas data workflow with prepaid API units.
- 10,000 prepaid API units
- API key management
- Hard stop by default
- Usage dashboard
- API reference
API pricing and credits
Oil and Gas API Pricing With Prepaid Units and Hard Stops
Start with 10,000 prepaid API units for $50. Usage is metered by endpoint unit cost, shown in the API dashboard, and stopped when the account runs out of included or prepaid units. API-only credits do not require the $150/month Premium app subscription. Standard MCP calls use the same API-key scopes and unit balance; your AI provider may charge separately.
How to buy oil and gas API credits
- 1. Create an account or sign in, then open Settings → API Access. You do not need to buy Premium first.
- 2. Select a credit pack, review the terms, and complete checkout. Account creation itself does not include paid API data.
- 3. Once payment is processed and access is active, create an API key and save it privately. Existing users can keep using an active key.
- 4. Run the zero-unit health check, then a small data request. Check scopes, source dates, pagination, and unit costs before scaling.
Already registered? Sign in to API Access. See the county drilling permit CSV/JSON export example or the MCP setup guide before choosing a pack.
Prepaid API credits
Choose a unit pack, then add more when needed
API-only access is prepaid. Credits are metered by endpoint unit cost, shown in the API dashboard, and hard-stopped by default.
API Growth Credits
$200
For recurring jobs, dashboards, and CRM enrichment where one starter pack is not enough.
- 50,000 prepaid API units
- Lower unit price than starter
- Hard stop by default
- Usage dashboard
- API reference
API Volume Credits
$350
For higher-volume API testing, larger enrichment runs, and repeatable internal workflows.
- 100,000 prepaid API units
- Best public unit-pack price
- Hard stop by default
- Usage dashboard
- API reference
Premium App + API
$150/month
For users who need the app workspace plus included API access for recurring workflows.
- Premium app access
- Maps, tables, exports, and reports
- Included API access
- Usage controls
- Billing portal
Custom API / MCP
Custom
For larger teams, higher-volume integrations, custom MCP support, or custom data delivery. Standard MCP setup uses the same API credits.
- Custom unit allowance
- Endpoint and geography planning
- 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. At the starter-pack rate, 120 units is approximately $0.60.
Operator search
Typical low-unit lookup for matching operator names and ids.
Permit search
6 units per request, including each additional page. The documented two-page county export used 12 units; returned row count does not set the per-request price.
Well production
6 units per request for supported modeled well history. Official Texas lease production is a separate 48-unit endpoint; do not treat modeled well values as official lease filings.
Texas regulatory well workflow
A complete search, standard well detail, regulatory identity, completion, and official lease-production workflow totals 120 units when every call is needed. Lease production can be reused across wells on the same lease.
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
Contact EnergyNetWatch before using API data in a public-facing product, resale workflow, or larger-volume data delivery.
Billing FAQ
Cancellation, refunds, and prepaid credits.
How does Premium billing and cancellation work?
Premium is month to month. Cancel anytime. Access runs to the end of the paid month. No prorated refund.
Are unused prepaid API units refundable?
Prepaid API credits are not cash. Unused units are not refunded once the pack is issued.
When is a payment refunded?
Refund a Stripe duplicate, or a pack that never activated (no key, 0 units).
Do prepaid API credits expire?
Credits do not expire in year one. Contact info@energynetwatch.com for billing.
Read the EnergyNetWatch Terms.