Tranche

Fund the agent.
Share the revenue.

Pool USDG to launch a useful x402 service.
Receive your agreed share of the payments it earns.

Explore campaignsSee the mechanism

Capital at risk. Revenue depends on real demand.

One payment. A shared outcome.Illustrative example
200requests
01,000

At 0.05 USDG per request.

Campaign receipts10.00USDG

Only received tokens enter the split.

Backers 30%3.00USDG
Operator 70%7.00USDG
Move the request slider to explore the split.Gross receipts, not profit or a return forecast.
Onchain protocol data
Service campaigns—

Created onchain

Capital released—USDG

Launch budgets of active campaigns

Receipts received—USDG

Actual tokens received, not net profit

Paid to backers—USDG

Confirmed distributions

The funding desk.

All campaigns
ServiceLaunch budgetBacker shareReceivedOperator bond

Reading service campaigns...

Only onchain campaigns appear here. No simulated funding or customer activity.

Back a specific service, not an anonymous pool. Read its terms before committing.

Optional bond assets
NVDAQQQGOOGLAAPLMSFTAMZNMETATSLA

A business model.
Not a yield promise.

Launch capital comes from backers. Revenue comes from customers. Tranche keeps the allocation explicit.

Paid work, settled onchain.

x402

A service advertises its price. An accepted payment settles to the campaign receiver before the result is returned.

01Request the serviceHTTP 402
02Authorize exact paymentEIP-3009
03Settle to the campaignReceipt
04Return the resultHTTP 200
Protocol illustration. Not a live activity feed.

Terms before capital.

Operator. Budget. Revenue share. Deadline. Service URL. Terms hash. Fixed when the campaign is created.

Read the commitments

A bond with limits.

Operators can pledge a supported Stock Token. It follows objective activation and lock rules, not a promise to cover losses.

Understand the bond

From a budget
to a paid request.

  1. 01

    Review the service.

    Read the operator’s terms and compare their exact text with the public hash.

  2. 02

    Fund the launch.

    Pool USDG toward a defined target. Activation releases that budget to the operator.

  3. 03

    Claim received revenue.

    Backers claim in proportion to their contributions. Only received tokens can be shared.

Know the downside.

Funding can be lost.
All of it.

No customers means no customer revenue. The operator can spend the budget, fail to deliver or route payments elsewhere. Contracts are unaudited. Gross receipts are not profit.

Read the full risks

Before you back.

Is my funding a repayable deposit?

No. Activation releases the entire budget to the operator to spend. You receive a share of tokens reaching the campaign, not a guarantee of repayment. Backer positions cannot be transferred and have no early capital exit.

What if the campaign never launches?

A missed funding target enables refunds after the deadline. If fully funded, the operator has two days after the funding deadline to activate. Missing activation also enables refunds and a proportional bond claim where a bond exists.

Can the contract guarantee customer payments?

No. The operator controls the service and its payment routing. Customers must pay the campaign receiver for receipts to be shared. Direct transfers also count as receipts, so receipt totals alone do not prove demand.

Does the Stock Token bond insure my funding?

No. The bond follows activation and lock rules. Low revenue, poor service and misconduct are not automatically slashable. Its value and transferability can change.

Useful work needs
a starting point.

Explore the application

Review a campaign. Understand the risk. Decide for yourself.