Pricing

Pay for what you use. Know the cost before every call.

Discovery, scoring, and browsing are always free. When your agent runs a capability through Rhumb, you pay per call — and you can check the exact price before committing. No subscriptions, no seat fees, no minimums.

Choose your path

Same directory, different execution rails.

Discovery is always free. Execution depends on how you want authorization and payment to work: account API key, wallet-prefunded balance, zero-signup x402 per-call, or BYOK passthrough.

Browse

Scores, comparisons, read endpoints, and MCP discovery. No signup, no key, no wallet.

API key

Managed

Rhumb handles routing, failover, and billing behind one key. Best default for apps and production agents.

x402

Per call

Use USDC on Base when the agent should pay directly and the payment proof should authorize each request.

Wallet prefund

Reusable

Authenticate wallet once, top up balance via x402, then execute repeat calls with X-Rhumb-Key.

BYOK

Zero markup

Route through Rhumb with your own provider credentials when you need direct vendor control or enterprise boundaries.

Three payment rails, one execution endpoint

Rhumb supports three ways to fund execution traffic: account billing with API keys, wallet-prefunded balance, or x402 per-call settlement. All roads still end at POST /v1/capabilities/{capability_id}/execute.

Rail	Auth	Best fit
Governed API key	X-Rhumb-Key	Apps and teams with dashboard-based billing controls.
Wallet-prefunded balance	X-Rhumb-Key	Wallet-first agents that want reusable balance for repeat calls.
x402 per-call	X-Payment	Zero-signup and strict request-level payment authorization.

Discovery

Always free

Browse services, read scores, search the directory, check comparisons, and call any read-only endpoint. No signup required. No limits.

Includes: Search, scores, comparisons, MCP discovery
Auth: None required

Explore services

Standard

API key

Rhumb handles credentials, routing, failover, and billing. You get pre-call cost estimates, smart provider selection, and fail-closed execution safety. Pay per call, no commitments.

Auth: X-Rhumb-Key
Pricing: Per-call, with estimates before every call
Best for: Apps, agents, and production workloads

Get API key

Enterprise

Contact

For teams that need procurement support, security review coordination, or a direct conversation about rollout and controls.

Best for: Security-conscious teams and larger deployments
Commercial model: Discuss with Rhumb

Contact

Usage

What counts as a call?

1 call = 1 API call to a third-party service routed through Rhumb. Scoring, searching, and browsing are always free. You're only charged when Rhumb makes an API call on your behalf.

Example	Counts as	Notes
Send an email via Resend	1 call	Rhumb makes one third-party API call on your behalf.
Search for a service on Rhumb	0 calls	Discovery is never charged.
Get an AN Score for a service	0 calls	Scoring is always free.
Execute a 3-step capability chain	3 calls	Each provider API call counts separately.
Failed call (provider error)	0 calls	Provider errors are not charged.

Pricing FAQ

What counts as a call?

A call is one API call to a third-party service routed through Rhumb. Searching, scoring, and browsing are always free, and failed provider calls are not charged. See the examples above .

What is the difference between API key, wallet-prefund, and x402?

API key and wallet-prefund both execute with X-Rhumb-Key. API key is account-first billing; wallet-prefund is wallet-first funding that tops up reusable balance. x402 is per-call payment-as-auth using X-Payment. See the examples above .

For agents and automation

The canonical machine-readable source remains public. Resolve the pricing contract, then call the estimate endpoint for exact per-call numbers before you run anything.

Contract

curl https://api.rhumb.dev/v1/pricing

Estimate

curl "https://api.rhumb.dev/v1/capabilities/{capability_id}/execute/estimate"

For wallet-first flows (x402 per-call and wallet-prefunded balance), see our Agent Payments guide.