Pulse Verity

Usage and access

A request limit tells you when to pause. The error message identifies which limit applies.

Temporary request limit

RATE_LIMITED

Pause requests. If the error includes a retry delay, wait that long before trying again. Reduce repeated or concurrent requests.

Monthly allowance reached

MONTHLY_LIMIT

Wait until the start of the next UTC month for the monthly allowance to reset. Usage is shared across the account’s API keys and hosted connections. Creating another key does not reset it.

This guide does not show your account’s current usage or reset time. If an error does not identify a monthly limit, do not assume the monthly allowance is exhausted.

How access works

Public npm samples

The public pulse-verity npm package can read BTC, ETH and SOL samples without an API key. An optional API key connects a local MCP client to the developer account’s access.

Hosted connectors

The hosted MCP service requires a developer account. When your client opens the connection flow, sign in and approve access. Hosted requests use the connected account’s allowance.

Installing a package or connecting another client does not create a separate account allowance.

What account access includes

Account access supports current index prices, catalogue pages, batch reads and recorded settlement prints, subject to account permissions, usage limits and available data.

The MCP tools are read-only. A recorded settlement print is a historical price record. It does not initiate a transaction.

Access does not guarantee a current price for every asset or a recorded print at every requested time. Use the returned status and timestamp to check availability.