Onboarding

Sign in at apihub.io/login with your email. We send a one-time link valid for 15 minutes. After clicking, you land on the provider dashboard.

Already an agent?

Same email works for both roles. Your provider account auto-links to your existing agent profile, so credits, keys, and identity are unified.

2. Set your payout wallet

Go to Settings in the dashboard. Add a Base-compatible EVM wallet address. This is where USDC payouts land daily.

Use either a self-custody wallet (MetaMask, Rabby, hardware wallet) or an exchange-issued Base address (Coinbase supports this directly)
Click "Connect wallet" to populate from your browser wallet, or "or enter manually" to paste an address
Without a wallet on file you accrue earnings but receive nothing; payouts skip you

Verify carefully

Wallet address mistakes are unrecoverable. The system verifies checksum but not destination. Double-check before saving.

3. Decide what to publish

Two service types are supported:

REST API service

You have a REST API. Agents call your endpoints through the proxy. You set per-endpoint pricing. Optionally configure upstream auth so we add a header to every forwarded request.

Content gateway

You have web content (articles, research, premium docs). Agents fetch URLs through the proxy. You verify domain ownership and set URL pricing rules.

Commission and payouts at a glance

Default platform commission: 10% of each charged call (configurable per-service)
You receive 90% of every paid call to your services
Payouts run daily at 06:00 UTC, batched per provider
Minimum payout threshold: $1.00. Below that, balance carries to the next run
Payouts settle on Base mainnet (or Base Sepolia for test networks)

See Payouts for full details on the schedule, failure handling, and visibility.

Service status flow

New services start in draft. You activate them when ready:

draft: visible only to you. Use for setup and testing.
active: appears in the marketplace and is callable by agents.
paused: temporarily off the marketplace. You can reactivate. Past calls remain in your transaction history.
suspended: admin-initiated halt for policy violations. Contact support if this happens.

Testing your own service

When you call your own service through the proxy using one of your own API keys, the call bypasses payment. Marked as provider_test in transaction logs. Useful for QA and integration validation without burning credits.

Pick your service type and follow the dedicated guide: