OBUL

One API Key. Infinite Agents.

Get Started
obul-about

Obul Access Skill

Universal gateway to the agent economy. Access any x402-compatible service with a single API key - Obul handles discovery, micropayments, and authentication automatically.

The Problem

You want to compose agents using specialized APIs (compute, data, reasoning), but x402 requires wallet management, gas funding, and payment negotiation. That’s a week of plumbing before you ship.

The Solution

Route every request through Obul. One Bearer token unlocks 70M+ existing transactions across the x402 ecosystem, with built-in spend tracking and rate limits.

Key difference: You don’t “integrate crypto.” You just make HTTP requests.

Configuration

Get your key in 30 seconds at obul.ai:

OBUL_API_KEY=obul_live_xxxxxxxx

No .env overload. No wallet seed phrases. No gas tanks to refill.

Usage

Call any x402 endpoint through the Obul proxy:

curl -X POST "https://proxy.obul.ai/https/api.target-service.com/v1/analyze" \
  -H "Authorization: Bearer ${OBUL_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{"input": "your data"}'

What happens under the hood:

  1. Obul discovers the x402 payment requirements
  2. Automatically attaches payment proof (handled by Obul, not you)
  3. Forwards your request to the upstream service
  4. Returns the response + tracks spend in your dashboard

Capabilities

FeatureHow It Works
Auto-Paymentx402 proofs generated and attached automatically. You never touch USDC or gas.
Unified BillingAll services aggregate into one Obul invoice. One credit card, infinite agents.
Scoped KeysCreate dedicated keys per agent with spend caps (max $5/day) and kill switches.
Ecosystem AccessInstant access to compute, search, storage, and reasoning APIs already running on x402.

Prerequisites

  • Obul account (free tier available)
  • One environment variable
  • That’s it. No browser extensions. No “Connect Wallet” buttons.

When to Use This

  • Composing workflows: Your agent needs to call paid APIs (OpenAI, compute, data sources) but you don’t want to manage 12 different API keys and billing relationships
  • Vibe-coding: You’re building in Cursor/Bolt and need infrastructure that “just works” without explaining crypto to your LLM
  • Cost control: You want granular spending limits per agent, not unlimited exposure to on-chain gas costs

Example Workflow

Your Agent → Obul Proxy → [Sentiment API] → Obul Proxy → [Translation API] → Result
            (pays $0.01)          (pays $0.002)

Total cost: $0.012
Your overhead: 0 lines of billing code

Time to BUILD!