Obol | Give Your Agent Real-World Reach

Why Obol?

Pay Only When It Runs

A few cents per call. No subscriptions, no monthly minimums. Your agent only pays when it actually does something.

Pay How You Want

Buy credits with a credit card, let your agent pay automatically via x402, or set a spending cap with sessions. Your choice.

✓

Proof of Every Call

Every action your agent takes is logged with a receipt. Full audit trail you can verify anytime.

…

Your Keys, Your Control

Connect your own API keys for each service. They're encrypted and never logged. You control exactly what your agent can access.

Control & Trust

Your agent acts on your behalf. You should be able to see what it's doing, set limits, and approve the risky stuff.

Preview Before Execute

Simulate any action before it runs. See the resolved parameters, policy result, and estimated cost — without touching the real API.

Approval Gates

High-risk actions require human approval before they execute. Configurable per operation, provider, or risk tier.

Budget Guardrails

Per-call limits, daily and monthly caps, and per-provider spending controls. Policy-enforced budget gates block requests that exceed caps.

Execution Receipts

Every execution produces a receipt with a full audit trail — what ran, when, what it cost, what it returned. Optionally cryptographically signed for tamper-proof verification.

How It Works

Run Setup

Run the setup wizard, name your agent, and connect your accounts. Takes about 60 seconds.

Choose How to Pay

Buy credits with a credit card, or have your agents pay automatically via the x402 protocol. Either way, a few cents per call.

Your Agent Runs

Your agent tells Obol what it needs to do. Obol handles authentication, payment, execution, and gives you a receipt for every call.

Get Started in 60 Seconds

Run one command. The setup wizard registers your agent, saves a recovery key, connects your services, and configures either automatic agent payments or credits.

Terminal

$ npx -y -p @obol/cli obol setup

●  Welcome to Obol!
│  Let's connect your agent to Obol.

◇  Which services does your agent need?
│  ☑ Stripe  ☑ GitHub  ☑ Slack  ☐ Notion  ☐ Discord
│
◇  How should your agent pay for Obol calls?
│  ● Automatic USDC payments (recommended)
│
│  ✓ Account created
│  ✓ Setup key saved to .env
│  ✓ SDK installed
│  ✓ Created obol.js
│  ✓ Connected! 3 services linked (Stripe, GitHub, Slack)
│
◼  Your agent is connected to Obol!

Requires Node.js 18+. The setup wizard can enable automatic x402 agent payments or prepaid credits.

your-agent.js

import { ObolClient } from '@obol/sdk';

const obol = new ObolClient();  // reads token + payment mode from .env

// Create a GitHub issue
const result = await obol.execute(2, 'Create issue titled "Deploy checklist" in myorg/myrepo');

// Send a Slack message
await obol.execute(3, 'Send "Deployment complete ✓" to #engineering');

Provider IDs: 1=Stripe 2=GitHub 3=Slack 4=Notion 5=Discord 6=Twitter 7=AgentMail

Automatic x402 agent payments are available in the JavaScript SDK today. Python onboarding uses credits by default.

Integrations

Your agent can use any of these services through Obol today.

Stripe

Create invoices, charge customers, manage subscriptions and payouts.

GitHub

Open issues, create pull requests, comment on code, manage repositories.

Slack

Post messages, manage channels, automate workflows and notifications.

Notion

Create pages, update databases, sync workspaces and documents.

Discord

Send messages, manage servers, handle interactions and events.

Twitter / X

Post tweets, manage threads, engage followers and monitor mentions.

AgentMail

Create inboxes, send and receive emails, reply to threads — email for agents.

Simple Pricing

You only pay when your agent uses an Obol integration. No subscriptions, no monthly fees, no minimums.

Without Obol

~$2,000+/mo

Build & host your own integrations, manage API auth, handle errors, maintain uptime for each service

vs.

With Obol

~$50–100/mo

Same capabilities, pay only for calls your agent makes. No infrastructure to build or maintain.

Based on a typical agent making 10K API calls/month across multiple providers. Your savings depend on usage.

RECOMMENDED

Agent Payments

Your agent pays automatically in USDC using the x402 protocol on Base. Each API call is a micropayment — a few cents settled instantly on-chain. No pre-funding, no credit packs, no interruptions. Obol's JavaScript SDK can do this out of the box today, and any x402-compatible client can too.

✓ Only charged when your agent calls an Obol integration

✓ Open protocol — works with any x402-compatible client

✓ Instant settlement on Base

Don't have a crypto wallet? No problem.

Credit Card

Buy credit packs via Stripe. Your agent draws from your balance as it runs. Bigger packs include bonus credits. The website checkout asks for your setup key so credits can only land on your agent.

Choose your tier on checkout. Available after running setup.

Sessions

Set a spending cap upfront. Your agent runs until the budget is used up. Unused balance converts to credits you can use anytime.

✓ Spending limits

✓ Unused balance → credits

✓ $0.50 per session

Configured via the CLI or SDK after agent setup.

Refer Agents, Earn Credits

Every agent you bring to Obol earns you real money. Commissions last as long as your referrals use Obol.

Signup Bonus

Your referral gets $5 in free credits. You get $2 when they make their first real payment.

10%

Ongoing Commission

Earn 10% on every API call your referrals make. For as long as they use Obol.

1 cmd

Easy Setup

Run npx -y -p @obol/cli obol referral code to get your unique code. Share it anywhere.

Frequently Asked Questions

Without Obol, every agent needs its own code to talk to Stripe, GitHub, Slack, etc. That means building, hosting, and maintaining separate integrations for each service. Obol replaces all of that with a single API call. Your agent says what it wants to do in plain English, and Obol handles the rest — auth, execution, payment, and proof it happened. You pay a few cents per call instead of hundreds in engineering and hosting costs.

No. You can pay with a regular credit card through Stripe — just like buying anything else online. If you do have a crypto wallet, you can also pay with USDC on the Base network for instant per-call payments. Both options work, pick whichever you're comfortable with.

You bring your own API keys for each service you want your agent to use. Obol stores them encrypted — they never leave the server and are never logged. You can also connect via OAuth (like "Sign in with GitHub") for supported services. You stay in full control of which accounts your agent can access.

If a call fails, you don't pay for it. Every successful call produces a receipt recording what happened. When an oracle signing key is configured, receipts are cryptographically signed for tamper-proof verification. Obol also has built-in replay protection so no call can accidentally run twice.

Obol currently supports Stripe, GitHub, Slack, Notion, Discord, Twitter/X, and AgentMail. More services are being added regularly. Each service works the same way — your agent describes what it wants to do, and Obol translates that into the right API calls.

Every operation has a risk tier (low, medium, high). High-risk actions — like issuing refunds, creating pull requests, or dispatching workflows — require human approval before they execute. You can also configure approval rules per provider or operation, and preview any action before it runs.

Yes. Obol policies let you set per-call maximums, monthly budgets, and per-provider limits. You can also set velocity limits (calls per minute). Requests that exceed any cap are blocked before execution. All configurable through the admin dashboard or API.