Skip to content
Developers
Get an API token

Rate limits

Request rates, concurrency, size limits and back-off rules for each Novi product, as published today.

View MarkdownOpen in Claude(opens in a new tab)

Only the EVA REST API publishes a request rate today; the others limit work by size, jobs in flight or warehouse.

Novi UDM Data (v4)
Request rate
Not published yet
Work in flight
Not published yet
Size limits
Not published yet
Rate headers
Not published yet
Novi Forecasts API
Request rate
Not published yet
Work in flight
Async forecasts: 50 per company. Plan economics: 4 per company. Exports: 20 per model set, 3 per plan. Your unfinished plan forecasts: limits.plan_unfinished_forecasts
Size limits
50 drawn wells per POST /forecasts. Bodies: 64 MB on POST /plans, 10 MB on POST /exports
Rate headers
Retry-After only, when a job cap is reached
Novi EVA REST API
Request rate
10 requests per second on average, bursts up to 30
Work in flight
5 requests
Size limits
50,000 wells per POST /v1/data, 1,000 per POST /v1/production
Rate headers
Not published yet
Novi EVA MCP server
Request rate
Not published yet
Work in flight
A few data tool calls at a time per person; more wait briefly
Size limits
Request body 1 MiB. Data tool result 64 KiB. Chart result 256 KiB. 30-second deadline per data tool call
Rate headers
Not published yet
Novi M&A Intelligence MCP server
Request rate
ma_search_deals is rate limited per person; the value is not published yet
Work in flight
Not published yet
Size limits
100 rows per page; 50 deals in your basket
Rate headers
Not published yet

Your queries run on a Snowflake warehouse, so compute, not a request count, sets the pace.

  • In a reader account, the first query after about a minute idle takes 10 to 30 seconds to start. The same SQL run again within 24 hours returns at once.
  • On your own Snowflake account, your warehouse runs the queries and you pay for it.
  • On a BI or lakehouse connection, statements stop after 2 hours.

GET /dataset limits and GET /export-formats limits report most limits: read them rather than hard-coding values. Every limit and how to back off: Errors and limits.

  • REST: stay under 10 requests per second and 5 in flight. Batch wells into one call instead of many small ones.
  • MCP: LIMIT_EXCEEDED and DEADLINE_EXCEEDED are retryable. Wait, then retry, or narrow the request.
Item Status
RateLimit and RateLimit-Policy headers, so a client can pace itself Planned
Published request rates and concurrency for Novi UDM Data over HTTPS Planned