Skip to content
Developers
Get an API token

Roadmap

Everything planned for the Novi developer platform, by product, with the reason each item belongs.

View MarkdownOpen in Claude(opens in a new tab)

Nothing on this page is available yet.

Item What it gives you Status
Canadian wells in Novi UDM Data, keyed on UWI-DLS North American coverage in one data model. Canada is on v3 today Planned
US wellbores keyed on API14 Per-lateral joins with operators’ own data Planned
A v3 to v4 field mapping guide A column-by-column path from v3 Planned
A “data as of” time and refresh cadence for every view Know how fresh each table is Planned
Published request rates and concurrency for Novi UDM Data over HTTPS Published limits to plan against Planned
GIS delivery as standard map layers (OGC or Esri) GIS layers in your mapping tools Planned
OpenSharing (formerly Delta Sharing) for recipients outside Snowflake The same share for Databricks, pandas, Spark and Power BI users Planned
An MCP server beside the Snowflake share Agents query Novi UDM Data inside your own Snowflake account Planned
Item What it gives you Status
Python and TypeScript SDKs Typed clients in Python and TypeScript Planned
Read-only service tokens not tied to a person Least privilege for partners, pipelines and agents Planned
Callbacks to your own receiver when a plan or an export finishes Push instead of polling Planned
Deletion records for sync Partner tools catch removals without a periodic full list Planned
Arps segments as JSON Partner tools that import decline parameters, not volumes Planned
RateLimit and RateLimit-Policy headers Clients pace themselves Planned
Arazzo workflow files for common jobs: find wells, run a forecast, export Agents and code generators follow the documented sequence Planned
Item What it gives you Status
The EVA MCP server on company hosts Ask EVA questions from an assistant on your company host Planned
Item What it gives you Status
One export job method for every product: send a filter or an area, get a short-lived download link, with MCP as another caller Large extracts without SQL, for agents and people who do not write SQL Planned
Assistant sign-in for clients beyond Claude, Claude Code and Codex, including your own agents Any MCP client, including your own agent, can connect Planned
One error format, RFC 9457 problem details One error parser for every Novi API Planned
Deprecation and Sunset headers on deprecated versions and endpoints Clients learn of retirements from the response itself Planned
One sign-in and API token for every Novi API, including Novi UDM Data and the EVA REST API One credential to manage across products Planned
Shared conventions for P-levels, units, BOE and first-12-month measures across products The same number means the same thing in every product. See P-levels and Units and conventions Planned
Forecasts data in the v4 data model Forecasts in the same schema as Novi UDM Data Planned
Alerts when new permits, spuds and completions land in an area you watch Watch an area without polling Planned
A status page Live service status in one place Planned
A sandbox with synthetic sample wells and a test token Try the APIs before you sign Planned
A try-it console against the sandbox Run a call from the docs page Planned
An API catalog at /.well-known/api-catalog (RFC 9727) Agents and tools discover every Novi API and spec in one request Planned
An MCP server card for each Novi MCP server Clients read a server’s address and protocol versions before they connect Planned
An agent plugin that bundles the MCP servers and the Claude skill One install for every Novi tool Planned
A docs MCP server for this site Agents search these docs directly Planned

Dates are not published. To ask about an item, email support@novilabs.com.