Vessel Rate Limits
Vessel publishes no numeric rate limits and returns no rate-limit response headers. Every pricing tier advertises "Unlimited API calls", and grepping all 20 published OpenAPI definitions on 2026-08-13 found no X-RateLimit-*, RateLimit-* or Retry-After header declared on any response. The binding constraint is the END CUSTOMER's downstream SaaS quota, which is spent on every uncached read: Vessel forwards unified calls straight through to the connected system. Vessel's own documented remedy is the synced-cache, which it states carries no read rate limits because reads hit a Vessel-hosted database instead of the customer's tenant. Downstream 429s are normalized into the {message, errorCode, metadata} error envelope with the original status and errors under metadata, rather than surfaced as headers.
Vessel Rate Limits is the machine-readable rate-limit profile for Vessel on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring requests, varies, and connections.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled and note.
Tagged areas include Rate Limiting, Unified API, and Integrations.
Limits
Policies
Sources
- https://www.vessel.dev/pricing
- https://github.com/vesselapi/all-api-docs/blob/main/docs/pages/home/synced-cache.mdx
- https://github.com/vesselapi/all-api-docs/blob/main/docs/pages/crm/error-handling.mdx
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.