Plans & limits

MCP and REST share a single daily request limit per account. This page covers what each plan allows and what counts against it. For REST status codes, rate-limit headers and retries, see Errors & retries.

Daily limits

One counter covers both MCP tool calls and the REST API. It resets at 00:00 UTC. Requests made with an organization API key count against the counter of the member who created it, or the owner's once that member leaves.

REST responses with HTTP 400–599 do not consume the daily allowance, including invalid parameters, missing data and server errors. A successful REST request counts once, including each page of a paged read. Requests already in progress temporarily reserve capacity; their allowance is restored if they fail.

Every plan, Free included, gets API access to both the MCP server and the REST API. The plans differ in how many requests a day they allow:

Pricing always shows the current allowances — it reads them from the live plan, so trust it over this table if the two ever disagree.

Need more? Compare plans.

Two MCP feedback tools are free and never counted: ReportProblem, for a failed or non-credible call, and SuggestToolImprovement, for a concrete improvement to an existing tool the agent actually called. Reporting our defect or limitation should not cost you a request. See Tools overview for what they send.

Parallel MCP calls

Each API key, or each account connected through OAuth sign-in, runs at most 4 MCP tool calls at once. Extra calls wait up to 20 seconds for a free slot, so a burst of parallel calls just finishes a little later. Up to 64 calls per key can wait at once. A call that finds no slot in time, or arrives while 64 are already waiting, gets a tool result starting "Too many parallel Equibles requests". It does not count against your daily limit, and you can retry it once earlier calls finish. A call that carries no JSON-RPC id gets a 429 with Retry-After: 5 instead.

Data that needs a paid plan

Most tools and endpoints work on every plan, Free included. A few need a paid plan, and each reference page notes its plan requirement. For example:

• Intraday stock quotes, live quotes and option chains.
• Index-forecast candidates.
• Trackers, which need a plan that includes them.

Over MCP, the tool answers in the conversation with a note explaining what your plan is missing. Over REST, quotes, option chains and trackers return 403 (see Errors & retries), while index-forecast candidates come back locked, with candidatesLocked: true and empty rows.

Pricing lists everything else each plan adds, such as multi-condition screens and organizations.

Requests without a key

The MCP server answers a keyless request only when it is the handshake or a pure-metadata read (initialize, tools/list, …), so a client can list the tool catalogue before signing in. Anything that would actually run a tool returns 401 — attach a key or complete the OAuth sign-in.

That open path carries its own per-IP cap of 60 requests per minute, separate from the daily limits above. Over it you get a 429 with a Retry-After: 60 header and a message pointing at your API keys. Keyless requests resolve no account, so they never touch your daily counter — but they also never get past metadata, so add a key rather than leaning on this path.

The REST API has no keyless path at all: every request needs a key, and one without it is a 401.

When you hit the limit

Over the limit, the MCP server returns a normal tool result whose text explains the limit and links to upgrade, so your agent can relay it in the conversation rather than surfacing an opaque transport error. The message starts "Daily call limit exceeded" and names the reset time. The REST API returns 429 Too Many Requests with its error envelope. Either way, the counter resets at 00:00 UTC.

Still stuck?

If a request keeps failing or a number looks wrong, email [email protected] or open a ticket. Include the request or prompt (with any key removed) and the response you got.