Version 0.1.3 · Registry installation commands use exact versions.
Fragment API automation for Stars and Premium
Automate recipient validation, TON/USDT balance checks, and one-at-a-time Stars or Premium gifts from a server backend.
Purchase requests transmit your wallet mnemonic and Fragment session/cookie to the API operator.
A safe automation pipeline separates read operations from spending operations. Username lookup and wallet balance may use bounded opt-in retries; Stars and Premium purchases never retry automatically.
Keep one durable internal record for each intended purchase: recipient, product, amount or duration, payment method, creation time, and final or uncertain state. Do not store the mnemonic, Fragment cookie, provider key, or proxy password in that record.
Use a worker with a strict one-purchase-at-a-time policy per intent. If the response is unconfirmed, the connection times out, or the response cannot be parsed, stop that intent and require reconciliation instead of placing a second order.
The service has a shared per-IP minute quota across all four endpoints. Schedule read traffic, honor the longest valid Retry-After hint, and do not let a batch job turn a rate-limit response into duplicate spending.
Example
lookup recipient -> check balance -> create intent -> submit once
|
success <----------+----------> uncertain -> reconcileContinue reading
Telegram Stars API: send Stars to a username · Handle Telegram Stars API 429, Retry-After, and flood wait · Payment timeout: prevent duplicate Telegram Stars purchases