PREVIEW · Proposed endpoints and dated plan snapshot · Not ready for public launch
navquote.
Menu
Plans & access

Start small.
Build from there.

Match your app’s interfaces and request volume to a plan. Use the same account for keys, usage and billing.

PREVIEWSnapshot dated . Current prices and access are unverified. The free-plan allowance differs across local sources; confirm the published plan in Console.
MONTHLY SNAPSHOT · USDCheckout in the shared console
PLAN / BASIC

Basic

Explore the API

$0/ month

Snapshot price · verify before launch

200requests / month2 requests / second
  • Batch quotesIncluded
  • StreamingIncluded
  • MCPIncluded
View Basic in console
PLAN / PRO

Pro

REST-focused access

$10/ month

Snapshot price · verify before launch

40,000requests / month5 requests / second
  • Batch quotesNot included
  • StreamingNot included
  • MCPNot included
View Pro in console
PLAN / MEGA

Mega

A larger data workload

$80/ month

Snapshot price · verify before launch

1,000,000requests / month5 requests / second
  • Batch quotesIncluded
  • StreamingIncluded
  • MCPIncluded
View Mega in console
Choose by what you are building

Find your path.

Match the required features first. Then compare request budgets in Console.

Dated plan snapshot. Basic also includes limited evaluation access; confirm current features and terms before subscribing.

Size your own workload

Make the workload
visible.

Adjust the schedule to your app. Count HTTP calls, not the number of people viewing your interface.

What else should I count?

Add first-page loads, chart requests, search, retries and background jobs. Decide whether your server shares results across users or makes separate calls.

How do billing units differ?

A batch, a token mint and a tool call need not consume the same unit. Stream messages are not credential mints. Confirm accounting and measure actual usage in Console before choosing a budget.

Estimate your polling workload
Estimated monthly HTTP requests10,560 1 × (3,600 ÷ 60) × 8 × 22

Assumes evenly spaced refreshes. Count all independent polling jobs; shared server results need not be fetched once per user. Excludes retries and other API calls.

This estimates request volume, not a bill or plan recommendation. Batch accounting, stream tokens and MCP usage are separate checks.

01 / The details, side by side

Choose by workload.

Token mint allowances count issued credentials, not messages or connected symbols.

Snapshot entitlementBasicProUltraMega
Monthly REST request budget20040,000160,0001,000,000
Requests per second2555
Batch quotesIncludedNot includedIncludedIncluded
Stream token lifetime30 minNot included6 hrs1 days
Stream token mint allowance50 / moNot included1,000 / mo200,000 / mo
MCP token lifetime30 minNot included15 days30 days
MCP monthly allowance*50 / moNot included1,000 / mo200,000 / mo

* The exact unit of the MCP monthly allowance needs verification. Batch accounting, connection limits and renewal periods must be confirmed separately.

Know what you are counting

Three budgets to keep separate.

A monthly total alone does not describe the workload.

01 / REQUESTS

Monthly volume

Count polling, chart loads, searches and retries. A batch can contain multiple symbols; confirm how the active plan charges it.

See a batch request
02 / BURSTS

Requests per second

Spread simultaneous jobs across time. Two apps with equal monthly usage can create very different peak loads.

Handle rate limits
03 / CONNECTIONS & TOOLS

Tokens and sessions

Generating a credential is different from receiving an update or calling a tool. Check lifetimes, connection limits and usage units.

Credential workflows
From evaluation to subscription

Check the fit before you commit.

Use a representative workload to choose with confidence.

  1. Validate the data

    Check your symbols, timestamps, candle intervals and missing fields with a small request.

    Start with one quote
  2. Confirm the access

    Check your assets, markets and required datasets, then confirm endpoint and transport access on the current plan.

    Compare asset & data coverage
  3. Review the current offer

    Confirm price, billing period, allowance, overages and change or cancellation timing before checkout.

    Open current plans
Before you choose

Billing, without guesswork.

How should I evaluate the API before subscribing?

Choose a few required symbols and one representative historical window. Run the quickstart, check timestamps and missing fields, then test the batch, stream or MCP interface your app needs. Basic is an evaluation option in this snapshot; confirm its current allowance in Console.

What happens when I reach a limit?

Monthly allowance, request rate and interface access are different limits. A larger monthly budget does not necessarily raise the per-second limit. For a 429 response, inspect the error body and honor Retry-After when supplied. Check the active plan’s hard limits and any overage charges in Console; do not assume extra usage is automatically allowed.

Can I change or cancel a subscription?

Manage the subscription in Console. Before confirming a change, review its effective date, any prorated charge and the resulting access. Cancellation timing and downgrade options depend on the active subscription. This preview does not establish refund terms.

When is it worth moving beyond a small evaluation?

After you have validated the required data and know which features your application needs. Compare subscriptions when repeated use needs more allowance or a specific transport. Confirm current terms in Console rather than treating the preview as a checkout offer.

Do I need a separate account for NavQuote?

No. Use the shared account console for keys, usage and subscriptions. Existing users do not need to create a second account.

Does every paid plan include streaming?

No. In this snapshot Pro does not include streaming or MCP. Check the current console before choosing a plan.

Are these current prices?

They are not yet verified. This preview uses a dated repository snapshot. Prices, access and quota accounting must be confirmed before public launch.

Do token limits count market updates?

A streaming token mint allowance counts generated credentials. It is not a message allowance or a concurrent connection limit. MCP allowance units still require confirmation.

One account. Your next build.

Review current plans and manage your API access in the console.

Get API Key

Continue to our shared account console.