Optional sponsored offers
Earn your credits
Discover tools or watch sponsored videos. Eligible, verified activity earns credits you can use for AI.
Rewards become available after verification and maturation.
Build more.
Spend less on AI.
One wallet for your AI coding tools. Earn credits from optional sponsored offers, add funds, or bring your own API keys.
Desktop app for macOS, Windows and Linux.
Ready for your next idea.
Available credits
1,280credits
800 purchased480 earned
Recent activity
Code review
Frontier model
Sponsored exploration
Verified reward, matured
Project summary
Fast model
Discover & earn
Sponsored exampleA new tool.
Your next AI credits.
Explore a useful product. Eligible, verified actions earn credits for your next project.
How earning worksOne wallet
Compatible with your tools
Ads are always optional
Your tools.
One place to power them.
Keep the workflow you know. Obol Wallet brings your AI credits, model access and usage into one place.
- 1
Make it yours
Download the Obol Wallet app and sign in. No organization setup required.
- 2
Choose how to fund it
Earn credits through sponsored offers, add paid credits, or connect your own provider keys.
- 3
Connect and build
Add your Wallet key and endpoint to a compatible tool. Follow every credit in your activity.
A wallet that works
your way.
Start with the option that suits you.
Keep control as your projects grow.
More credits. Your choice.
Start free with $1 in credits every day, no card required. Choose a monthly allowance for regular builds, or top up when you need more. Your credits work across supported AI models.
Free forever
$1 in credits every day
No card required. No end date. Daily credits refresh each day and don't roll over. Earn extra credits by watching sponsored videos and engaging with eligible ads.
Ad rewards depend on verified activity and campaign terms. Watching and engaging are always optional.
Monthly subscriptions
USD, billed monthly
Starter
$15/ month
100,000
credits each billing period
Plus
$25/ month
200,000
credits each billing period
Pro
$55/ month
500,000
credits each billing period
Monthly credits expire at the end of each billing period and do not roll over. Cancel renewal anytime; your paid allowance stays available until that period ends.
Just need a little more?
Add a one-time credit top-up, with or without a subscription. Keep it for your next build: purchased credits have no scheduled expiry.
No recurring charge. No automatic refill.
Choose a credit pack
50,000 credits
$10one time
Sign in to continue to secure Stripe Checkout. Availability is confirmed at checkout.
Less wasted compute.
More room to build.
A lower AI bill starts with the work you avoid repeating. Wallet brings caching, model choices, spending controls and optional sponsored credits into one workflow.
Early-access feature guide. Availability depends on the model and rollout. Savings vary with your workload and provider rates; a lower price on every request is not guaranteed.
Make repeated context cost less
Provider prompt caching can reduce the cost of repeated instructions and project context. Wallet accounts for cache reads and writes separately. Supported Anthropic cache writes are enabled only when expected reuse saves money.
Savings depend on the model, cache lifetime and reuse. A cold request may cost more than a cache hit.
Pay for usage, release the rest
Wallet reserves a spending allowance before a request, then settles against attributable usage at the agreed model rates. Unused reserved credits return to your balance.
A reservation is not a charge. Missing usage stays subject to review instead of becoming an estimated bill.
Let sponsors fund part of the work
Eligible, verified sponsored activity can earn credits for your AI usage. Combine matured rewards with paid credits, or keep ads off and use your own provider keys.
Rewards depend on funded offers and verification. BYOK usage stays on your provider bill.
Explore the opt-in controls.
Advanced controls are not live by default. They require your permission, compatible models and rollout approval. Ordinary requests keep their existing behavior.
Send what the next step needs.
Opt-in context and output controls reduce unnecessary input and keep responses within the bounds you choose.
- Bounded conversation history
- Keep recent required turns and use a summary or key facts you supply for older context. Protected instructions and complete tool exchanges stay intact.
- Selective context and examples
- Select relevant material from context you mark as optional, and prune examples you explicitly allow Wallet to remove. No automatic repository indexing or paid summarizer is implied.
- Tool-result limits
- Cap eligible older tool results so a large output does not keep inflating later requests. The newest tool exchange and code whitespace remain protected.
- Output limits and formats
- Set tighter output-token limits, stop conditions or supported structured formats. These are explicit choices, with support varying by model and API.
Match the model to the job.
Keep routine work on eligible lower-cost routes, with stronger models reserved for the tasks and budgets you authorize.
- Progressive model routing
- Start with an eligible lower-cost tier and allow bounded escalation when appropriate. Model substitution needs permission; attempts and spend stay capped. Optional Jev advice requires separate consent and its usage is counted.
- Usage-aware route selection
- Use trusted reliability and usage metadata to choose among eligible routes. A successful API response is not treated as proof of answer quality, and selection does not require retaining prompts.
- Private and device-local modelsLocal setup required
- Use configured private routes, or an optional local runtime and models you supply. Device-local execution has no Wallet debit, still uses your hardware, and never silently falls back to paid cloud inference.
- Native speculative decodingRuntime verification pending
- A compatible inference engine may accelerate generation with a verified draft and target model pair. Actual runtime support and performance still need validation; this is not two separately billed chat calls.
Avoid generating the same answer twice.
Separate retention consent lets eligible requests reuse private, short-lived results instead of paying for a fresh generation.
- Private response reuse
- Reuse an eligible exact result within your account and key scope. Results stay in bounded memory, expire and can be purged. Each reuse is freshly authorized and gets a zero-charge reuse receipt.
- Concurrent request deduplication
- Identical requests arriving together can share one in-flight generation. Each recipient must be authorized, and a failed or canceled leader does not trigger a hidden replacement call.
- Guarded safe-task matching
- A narrow opt-in mode can ignore insignificant whitespace in eligible simple text tasks. This is not general semantic or paraphrase caching. Tools, structured outputs and freshness-sensitive work are excluded.
Give every run a spending boundary.
Track the whole job, choose asynchronous pricing when it fits, and avoid turning uncertain work into another paid attempt.
- Request and agent-run budgets
- Cap a logical request or shared agent run, including settled usage, in-flight reservations and classifier attempts. Remaining-budget signals help agents plan. Wallet budgets do not cap your external BYOK bill.
- Native provider batchesProvider support required
- Submit eligible, non-urgent text work to supported provider batch APIs at configured batch rates. Batches are explicitly asynchronous; they do not replace interactive streams or promise a discount just for waiting.
- Bounded streaming and cancellation
- Shared connections, concurrency limits, deadlines and cancellation help avoid wasted work. Streaming does not wait for a complete response, and uncertain requests are not automatically replayed. Completed work can still be billable.
Providers can offer caching and batch pricing directly, too. Wallet’s value is bringing eligible cost controls, usage and funding together across supported tools.
Compare plans and top-upsKeep your workflow.
Change the connection.
Use your Wallet endpoint and API key in a compatible client. Pick an example and copy the configuration.
One key. One endpoint.
Configuration examples for early access. Model aliases and live availability are confirmed at launch.
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://obol-wallet-api.fly.dev/v1",
apiKey: process.env.OBOL_WALLET_API_KEY,
});
const stream = await client.chat.completions.create({
model: "obol-wallet/claude-sonnet",
messages: [{ role: "user", content: "Summarize this diff" }],
stream: true,
});
for await (const chunk of stream) {
process.stdout.write(chunk.choices[0]?.delta?.content ?? "");
}
Your Wallet.
Right on your desktop.
Obol Wallet is a desktop app. Sign in, manage your keys and credits, and connect your coding tools from your computer.
Obol Wallet app
1.0.0 · Choose your operating system.
Windows
Available soonWindows x64
macOS
Available soonApple Silicon & Intel
Linux
Available soonLinux x64 · AppImage
Signed installers for macOS, Windows and Linux are on the way.
Your work stays yours.
Advertisers never receive your prompts, code or AI replies. Sponsored placements live in Wallet-owned spaces, and never change the AI’s answer.
Optional ads
Encrypted provider keys
No prompt logging by default
Good questions.
Straight answers.
A little more detail, if you need it.
More room
for your next idea.
Get ready for one wallet that keeps your AI tools working for you.