· Standard
U
Community-Eintrag
llms.txt erreichbar
KI-Impact-Score 95/100 · A
UseAPI.net ist im llmstxt.info-Verzeichnis als KI-auffindbare Organisation gelistet. Branche: Entwickler-Tools. Die Website useapi.net stellt ihre llms.txt unter https://useapi.net/llms.txt bereit. Der Eintrag besteht seit 23. January 2026.
Geschäftskategorie
Entwickler-Tools
Eingetragen seit
llms.txt-Adresse
Beschreibung
UseAPI.net provides API access to leading AI models for video creation, image generation, music composition, speech synthesis, face swapping, and more — all through a single $15/month subscription. Each API connects your existing AI website account(s) to a fully-featured REST API at website subscription prices, significantly cheaper than official API rates. Multi-account configuration with automated load balancing is included. An active subscription to the underlying service (e.g. Midjourney, Ru
Gemäß DSGVO Art. 17 kannst du die Löschung deiner Daten beantragen.
llms.txt — Aktueller Inhalt
Öffnen ↗
# UseAPI.net — third-party API for popular AI services
<small>Index generated: 2026-07-07 00:20 UTC</small>
> UseAPI.net provides API access to leading AI models for video creation, image generation, music composition, speech synthesis, face swapping, and more — all through a single $15/month subscription. Each API connects your existing AI website account(s) to a fully-featured REST API at website subscription prices, significantly cheaper than official API rates. Multi-account configuration with automated load balancing is included. An active subscription to the underlying service (e.g. Runway, Kling) is required.
## Start here
- [Model Matrix](https://useapi.net/model-matrix): **Canonical list of every model across every API** (video, image, music, speech, face swap, upscale, extend, effects). The authoritative source for what models are available where, with notes on unlimited / free / Premium-only tiers. Always check this first to find which API exposes a given model.
- [Complete API spec](https://useapi.net/assets/aibot/all.txt): Single combined documentation file for all supported APIs (~4 MB). Feed this to your LLM for cross-service integrations. For smaller-context models, fetch only the per-service files listed below.
- [General Q&A](https://useapi.net/assets/aibot/qa.txt): Cross-cutting tips (rate limiting, prompt moderation, common patterns). **WARNING**: items are general-purpose and may reference deprecated APIs, sunsetted services, or scenarios not applicable to a specific API — always cross-check against the relevant service-specific documentation before applying.
- [Account management](https://useapi.net/assets/aibot/account-management.txt): Programmatic account endpoints — check credits & usage statistics (`GET account`, `GET account/stats`) and set account-level defaults like the global `replyUrl` webhook (`POST account`).
- [Subscription & pricing](https://useapi.net/docs/subscription): The single flat $15/month useapi.net subscription — what's included and how it works (an active subscription to each underlying AI service is still required).
- [Legal & Terms of Service](https://useapi.net/docs/legal): Terms of service and legal information for the experimental APIs.
- [Postman & Swagger](https://useapi.net/docs/postman-swagger): The Postman workspace and Swagger / OpenAPI specs for the APIs.
- [Support](https://useapi.net/docs/support): How to get help — Discord, Telegram, and email.
## Universal conventions
**Authentication.** Every useapi.net request uses header `Authorization: Bearer <token>`. The token format is `user:<number>-<unique-string>` (e.g. `user:12345-abcdefghi`). **Use the complete string** — include the `user:` prefix and the alphanumeric suffix. Do not truncate to just the number. Do not URL-encode. A single token authorizes every API under the user's subscription.
**Cross-service shared models.** The same underlying model (Veo 3.1, Seedance 2.0, Nano Banana, etc.) is often exposed by multiple useapi.net APIs. Request and response shapes DIFFER between APIs even for the same model — each API exposes its own native interface. Veo 3.1 via Google Flow uses a different request body than Veo 3.1 via Runway. See the Model Matrix to find which API exposes a model, then consult THAT API's documentation for its specific format.
**Everything else is service-specific.** Identifier names (`jobid` / `taskId` / `musicId` / etc.), job lifecycle, response shapes, webhook payload shape, status code semantics, and synchronous-vs-asynchronous behavior vary per API. Use the per-service documentation below as the authoritative source for each API.
## Tutorials & Guides
Worked, copy-pasteable tutorials (curl commands, runnable scripts, and sample output) for common tasks. Combined full text of every guide: [all tutorials (articles.txt)](https://useapi.net/assets/aibot/articles.txt). Individual guides by API:
**Google Flow**
- [Nano Banana 2 Lite vs 2 vs Pro: Google Flow Image Models Compared](https:/
[…gekürzt]