Skip to main content
Developers earn from agent subscriptions, subscriber success fees, and related marketplace revenue splits. Use the developer revenue and claims endpoints to inspect balances, claim earnings, and track payout history. All routes require developer registration and API key authentication with HMAC signing — see API keys and HMAC.

​
Fee economics

​
Worked example: success fee

A subscriber follows your signal with a 10,000∗∗buy.Thepositionclosesat∗∗+2010,000** buy. The position closes at **+20%** profit (**2,000 profit USD). Your agent successFeePercent is 15% (applied to profit on close, not entry notional):
  1. Success fee assessed: 2,000×152,000 × 15% = **300**
  2. Platform share (20%): $60
  3. Your net success fee: $240 (claimable via strategy-fee claims)
Success fees accrue on realized profit when trades close (accrueSubscriberFeesOnClose). Fees are not charged on entry notional unless you configure legacy feeConfiguration.chargeOnPerformance: false on non-marketplace bots.

​
Worked example: subscription

You set monthlyPrice: 29. Ten subscribers pay for one month.
  1. Gross: $290
  2. Platform fee (20%): $58
  3. Creator share via Stripe Connect: $232

​
Monetization models

Set on agent create/update (pricingModel): Set subscription price via agent subscription endpoints or Dev Portal. Stripe Connect onboarding is required before paid subscriptions route creator share.

​
Revenue streams

​
Key endpoints

​
Earnings summary

Returns:
  • totals - lifetime success-fee totals from weekly payouts
  • byAgent / byPeriod - breakdowns
  • fromSubscriptions - subscription ledger with claimableUsd
  • fromTrading.claimableUsd - claimable strategy success fees
  • totalClaimableUsd - combined claimable balance
Check this before claiming.

​
Payout history

Paginated weekly payout rows: gross amount, platform fee, net paid.

​
Claim subscription earnings

Marks all CLAIMABLE subscription creator earnings as CLAIMED. Returns total USD claimed and number of ledger rows updated. Returns 400 when there is nothing to claim. Call GET /earnings first to check fromSubscriptions.claimableUsd.

​
Strategy success fee claims

Per-agent claims drain success-fee balances (SOL transfer), mark subscription-ledger rows CLAIMED, and support legacy bot feeEarnings. Capped at CLAIM_MAX_USD per agent per call. Returns 404 if the agent is not found or not owned by the caller.

​
Stripe Connect

Paid agent subscriptions route creator share (80%) via Stripe Connect transfer_data. Complete onboarding before publishing paid agents.

​
Start onboarding

Creates a Connect Express account when missing, then returns a hosted onboarding URL. Status updates via Stripe account.updated webhooks.

​
Check status

Returns Connect account status, USD balances, next payout estimate, lifetime paid payouts, and subscription MRR / churn metrics.
Returns a short-lived URL to the Stripe Express dashboard for tax forms and payout settings.

​
Typical workflow

1

Register as a developer

Complete developer registration in the Dev Portal or via POST /api/v1/developers/register.
2

Set up Stripe Connect

Call POST /stripe-connect/onboarding and complete the hosted flow before enabling paid subscriptions.
3

Publish agents

Create marketplace agents with subscription pricing. Subscriber payments flow through Connect.
4

Monitor earnings

Poll GET /v1/developers/earnings for claimable balances and GET /payouts for settlement history.
5

Claim balances

  • Subscription ledger: POST /claim-subscription-earnings
  • Strategy success fees: POST /claims/agents/{agentId} or POST /claims/all

​
Dashboard analytics

Additional developer dashboard routes (subscribers, performance, signal history) are under the Developer dashboard tag in the API Reference. These complement earnings data for operational monitoring.
  • Sandbox testing - test signal flows without affecting live subscribers
  • Signal envelope - how signals become executable trades that generate success fees
  • Error codes - handling 400/404 claim errors and rate limits