Paragon · Rate Limits

Useparagon Rate Limits

Paragon does not publish a single, transparent public rate-limit table. Because Paragon is an embedded integration platform, effective throughput is bounded by two layers: (1) Paragon's own per-project limits on Connect API, ActionKit, and Managed Sync calls, which vary by plan and are raised for Enterprise agreements; and (2) the rate limits of the underlying third-party APIs being proxied or synced (e.g. Salesforce, Slack, HubSpot), which Paragon surfaces back to callers. Managed Sync additionally manages its own ingestion concurrency, backfill pacing, and automatic retry/backoff on behalf of the application.

Useparagon Rate Limits is the machine-readable rate-limit profile for Paragon on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests and records.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Integration, iPaaS, Embedded Integrations, ActionKit, and Managed Sync.

4 Limits Throttle: 429
IntegrationiPaaSEmbedded IntegrationsActionKitManaged SyncRate LimitingQuotasThrottling

Limits

Connect API Requests project
requests
see provider documentation
Per-project limits on zeus.useparagon.com SDK endpoints; varies by plan.
ActionKit Run Requests project
requests
see provider documentation
Rate on POST /projects/{id}/actions/run; downstream provider limits also apply.
Proxy API Requests user
requests
bounded by third-party provider
Proxied calls are subject to the connected third-party API's own rate limits.
Managed Sync Ingestion project
records
managed by Paragon
Backfill pacing, incremental sync concurrency, and retry/backoff are handled by Paragon.

Policies

Tiered Limits
Per-project limits are raised as accounts move from Startup to Growth to Enterprise agreements.
Downstream Passthrough
Proxy and ActionKit requests inherit and surface the underlying third-party API rate limits.
Managed Backoff
Managed Sync automatically retries with backoff and recovers from third-party failures during backfill and incremental syncs.
Client Backoff
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources

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.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/useparagon-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.