Intelerad · Rate Limits

Intelerad Rate Limits

Intelerad does not publish fixed numeric rate limits for the InteleShare / Ambra v3 Services or Storage APIs in the public reference. Access is gated by session (sid), Basic, or OAuth authentication and by per-account, per-role, and per-namespace permissions rather than by a documented public per-minute request cap. Practical throughput is bounded by account entitlement and by the study / image volume of the contracted deployment. The v3 API signals errors with a status of "ERROR" plus HTTP codes such as 401 (authorization), 405 (invalid method), and 412 (precondition failed).

Intelerad Rate Limits is the machine-readable rate-limit profile for Intelerad on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests and bytes.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 2 backoff/retry policies defined and response codes documented for unauthorized, invalidMethod, and preconditionFailed.

Tagged areas include Medical Imaging, PACS, Image Exchange, Rate Limiting, and Quotas.

3 Limits
Method: generated, dated 2026-07-05.
Written by API Evangelist on 2026-07-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Medical ImagingPACSImage ExchangeRate LimitingQuotas

Limits

v3 Services API Requests account
requests
not published
No fixed numeric request-rate limit is documented; access governed by auth, roles, and namespace permissions.
Storage API Throughput account
bytes
not published
Image upload / retrieve throughput bounded by account entitlement and deployment scope.
DICOMweb Access account
requests
not published
WADO-RS / QIDO-RS / STOW-RS access governed by the same authentication and permission model.

Policies

Permission-Scoped Access
Access is controlled by a role/permission matrix (Admin, User, PHR, Anonymous) and by namespace scoping rather than a global public rate limit.
Backoff Strategy
Clients should implement exponential backoff with jitter and handle 401 / 405 / 412 responses and ERROR status payloads gracefully.

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/intelerad-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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