MyCarrier · Rate Limits
Mycarrier Rate Limits
Mycarrier Rate Limits is the rate-limit profile for MyCarrier on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the documented, observed_in_spec, and note response headers.
Tagged areas include Company, Logistics, Transportation, Freight, and Shipping.
0 Limits
documentedobserved_in_specnote
Transcribed from the provider's documentation on 2026-08-26 — developer.mycarrier.io/docs/api-rate-limits.
View Source
Limits
MyCarrier publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
MyCarrier documents that rate limits EXIST and how to react to them, but publishes no numbers. The rate-limits page states that limits are "customized", that "distinct rate limits are applied to different API endpoints", and that they are "enforced on an account-by-account basis" — without naming a single quota, window or burst value. No rate-limit response headers are documented anywhere in the developer docs, and none of the six published OpenAPI contracts declares a 429 response or a RateLimit/X-RateLimit/Retry-After header. An agent therefore cannot read its remaining budget at runtime; it can only observe the 429 and back off. limit_count is 0 because zero numeric limits are published, not because limits are absent.
CompanyLogisticsTransportationFreightShippingLTLSupply ChainTransportation ManagementFreight AuditInvoicing
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.