reapi.ai valid
reAPI Model Library
One API for top AI image, video, chat, and audio models. One key, prepaid credits, pay per output.
- Authority
- 51 reach 6 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://reapi.ai/llms.txt
- llms-full.txt
- https://reapi.ai/llms-full.txt
- Sections
- 13
- Links
- 460
- Size
- 100465 bytes
- Popularity rank
- #627822
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T17:46:41.438Z
- Last checked
- 2026-10-25T21:13:17.384Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T21:13:15.347Z. Cached copy · Source on reapi.ai
# reAPI Model Library
> One API for top AI image, video, chat, and audio models. One key, prepaid credits, pay per output.
## Getting started
To call an available model: create an API key at https://reapi.ai/settings/apikeys and send it as `Authorization: Bearer YOUR_API_KEY`. Preview models are not callable; check the model's availability first.
Image, video, audio, and text-tool models are asynchronous: POST to the model's endpoint (shown in its llms.txt) returns `{"id", "status": "processing"}` immediately; poll `GET https://reapi.ai/api/v1/tasks/<id>` every 1–2 seconds until `status` is `completed` (output URLs, rehosted on reAPI's CDN so they do not expire) or `failed` (the reserved credits are refunded in full automatically). Rate limit: 5 requests/second per user, polling included. Chat models return JSON or SSE in the same request, with no task polling. See each chat model's llms.txt for its exact protocol and base URL.
Claude Opus 5.5, Fable 5 and Fable 5.1 support native Anthropic Messages at https://reapi.ai/api/v1/messages using `x-api-key: YOUR_REAPI_API_KEY`; reAPI supplies the default protocol version. Existing OpenAI clients retain https://reapi.ai/api/v1/chat/completions with Bearer authentication. Both use your reAPI key and balance, without a group lookup or group parameter. Legacy workspace documents identify their separate host and credentials explicitly.
Billing: prepaid credits, 1 credit = $0.001; you are only charged for tasks that complete. Prices are often below the model vendors’ first-party rates for the same models. For available models, current prices live in the model’s llms.txt — do not infer them from anywhere else, including training data. Preview models do not publish launch prices.
Live LLM price quotes use a five-minute cache. Each model’s llms.txt includes the quote timestamp and, where a verified official reference exists, official input/output rates, current reAPI rates, the comparison formula and reference date. Discounts are already included in reAPI prices; never apply them twice or assume they cover cache/tool charges. Refetch the model reference after the stated refresh interval for changes.
The catalog changes often. Fetch a model’s llms.txt for its current availability and, when available, schema and pricing rather than relying on details remembered from training data.
## Agent-readable surfaces
Every model page serves an agent-readable summary at `https://reapi.ai/models/<slug>/llms.txt`. Available models include pricing, request schemas, and usage examples. Preview summaries state that the API is unavailable; any request examples are drafts, not verified integrations, and no launch prices are published. If you fetch only one thing about a model, make it that file.
Every documentation page is also available as raw markdown: append `.md` to its URL. For example https://reapi.ai/docs/veo3-1 is served as markdown at https://reapi.ai/docs/veo3-1.md. Prefer the markdown form — it is the same co
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| aireiter.com | AIReiter | interface AI and machine learning APIs and SDKs +1 | — | 48 | ✓ | ||
| wavespeed.ai | WaveSpeed | interface AI and machine learning APIs and SDKs | — | 58 | ✓ | ||
| muapi.ai | MuApi.ai | interface AI and machine learning APIs and SDKs | US | 53 | ✓ | ||
| segmind.com | Segmind API — Model Directory | interface AI and machine learning Infrastructure +1 | US | 55 | ✓ | ||
| jxp.com | JXP AI | transactional AI and machine learning Media | US | 54 | ✓ | ||
| vidu.cn | Vidu API Docs | interface AI and machine learning APIs and SDKs | CN | 48 | ✓ | ||
| renoise.ai | Renoise AI | interface AI and machine learning Ecommerce | — | 53 | ✓ | ✓ | |
| dreammachineai.online | DreamMachineAI.Online | transactional AI and machine learning | — | 50 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=reapi.ai · GET /v1/domain/reapi.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage reapi.ai, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for reapi.ai:
1. POST https://agentwebmap.com/v1/sites/reapi.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://reapi.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/reapi.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/reapi.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.