Skip to content
RVO Documentation

Limits & Quotas

RVO enforces explicit limits and quotas on a per–API key basis.

Limits are not adaptive, hidden, or heuristic-based. Every request is evaluated against clearly defined boundaries so that application behavior remains predictable as traffic grows.

How limits are applied

Section titled “How limits are applied”

Limits and quotas are enforced per API key, not per account or IP address.

Each key operates as an independent workload with its own:

  • Request throughput limits
  • Usage quota
  • Error accounting

This isolation ensures that one application, environment, or service cannot impact another.

Deterministic enforcement

Section titled “Deterministic enforcement”

RVO does not silently slow down or deprioritize requests.

When a limit is reached:

  • Requests are rejected immediately
  • A deterministic error response is returned
  • The reason for rejection is explicit

There is no hidden throttling and no “best effort” traffic handling.

Temporary bursts vs sustained usage

Section titled “Temporary bursts vs sustained usage”

Short-lived traffic spikes may be accepted when system capacity allows.
However, sustained traffic above the defined limits will consistently result in rejected requests.

If your application regularly hits limits, upgrading the plan is the intended scaling path.

Where limits are defined

Section titled “Where limits are defined”

All active limits and quotas are always visible.

You can review them in the dashboard and on the public pricing pages:

There are no undocumented thresholds or unpublished constraints.

Usage accounting

Section titled “Usage accounting”

Usage is tracked in real time and attributed to the API key used for each request.

Metrics include:

  • Accepted requests
  • Rejected requests
  • Method-level usage
  • Error classifications

Usage history retention depends on the selected plan.

Live usage data is available in the dashboard:

👉 https://dashboard.rvo.network/usage

What happens when limits are exceeded

Section titled “What happens when limits are exceeded”

When a request exceeds the allowed limits:

  • The request is rejected
  • No retry is performed by the platform
  • The response indicates the reason for rejection

Rejected requests do not modify or retry themselves automatically.
Retry behavior must be handled explicitly by your application.

Details on error responses and recommended retry strategies are covered in Errors & Retries.

Scaling with RVO

Section titled “Scaling with RVO”

RVO is designed to scale by intentional configuration, not by surprise.

When your workload grows:

  • Increase limits by upgrading your plan
  • Use multiple API keys to separate workloads
  • Monitor usage trends before limits are reached

This ensures scaling remains controlled, observable, and predictable.

What’s next

Section titled “What’s next”

To understand how limit-related failures are reported and how to handle them correctly, continue with:

  • Errors & Retries – error types, responses, and retry strategies