Velt Rate Limits
Velt governs usage primarily through plan-based capacity rather than a published per-endpoint request-per-second limit. The main capacity dimensions are Monthly Active Documents (MADs) and simultaneous real-time connections, both set by tier (20 connections on Hacker, up to 100,000 on Growth, up to 200,000 on Enterprise). Data (REST) API calls that accept batches cap list inputs - for example notification config requests accept up to 30 document IDs per call. Webhook deliveries are subject to retry scheduling with exponential backoff and provider-side rate limiting on the delivery path. Specific per-endpoint request-rate values are not reconciled in this artifact.
Velt Rate Limits is the machine-readable rate-limit profile for Velt on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring documents, connections, and deliveries.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Real-Time Collaboration, Comments, Presence, Notifications, and SDK.
Limits
Policies
Sources
- https://velt.dev/docs/api-reference/rest-apis
- https://velt.dev/docs/webhooks/advanced
- https://velt.dev/pricing
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/velt-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.