AI
Pass

How AI Pass Works

From multiple API keys to one universal AI wallet

1

Today: The Problem

Apps keep API keys on their server, implement different methods for each provider, and manage each one separately

📱 Bupple
(AI App)
api_key
api_key
api_key
✨ Gemini
🎨 Fal AI
🤖 OpenAI

Different API keys, different methods, different implementations for each provider. Developer pays for everything.

2

Step 1: Replace with AI Pass Proxy

One API key, one method — replaces all providers. Like OpenRouter, but with zero commission.

📱 Bupple
(AI App)
api_key
⚡ AI Pass
Proxy
routes to
✨ Gemini
🎨 Fal AI
🤖 OpenAI
💰 Zero commission on API key mode

No need to implement different methods for different APIs. One integration, all providers. Zero commission — we do this free to help them move to step 2.

3

Step 2: Implement OAuth

Like Google OAuth — users connect their AI Pass wallet. Then just swap the API key with the user's OAuth token. Same format, same request — our server uses user's credit instead of theirs.

User opens 📱 Bupple
Connect AI Pass
OAuth
AI
Pass
Allow Bupple to
use your AI wallet?
✓ Approve

OAuth2 Token returned to app

📱 Bupple
User's request
api_key
oauth_token
⚡ AI Pass
Proxy
AI response
🤖 AI
Provider
🔑 Exact same request format — just change authentication from API key to user's OAuth token
🔒 More secure: users never share their API key — OAuth token can be revoked anytime
🎯

See It Live

Try it yourself at chat.aipass.one — an AI chat app powered by AI Pass

Step 1

Sign in with AI Pass

AI Pass Sign In
Step 2

Approve the app

OAuth Approval
Step 3

Chat with AI — paid from your wallet

AI Pass Chat

The app never sees API keys. Users control their own wallet and can revoke access anytime.

Everyone Wins

👨‍💻

Developer

Zero AI costs. One integration. Earns 20% on every API call.

👤

User

One wallet for all AI apps. Pay as you go. No subscriptions.

🔒

Security

OAuth tokens, not API keys. Users control access and can revoke anytime.

Embed AI Pass — How It Works