ComboCurve
ComboCurve is an oil & gas well forecasting, type-curve, reserves and economics platform used by petroleum engineers, operators, private equity firms, investment banks, and mineral/royalty companies for acquisition-and-divestiture (A&D), upstream asset management, and reserves analysis. Its public REST API at https://api.combocurve.com exposes well headers, daily and monthly production data, directional surveys, forecasts, forecast configurations, econ-models (capex, expenses, differentials, escalations, depreciation, ownership reversions), economics runs, and asynchronous export jobs. Backed by Bessemer Venture Partners.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles ComboCurve the way a machine reads it — 21 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ComboCurve scores 47.8/100 (developing), with a separate agent-readiness read of 62/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile ComboCurve
Each block below is one kind of artifact we hold for ComboCurve. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
ComboCurve v1 custom-columns API
custom-columns operations
ComboCurve v1 daily-productions API
daily-productions operations
ComboCurve v1 directional-surveys API
directional-surveys operations
ComboCurve v1 econ-models API
econ-models operations
ComboCurve v1 econ-runs API
econ-runs operations
ComboCurve v1 exports API
exports operations
ComboCurve v1 forecast-configurations API
forecast-configurations operations
ComboCurve v1 forecast-daily-volumes API
forecast-daily-volumes operations
ComboCurve v1 forecast-monthly-volumes API
forecast-monthly-volumes operations
ComboCurve v1 monthly-productions API
monthly-productions operations
ComboCurve v1 ownership-qualifiers API
ownership-qualifiers operations
ComboCurve v1 projects API
projects operations
ComboCurve v1 tags API
tags operations
ComboCurve v1 users API
users operations
ComboCurve v1 well-comments API
well-comments operations
ComboCurve v1 wells API
wells operations
ComboCurve v1 wells-identifiers API
wells-identifiers operations
ComboCurve v2 exports API
exports operations
Scroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
combocurve-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for ComboCurve — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
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 3
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
← All providers · Data indexed from github.com/api-evangelist/combocurve · machine-readable index on apis.io