Growth is the first page of every service. It answers the question the rest of Forge works toward: are agents paying you more? It needs no setup and no SDK. Forge reads the wallets your 402 challenges ask agents to pay, and counts the x402 payments into them from onchain data. Because that history already exists, you get a baseline from before you joined Forge on day one.

​
Revenue

  • Since Forge: what agents have paid since you added the service, and the daily average.
  • Before Forge: the daily average over the 30 days before you joined. It’s your baseline.
  • Daily revenue: a chart of both, with a line where you joined Forge.
Once there are three full days since you joined, and your baseline is at least $10, Forge shows the change against your baseline.

​
Buyers

  • Agents that paid since you joined, and how many paid each day.
  • Who paid: returning agents, which have paid on more than one day, against new ones, which first paid after you joined.
  • Where revenue came from: the share paid by returning agents against agents that paid only once.
A buyer is a paying wallet. One agent can use several wallets, and several agents can share one.

​
How we measure

Select How we measure to see the wallets Forge reads.
  • Only x402 settlements count. Payments between your own wallets are left out.
  • USDC on Base and on Solana is counted today. On Solana, a payment counts when a facilitator paid the transaction fee, as x402 settles there. Wallets on other networks are listed as Coming soon. MPP payments on Tempo aren’t counted yet.
  • Wallets are taken from your live 402 challenges, so a new payTo address is picked up on the next scan.

​
Coming next

  • Selection rate: how often agents pick you for the tasks you serve.
  • Visitor to buyer: how many agents that reach your 402 go on to pay. This needs the Forge SDK, which sees agents that never pay.
Your Services page shows each service’s revenue over the last 30 days next to its Discovery score and health.