Verify your setup - Forge

The challenge

Inspect a paid route the way awal agents do:

npx awal x402 details "https://api.example.com/your/paid/route"

Check for the rating sentence at the end of description, and (on x402 v2) a forge-feedback: block under Extensions, after any bazaar: block. Or decode the header directly:

curl -s -D - -o /dev/null "https://api.example.com/your/paid/route" \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 -d

The OpenAPI document

curl -s https://api.example.com/openapi.json | jq '."x-forge-feedback", .paths["/feedback/rate"]'

With the agentcash MCP, discover_api_endpoints on your origin should list GET /feedback/rate as unprotected, and its guidance should end with the rating sentence.

The rating routes

curl -s https://api.example.com/feedback            # the form: allowed values and examples
curl -s https://api.example.com/feedback/summary    # public aggregate
curl -s "https://api.example.com/feedback/rate?feedback_id=AAAAAAAAAAAAAAAAAAAAAA&outcome=fully"
# → 404 unknown_or_expired_feedback_id, which means the route is wired and validating

A paid call

A real paid call needs a funded wallet. After one, the JSON response should have feedback_id, feedback_url and rate_this_call, and the header Forge-Feedback-Id. The call and any rating then show up on the Forge dashboard.

Diagnostics

forge.diagnostics() returns counters you can log or expose on a health route:

{ "minted": 12, "challengesDescribed": 40, "eventsSent": 52, "eventsDropped": 0, "openapi": { "enriched": true, "…": "…" } }