Enverus website screenshot

Enverus

Enverus is an energy-dedicated SaaS company providing analytics, market intelligence, and workflow automation across the global energy value chain — oil and gas, power and renewables, minerals, midstream, trading and risk, and financial services. Its developer surface is the Enverus DirectAccess API (formerly Drillinginfo DirectAccess), a token-authenticated REST API that delivers bulk access to Enverus' energy datasets — well origins, rigs, permits, producing entities, production, and related upstream data — with server-side filter functions, field selection, and cursor-based pagination. Enverus serves 8,000+ companies and 35,000+ energy customers from its Austin, Texas headquarters.

Enverus publishes 1 API on the APIs.io network. Tagged areas include Company, Energy, Oil and Gas, Energy Data, and Analytics.

Enverus’ developer surface includes documentation, getting-started guide, engineering blog, support, authentication, and 13 more developer resources.

23.0/100 emerging ▬ flat Agent 3/100 human only saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessSelf serve
1 APIs
CompanyEnergyOil and GasEnergy DataAnalyticsMarket IntelligenceWell DataSoftware-as-a-ServiceDirect AccessTrading and Risk

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/enverus: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Enverus DirectAccess API

Token-authenticated REST API (v2) for bulk programmatic access to Enverus' energy datasets — well origins, rigs, permits, producing entities, and production. Authenticate with a...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Enverus Authentication

apiKey/oauth2 · 3 schemes

SECURITY

Enverus Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: enverus
name: Enverus
description: Enverus is an energy-dedicated SaaS company providing analytics, market intelligence, and workflow automation
  across the global energy value chain — oil and gas, power and renewables, minerals, midstream, trading and risk, and financial
  services. Its developer surface is the Enverus DirectAccess API (formerly Drillinginfo DirectAccess), a token-authenticated
  REST API that delivers bulk access to Enverus' energy datasets — well origins, rigs, permits, producing entities, production,
  and related upstream data — with server-side filter functions, field selection, and cursor-based pagination. Enverus serves
  8,000+ companies and 35,000+ energy customers from its Austin, Texas headquarters.
url: https://raw.githubusercontent.com/api-evangelist/enverus/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- insight-partners
x-tier: enriched
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
image: https://www.enverus.com/wp-content/uploads/2024/08/enverus-og-logo-1553x1553-1.png
tags:
- Company
- Energy
- Oil and Gas
- Energy Data
- Analytics
- Market Intelligence
- Well Data
- Software-as-a-Service
- Direct Access
- Trading and Risk
tags_raw:
- Company
- Energy
- Oil and Gas
- Energy Data
- Analytics
- Market Intelligence
- Well Data
- SaaS
- DirectAccess
- Trading and Risk
apis:
- name: Enverus DirectAccess API
  description: Token-authenticated REST API (v2) for bulk programmatic access to Enverus' energy datasets — well origins,
    rigs, permits, producing entities, and production. Authenticate with an API key plus client credentials to obtain a bearer
    access token, then query datasets with server-side filter functions (gt/lt/btw/null), field selection, and pagination.
  humanURL: https://app.enverus.com/direct/#/api/explorer/v2/gettingStarted
  baseURL: https://di-api.drillinginfo.com/v2/direct-access
  tags:
  - Energy Data
  - Well Data
  - Oil and Gas
  - Direct Access
  tags_raw:
  - Energy Data
  - Well Data
  - Oil and Gas
  - DirectAccess
  properties:
  - type: Authentication
    url: authentication/enverus-authentication.yml
  - type: Conventions
    url: conventions/enverus-conventions.yml
  - type: Lifecycle
    url: lifecycle/enverus-lifecycle.yml
  - type: Conformance
    url: conformance/enverus-conformance.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/enverus-domain-security.yml
- type: Website
  url: https://www.enverus.com/
- type: DeveloperPortal
  url: https://app.enverus.com/direct/
- type: Documentation
  url: https://app.enverus.com/direct/#/api/explorer/v2/gettingStarted
- type: GettingStarted
  url: https://app.enverus.com/direct/#/api/explorer/v2/gettingStarted
- type: Login
  url: https://login.auth.enverus.com/
- type: Blog
  url: https://www.enverus.com/blog/
- type: Support
  url: https://www.enverus.com/contact-us/
- type: TermsOfService
  url: https://www.enverus.com/terms-conditions/
- type: PrivacyPolicy
  url: https://www.enverus.com/privacy-policy/
- type: GitHubOrganization
  url: https://github.com/enverus
- type: LLMsTxt
  url: llms/enverus-llms.txt
- type: Packages
  url: packages/enverus-packages.yml
- type: Authentication
  url: authentication/enverus-authentication.yml
- type: Conventions
  url: conventions/enverus-conventions.yml
- type: Lifecycle
  url: lifecycle/enverus-lifecycle.yml
- type: Conformance
  url: conformance/enverus-conformance.yml
- type: WellKnown
  url: well-known/enverus-well-known.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/enverus"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/enverus/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/enverus/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.