The lowest-cost production API for Telegram Stars and Premium: KYC 0%, no-KYC 0.25%, backend-only wallet signing, and reliable queue status.
KYC 0% · NO-KYC 0.25% · Lowest-cost Fragment API
Production API Endpoint
https://api-fragment.duckdns.orgHTTPS · port 443{
"username": "@client",
"amount": 50,
"kyc_commission": "0%"
}Never expose seed or Fragment cookies in frontend code. Do not retry blindly after a transaction may have been signed or sent.
Use the open-source Telegram bot/shop example to sell Stars and Premium through this API.
/api/v1/stars/buy/api/v1/premium/buy/api/v1/commission/ratesKYC is always free. No-KYC costs only 0.25%. Both public rates can be verified before every purchase.
Verify 0% / 0.25% anytime via GET /api/v1/commission/rates
Fragment Stars API connects your backend, Telegram bot, marketplace, or reseller panel to the Telegram Stars and Premium purchase flow on Fragment.com. Use direct REST requests or the maintained Python SDK, check live prices before checkout, submit an order, and poll its queue status until the result is final. No issued API token is required: wallet signing and Fragment credentials stay in your own backend environment.
KYC mode is designed for operators who already have valid Fragment cookies. Your backend supplies its wallet seed and Fragment session for the purchase, while the API handles recipient lookup, pricing, transaction preparation, queue processing, and final status. The API commission is permanently 0%, so you pay only the current Fragment price and blockchain costs.
No-KYC mode uses the service Fragment session and adds only 0.25% API commission. TON is the default payment method for backward compatibility; USDT-on-TON is available where supported. Read live commission rates immediately before creating an order instead of hard-coding pricing in your shop.
Stars purchases return a request identifier for status polling. Treat completed and failed states as final, preserve your own idempotency key, and never resubmit blindly after signing or broadcasting may have happened. Actionable error messages distinguish invalid usernames, insufficient wallet balance, temporary Fragment connectivity, and transaction relay failures.
Give Codex, Claude, Cursor, or another coding agent the prepared context before it writes code. It prevents invented API tokens, frontend seed leaks, and duplicate-purchase retry logic.
Small entrypoint with the canonical endpoint, links, and hard rules.
Detailed REST examples, SDK notes, queue behavior, and failure handling.
Drop this into a Codex project or reference it from AGENTS.md.
Copy this into CLAUDE.md or ask Claude to read it before coding.