Beta
infer0 lets end users connect their AI provider keys and authorize apps to use them. Developers integrate once using the API format that fits their stack. infer0 routes to whichever provider each user chooses without changing a line of code.
01 Connect AI providers. Set daily spend limits.
02 Apps use your AI provider. Never see your keys.
03 Per-app spend limits. Pause or revoke anytime.
1
Create an OAuth app in Developer Settings to get a client ID and secret. Add the infer0 OAuth flow to your app. Use any supported API format. infer0 translates between providers automatically.
2
Each user connects their OpenAI, Anthropic, or Google API key. Keys are encrypted with AES-256-GCM and stored securely. Users can set a per-provider daily spend limit to control costs.
3
During the OAuth flow, each user chooses which AI Provider the app may use. They can change the assigned provider or set a per-authorization daily spend limit later from their Authorizations page.
4
Your app passes the user's access token to the endpoint that matches your SDK. infer0 looks up their AI Provider, checks spend limits, forwards the request, and translates the response back into the format your SDK expects.
//
Use the OpenAI or Anthropic SDK your codebase already has. infer0 supports Chat Completions, Messages, and Responses formats. No provider-specific routing logic needed.
/**
Provider API keys are encrypted with AES-256-GCM and never exposed to your app. You don't store, handle, or even see them.
*/
Each user pays their own AI provider bills. Your app never handles billing, credits, or API costs. You only pay for your own hosting.
△
Connect your OpenAI, Anthropic, or Google API key. Switch which provider each authorized app uses. Set daily spend limits per provider to stay within budget.
△
Each authorized app gets its own provider assignment and daily spend limit. Change these anytime from your Authorizations page. Pause or revoke an app in one click.
△
Add, remove, or switch providers anytime. Set daily spend limits per authorization and per provider. Revoke any app's access instantly from your dashboard.
infer0 is in early development. If you are building something with it, tell us about it and we will feature your project here.
infer0 does not log or store prompt or completion content. Metadata for rate limiting is retained, but message bodies are never written to disk.
Provider API keys are encrypted with AES-256-GCM before storage. Tokens are hashed. Encryption keys are managed separately from the database.
Encrypted data cannot be read by infer0 staff. Encryption keys are managed separately from the database and never exposed to the application.
Users can revoke any app's access from their Authorizations page. Revoking immediately invalidates all associated tokens and blocks further requests.
Account profiles, encrypted provider configs, and OAuth authorization records are retained. Users can delete providers and revoke authorizations at any time.
User API keys with their AI provider remain valid and unaffected. App requests to infer0 will fail until service resumes. Handle this gracefully in your app.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。