Channel
@use_api
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
443subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002078752407 |
|---|---|
| Type | Channel |
| Username | @use_api |
| Description | Third-party API for Midjourney, Kling, Mureka (Suno/Udio competitor), Runway, MiniMax, PixVerse, InsightFaceSwap and Pika Visit https://useapi.net Discord https://discord.gg/w28uK3cnmF Reddit https://reddit.com/r/aiAPI |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/use_api |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 05:04 | 443 | no change |
| 7 Aug 2026, 13:12 | 443 | first reading |
18 posts held, back to 26 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 5 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 18 (26 June 2026 – 6 August 2026) |
| Views total | 2,104 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 05:04 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
8 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 50.0% | |
| ❤ | 3 | 37.5% | |
| 🔥 | 1 | 12.5% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 7 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 26 June 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
MiniMax API v1 — 768p on Hailuo 3.0: • Hailuo-3.0 now accepts resolution: "768" alongside 1440 (2K, still the default). 768p is billed at 7 credits per second against 12 for 2K, and a video reference is charged on its own length at the same rate as the output.
MiniMax API v1 — Hailuo 3.0 on POST videos/create: • New video model Hailuo-3.0 (MiniMax H3) — 2K output at 24 fps, 4–15 seconds, with native stereo audio on every generation. The short edge is 1440 pixels, so 16:9 renders 2560×1440 and 9:16 renders 1440×2560. • Supports text-to-video, start/end frames, and omni references — up to 9 images (@Image1…@Image9), 3 videos (@Video1…@Video3), and 3 audio clips (@Audio1…@Au…
👍1
Google Flow API v1 — occasional missing media download links: Google hands out media download links from an endpoint that limits how often it will answer a given network address. This is Google limiting our outbound calls, not useapi.net limiting you, and nothing you do triggers it. When it happens, Google returns an "unusual traffic" block page instead of a link, and it clears on its own. To put the frequency in co…
❤2
https://useapi.net/docs/articles/seedance-2-api-pricing
❤1👍1
Mureka API v1 — email + password accounts that stay connected: • POST /accounts now accepts email + password to connect a dedicated Mureka account. The API stores the password and logs back in automatically whenever Mureka ends the session, so the account keeps working with no manual re-linking — the most durable way to connect. The existing token + refresh_token method still works. See Setup Mureka. • New guided C…
👍1
Kling API v1 — connect accounts that hit the login slider captcha: • POST /accounts now accepts an optional passToken + did + userId trio (all three together, or none). Provide them for an account that gets the Kling login slider captcha, which our server cannot solve — the values are your signed-in Kling session, captured from your own browser where you solve the slider once. The account is then stored in passToken…
AI Music APIs Compared: Mureka vs MiniMax vs ElevenLabs vs Lyria 3 Pro https://www.youtube.com/watch?v=9-tVK4SYuR4
👍1
Runway API v1 — workspace (team) accounts: • POST /accounts now accepts useWorkspace to bill generation against a paid Runway workspace (team) an account was added to, rather than the account's own plan. Pass true to auto-select the account's single paid workspace, or a team id to pin a specific one. The resolved workspace is returned in the new workspace object and shown by GET /accounts. • GET /features now return…
PixVerse API v2 — Seedream 5.0 Pro image model: • New image model seedream-5.0-pro (Seedream 5.0 Pro) on POST /images — ByteDance's high-quality generation and editing model. Generates at 1080p (15 credits) or 1440p (30 credits) and accepts up to 10 reference images for image-to-image. Unlimited with Ultra PixVerse subscription. • seedream-5.0-lite now generates at 2160p (18 credits), alongside its existing 1440p an…
Mureka API v1 — simpler, fully browserless account setup: • POST /accounts now takes the token and refresh_token you copy from Mureka at sign-in, instead of a Google cookie. The API keeps your session alive on its own — when the token expires it refreshes with no browser and no Google involved. See Setup Mureka. • New one-page Connect Mureka flow captures both tokens for you — run the snippet, sign in to Mureka, and…
Runway API v1 — Nano Banana 2 Lite image model: • New image model nano-banana-2-lite (Gemini 3.1 Flash-Lite Image) on POST /images — Google's fastest image model, up to 14 reference images. Unlimited with exploreMode. • All Nano Banana models now accept aspect_ratio auto, which is also their new default — the request omits the ratio and the model picks it.
PixVerse API v2 — Nano Banana 2 Lite image model: • New image model nano-banana-2-lite (Gemini 3.1 Flash-Lite Image) on POST /images — Google's fastest, most cost-efficient image model. Generates at 1080p and accepts up to 14 reference images for image-to-image, the only PixVerse image model that exceeds 9. • Free in unlimited Relax Mode on Pro ($30/m) and higher plans, the same as qwen-image.
Showing the 12 most recent of 18 posts we hold for @use_api. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
@use_api named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 August 2026 — this entry's latest reading, not the date you are reading this.
“useapi.net” (@use_api), 443 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/use_api.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.