Ximilar · Rate Limits

Ximilar Rate Limits

Published limits for the Ximilar API. This file REPLACES a 2026-05-04 scaffold that asserted per-minute request ceilings and X-RateLimit-* response headers Ximilar has never documented. The honest picture: Ximilar throttles by CREDIT QUOTA and by resource count, not by requests per second, and it publishes NO rate-limit response headers and NO 429 contract. On the synchronous surface a caller has no runtime backoff signal at all; on the asynchronous surface throttling surfaces as a request STATE (RETRY, API_LIMIT_EXCEEDED) rather than an HTTP status.

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

It captures 9 rate-limit definitions, across the free, business, professional, and all tiers, measuring api_credits_per_month, records_per_request, records_per_collection, collections, and results_per_page.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and note.

Tagged areas include Rate Limiting, Quotas, and Credits.

9 Limits
Rate LimitingQuotasCredits

Limits

Free monthly credit allowance account
api_credits_per_month · month
1000
Business monthly credit allowance account
api_credits_per_month · month
500000
Professional monthly credit allowance account
api_credits_per_month · month
40000000
Batch size per request request
records_per_request · request
10
Visual search collection size collection
records_per_collection
1000
Visual search collection size collection
records_per_collection
500000
Visual search collection size collection
records_per_collection
-1
Number of collections account
collections
10
VLM request history page size request
results_per_page
100

Policies

Credit exhaustion
Once the monthly credit allowance is spent, calls that consume credits fail. Additional credit packs can be purchased on Business and Professional plans. Only calls that send or upload an image for AI analysis consume credits.
Automatic retry on the async surface
Asynchronous requests that hit a transient failure — explicitly including a rate limit — are moved to the RETRY state and retried by Ximilar automatically, with no client action required.
Storage capacity
Inserts into a collection that exceed the plan's collection size are refused with status 412 "hard capacity exceeded".

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/ximilar-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.