How Augur Payment Works

Augur uses x402 for per-call payment. The flow is HTTP-native: request the resource, receive payment requirements, sign the payment, retry the same request, receive JSON.

The 4-step flow

1. Request analysis
Call GET https://augurrisk.com/analyze?address=0x4200000000000000000000000000000000000006.
2. Receive a 402
Augur returns 402 Payment Required with a base64-encoded Payment-Required header describing the exact USDC payment on Base.
3. Sign and attach payment
Your x402 client signs the payment authorization from your wallet and retries the same request with a PAYMENT-SIGNATURE header.
4. Receive JSON
Augur verifies the payment with the facilitator, settles it, and returns the decision, recommended_policy, supporting findings, score, level, and proxy details if present.

What you do not need

What can fail before payment

If the address is missing, malformed, or has no bytecode on Base mainnet, Augur returns 422 before the x402 paywall. That prevents paying for EOAs or undeployed contracts.

First successful paid call

Use the Base WETH request below as the canonical integration check. It should produce HTTP 200 JSON with decision: "allow", level: "safe", and score: 0 after your x402 client retries with payment.

# First request
GET https://augurrisk.com/analyze?address=0x4200000000000000000000000000000000000006

# Retry after signing payment
GET https://augurrisk.com/analyze?address=0x4200000000000000000000000000000000000006
PAYMENT-SIGNATURE: <x402-payment-proof>

If the request is missing address, appends another path after the address, or uses a malformed address, Augur returns 422 before payment.

Integration references: