MyStars FaaS — Fulfilment API
A B2B Fragment-as-a-Service (FaaS) fulfilment REST API for programmatically buying and reselling Telegram Stars and Telegram Premium, delivered to any Telegram @username, paid on-chain in TON (GRAM) or USDT (TON). Non-custodial, no KYC. Offers versioned /v1 endpoints for pricing, recipient checks, product catalog, and order lifecycle, with signed webhooks and official TypeScript and Python SDKs.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles MyStars FaaS — Fulfilment API the way a machine reads it — 1 machine-readable artifact across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — MyStars FaaS — Fulfilment API scores 15.2/100 (emerging), with a separate agent-readiness read of 17/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile MyStars FaaS — Fulfilment API
Each block below is one kind of artifact we hold for MyStars FaaS — Fulfilment API. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
MyStars FaaS Fulfilment API
REST/HTTP API for pricing, recipient eligibility checks, product catalog, and Telegram Stars/Premium order lifecycle, with X-Api-Key auth and signed webhooks. OpenAPI contract a...
← All providers · Data indexed from github.com/api-evangelist/mystars-faas-fulfilment-api · machine-readable index on apis.io