MyStars FaaS · Rate Limits
Mystars Rate Limits
Mystars Rate Limits is the machine-readable rate-limit profile for MyStars FaaS on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions.
Limit state is signalled in the RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and Retry-After response headers.
Tagged areas include Telegram, telegram-stars, telegram-premium, Payments, and Crypto.
3 Limits
RateLimit-LimitRateLimit-RemainingRateLimit-ResetRetry-After
Transcribed from the provider's documentation on 2026-08-27 — mystars.tg/docs.
View Source
Telegramtelegram-starstelegram-premiumPaymentsCryptoTONfulfilmentBlockchainDigital Goodsreseller-api
Limits
General per-minute request budget per-tenant (API key)
60/1 minute
Default is 60 req/min; the docs say to read the live value from RateLimit-Limit rather than assume it.
Order-lifecycle bucket per-tenant (API key)
60/1 minute
A separate bucket of the same per-minute size as the general budget, isolated from read traffic — a burst of pricing or catalog reads can never throttle an order create, status poll or cancel, and vice versa. On these routes the RateLimit-* headers report this bucket. Added in v1.10.0 (2026-07-10).
Upstream probe cap per-tenant (API key)
60/1 minute
A tighter cap that applies IN ADDITION to the general budget, because each call drives a live upstream price/eligibility lookup. On these routes the headers report this (binding) budget. getPricingBatch counts as ONE unit however many quantities it quotes (up to 200).
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.