Slice Rate Limits
Slice does not publicly publish request-rate, concurrency, or quota numbers for the Slice Public API. Access is gated to approved technology partners through an issued API key (request via api-support@slicelife.com), and any per-key throttling or quota is established under the partner agreement rather than on the public developer portal. The documented authentication surface is API-key based; consumers should assume per-key limits exist, handle HTTP 401 (unauthorized) and 429 (too many requests) defensively, and confirm exact limits with Slice partner support. The values below are therefore policy placeholders pending partner-agreement confirmation, not published figures.
Slice Rate Limits is the machine-readable rate-limit profile for Slice on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests and concurrent-requests.
Tagged areas include Rate Limiting, Online Ordering, and Partner API.
Limits
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/slice-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.