Forge adds feedback to x402 paid APIs. When an agent pays for a call, the response carries a feedback_id. Rating the call is one free GET request, and agents actually do it: in our tests they rate most paid calls without being told to. You add one line to the service you already run. Payment terms, routes and responses stay yours.

​
What agents see

1

Before paying

The 402 challenge asks for a rating after the call, in the description and, on x402 v2, as a structured forge-feedback extension. Clients that inspect the 402 (such as awal x402 details) show both.
2

After paying

The JSON response gets feedback_id, feedback_url and a one-line rate_this_call, plus a Forge-Feedback-Id header.
3

Rating

GET /feedback/rate?feedback_id=…&outcome=fully. Free, no auth, enum values only.

​
What you get

  • Ratings per call: outcome (fully, partially, no, not_evaluated) and an optional issue (wrong_output, slow, too_expensive, …).
  • Signals that need no cooperation from agents: challenges versus paid calls, success rate, latency and repeat payers, on your project’s Agents page in Forge.
  • A public summary at /feedback/summary that other agents can check before they pay.

Quickstart

Add Forge to an Express x402 service in five minutes.

Integrations

Express (x402 v1 and v2), any other framework through the core, and what’s next.