Question 1

What does reAPI actually do for each call?

Accepted Answer

reAPI reads the model name in your request, looks at vendor health, current latency, and current load, and hands the call to whichever candidate is most likely to return cleanly fastest. Health checks run continuously, so the route table is always live, not refreshed on a schedule. When the chosen vendor regresses mid-flight, the next call moves automatically and your application never sees the failure.

Question 2

Do you keep my requests or responses?

Accepted Answer

No. Request bodies and model outputs travel through the AI API aggregator but are never persisted. We retain only billing and audit metadata: model name, token counts, latency, status code, and key identifier. That is what compliance reviews want and what we are willing to be on the hook for. The same posture is the industry baseline among serious gateways.

Question 3

Does my code change to use reAPI?

Accepted Answer

Set the base URL to https://reapi.ai/api/v1 and supply a key minted in the dashboard. The OpenAI, Anthropic, and Google SDKs continue to work unmodified — reAPI preserves their request and response shapes. Provider-specific paths like Veo or Suno mirror the original vendor request shape, so an existing integration moves over without a rewrite.

Question 4

What does 99.96% uptime mean in practice?

Accepted Answer

Every popular model is fronted by multiple vendors. When one degrades, reAPI moves traffic to the next within a sub-second window and the call still returns. Single-source models surface a structured error rather than guess. The status page publishes a rolling history.

Question 5

Do I need API keys from each provider, or just reAPI?

Accepted Answer

One reAPI key covers every supported model. We handle the vendor relationships behind the scenes, so there are fewer keys to rotate, fewer dashboards to monitor, and a single audit trail across image, video, chat, music, and code workloads. Adding a new provider to the catalog reaches your account without any procurement work on your side.

Pricing

Pay-as-you-go credits. $1 = 1,000 credits. Credits never expire.

Pricing

Pay-as-you-go credits. $1 = 1,000 credits. Credits never expire.

Questions

Questions

Pricing

Pay-as-you-go credits. $1 = 1,000 credits. Credits never expire.

Pricing

Pay-as-you-go credits. $1 = 1,000 credits. Credits never expire.

Questions

01What does reAPI actually do for each call?

02Do you keep my requests or responses?

03Does my code change to use reAPI?

04What does 99.96% uptime mean in practice?

05Do I need API keys from each provider, or just reAPI?

Questions

01What does reAPI actually do for each call?

02Do you keep my requests or responses?

03Does my code change to use reAPI?

04What does 99.96% uptime mean in practice?

05Do I need API keys from each provider, or just reAPI?