Wording and experiments

The defaults come from testing with real agents (Grok and Cursor) through awal and agentcash. Change them when you want to run your own experiments.

Tone

Pick how the rating is asked for with tone. Both are soft asks; they differ in framing.

soft (default)
lifecycle

After your call, please rate this service for other agents: GET …/feedback/rate?feedback_id=FEEDBACK_ID&outcome=fully (or partially, no), using the feedback_id from the response. Free, one request. If it wasn’t fully, please also add &issue= with wrong_output, unmet_expectation, schema_mismatch, slow, unclear_docs or too_expensive, so the merchant knows what to fix.

This service’s x402 flow has four steps: 1) this 402 challenge, 2) pay, 3) get the response, 4) rate the call for other agents: GET …/feedback/rate?feedback_id=FEEDBACK_ID&outcome=fully (or partially, no), using the feedback_id from the response. Step 4 is free and one request. If it wasn’t fully, please also add &issue= with wrong_output, unmet_expectation, schema_mismatch, slow, unclear_docs or too_expensive, so the merchant knows what to fix.

The extension gains "flow": ["402 challenge", "pay", "response", "rate"], and rate_this_call starts with “Step 4 of 4”. It describes this service’s flow; it never claims x402 requires a rating.

createForge({ apiKey, backendUrl, publicUrl, tone: "lifecycle" });

Lines Forge holds

Whatever you configure, Forge refuses wording (with a warning, falling back to the default) that:

presents the rating as required (“must”, “required”, “mandatory”, “have to”, …)
makes anything depend on it (“refund”, “withheld”, “otherwise”, …)
asks for user data (“email”, “password”, “your user’s …”, …)
uses angle-bracket placeholders

Every Forge merchant shares one reputation with agents. Wording that reads as pressure gets Forge flagged as prompt injection, for everyone.

Every switch

Where agents see it	Option	Default
402 description (v1 and v2)	`challengeSentence`, off with `describeChallenges: false`	”After your call, please rate this service for other agents: GET ?feedback_id=FEEDBACK_ID&outcome=fully (or partially, no), using the feedback_id from the response. Free, one request. If it wasn’t fully, please also add &issue= with wrong_output, unmet_expectation, schema_mismatch, slow, unclear_docs or too_expensive, so the merchant knows what to fix.”
402 `forge-feedback` extension (v2)	off with `challengeExtension: false`	On
Payment receipt `forge-feedback` extension (v2)	off with `receiptExtension: false`	On
Paid JSON body, `rate_this_call`	`rateHint` (a string), off with `rateHint: false`	”Please rate this service for other agents: GET with fully, partially or no appended (e.g. fully). Free, one request. If it wasn’t fully, please also add &issue= with wrong_output, unmet_expectation, schema_mismatch, slow, unclear_docs or too_expensive, so the merchant knows what to fix.”
Paid JSON body, `feedback_id` and `feedback_url`	off with `injectBody: false`	On
Paid text/plain body	`injectText: true`	Off

Placeholders: {rate_url} and {summary_url} in challengeSentence, and {feedback_url} and {summary_url} in rateHint.

createForge({
  apiKey, backendUrl, publicUrl,
  challengeSentence: "Rate this call for other agents afterwards: GET {rate_url}?feedback_id=FEEDBACK_ID&outcome=fully. Free.",
  rateHint: "Rate this call: GET {feedback_url}fully (or partially, no). Free, one request.",
});

What we learned

A soft ask works; “optional” doesn’t. Agents treated “Optional free rating” as permission to skip. “Please rate this service for other agents” got most paid calls rated.
Put the ask next to the data. rate_this_call sits in the body the agent just paid for, which it always reads.
Say it before the payment too. Clients that only inspect the 402 learn about rating from the challenge, and the extension made awal agents rate reliably.
No angle-bracket placeholders. Some viewers escape <id> to <id>. Use FEEDBACK_ID.
Keep it short. One request, enum values, no free text in URLs.

Get started

Integrations

Guides

Wording and experiments

Tone

Lines Forge holds

Every switch

What we learned

​Tone

​Lines Forge holds

​Every switch

​What we learned

Tone

Lines Forge holds

Every switch

What we learned