Payouts

How earnings accrue

Every time an agent calls one of your service's endpoints, the platform records a transaction with three values:

• amount_microdollars: total charged to the agent (your listed price)
• commission_microdollars: platform's cut (default 10%)
• provider_payout_microdollars: what you're owed (amount minus commission)

These accumulate in the database, unsettled, until the daily payout cron processes them.

Daily payout schedule

Payouts run automatically every day at 06:00 UTC. The cron:

1. Aggregates all unpaid completed transactions per provider
2. For each provider above the minimum threshold, transfers USDC from the platform wallet to the provider's configured wallet on Base
3. Marks the transactions as paid out, linked to a provider_payouts row with the on-chain tx hash
4. Sends an email notification with the payout amount and tx hash

Minimum payout threshold

The minimum is $1.00 per provider per run. If your unpaid balance is below this, the payout is skipped and the balance carries to the next day.

Why: each on-chain transfer costs gas. Below $1, the gas-to-payout ratio gets uneconomic for both us and you. Larger payouts amortize gas across more revenue.

Commission

Default platform commission: 10% of the call price. You receive 90%.

For a $0.001 endpoint:

Agent pays:           $0.001000  (1000 microdollars)
Platform commission:  $0.000100  (100 microdollars, 10%)
Provider receives:    $0.000900  (900 microdollars)

Custom commission rates per service or per provider can be arranged. Reach out via support if you need this.

Configuring your payout wallet

Set this once in Settings on the dashboard. The address must be:

• A valid EVM address (0x prefix, 40 hex chars)
• Capable of receiving USDC on Base (Base mainnet for production, Base Sepolia for test environments)

Either connect a browser wallet to populate the field, or paste an address manually using the "or enter manually" link.

Where to see payout activity

From the dashboard's Payouts tab you see:

• Pending earnings (unsettled, accrued since last payout)
• Last payout amount, status, and on-chain tx hash (linked to Basescan)
• Full history of past payouts with dates and amounts
• Per-service breakdown of what generated this period's earnings

Failure handling

If a payout fails (e.g. wallet address invalid, network congestion, gas issue):

• The transaction batch is marked failed with the error message
• Underlying transactions are NOT marked paid, so the balance is preserved
• Admin gets an alert email; you receive a notification with the failure reason
• The next day's run retries automatically with the accumulated unpaid balance
• Admin can also manually retry from the admin dashboard

What if you have no wallet on file?

You still accrue earnings as agents call your services. The cron skips you (no destination address). Once you add a wallet, the next run picks up your accumulated balance and pays it out.

Taxes and reporting

Each payout creates an on-chain record. The receipt URL (Basescan) is the canonical proof of receipt. Your dashboard shows full payout history exportable for accounting.

APIHub does not currently provide 1099 forms or other tax documentation. You are responsible for reporting your earnings according to your jurisdiction.

Quick reference

• Schedule: daily, 06:00 UTC
• Currency: USDC on Base mainnet (or Base Sepolia for test environments)
• Commission: 10% (default)
• Minimum payout: $1.00 per provider per run
• No-wallet behavior: earnings accrue indefinitely; payouts skip until address is set
• On failure: automatic retry next day, admin notification, balance preserved