Kno2 Rate Limits
Kno2 does not publish fixed numeric rate limits for the Communication API. As a partner/enterprise, per-subscription API, throughput and any throttling are governed by the subscription agreement rather than a public per-minute cap. Kno2's own reference client consumes inbound messages by polling GET /api/messages on a loop with a 10-second wait between empty polls, which implies clients are expected to poll on a modest cadence rather than hammer the endpoint. All values here are modeled - confirm concrete limits with Kno2 during onboarding.
Kno2 Rate Limits is the machine-readable rate-limit profile for Kno2 on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and source-ip.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Healthcare Interoperability, Direct Secure Messaging, FHIR, Rate Limiting, and Quotas.
Limits
Policies
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/kno2-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.