Uplead Rate Limits
API rate limits and throttling for the UpLead v2 API, read verbatim from the published Rate Limit section of the documentation. UpLead publishes one limit — 500 requests per minute per API key — and returns the full legacy X-RateLimit-* header trio plus Retry-After on the 429, so the runtime signal an agent needs is available on every response, not just at exhaustion. Note that the request-rate limit is NOT the binding constraint on this API: credit consumption is, and that is recorded in plans/uplead-plans-pricing.yml and finops/uplead-finops.yml.
Uplead Rate Limits is the machine-readable rate-limit profile for UpLead on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 1 rate-limit definition.
Tagged areas include B2B, Lead Generation, Contact Data, Company Data, and Email Verification.
Limits
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/uplead-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.