# SafeGate CommerceProof Verification API > An independent verdict on evidence of a Base USDC payment. Paid per call over > x402. You are charged only when the verdict is VERIFIED. SafeGate is operated by Nurexen Labs. It verifies **evidence**, not delivery. ## What this service answers Given evidence of a payment, SafeGate answers one question: does the evidence hold up when checked independently? It reads the chain through two independent RPC providers and requires them to agree field by field before it says yes. ## What this service never claims **SafeGate does not verify delivery of goods or services.** That is not a limitation of the current version, it is the boundary of what this service is. On any input, SafeGate does **not** assert: - that goods or services were delivered - that the commercial transaction completed - that any party passed sanctions screening beyond what the response explicitly reports - the identity of any party The field `commerce_verified` is **always false**. This deployment does not sign its own responses: `signing_capability` is `NONE_BY_DESIGN` and the assurance ceiling is `OBSERVED`. If you need a signed attestation, this is not it, and we would rather tell you now than let you find out later. ## Endpoint ``` POST https://pay.safegatelabs.xyz/api/commerceproof/verify-paid Content-Type: application/json PAYMENT-SIGNATURE: ``` Call it without a payment header and you get `402` carrying the full payment requirements, including an `extensions.bazaar` block that describes both inputs. That call is free, so discovery costs you nothing. ## Payment | Field | Value | |---|---| | Scheme | `exact` (x402 v2) | | Network | `eip155:8453` (Base mainnet) | | Asset | `0x833589fcd6edb6e08f4c7c32d4f71b54bda02913` (USDC) | | Price | `50000` base units = **0.05 USDC** | | Pay to | `0x367f1b3d8ca90d1e087481a9a40d585bf3451a03` | | Facilitator | `https://x402-agent-pay.com/facilitator` | | Max timeout | 300 seconds | | Min remaining validity | 60 seconds | The `payTo` address is the **facilitator treasury**, not the service operator's own wallet. That separation is deliberate: the facilitator settles to the operator separately. Do not infer the operator's revenue address from `payTo`. Header precedence: `PAYMENT-SIGNATURE` wins. If both it and the legacy `X-PAYMENT` are present, `X-PAYMENT` is ignored, so an old header can never override the canonical one. ## Two inputs. Send exactly one. ### 1. `payment` — you only have a transaction hash ```json { "payment": { "transaction_hash": "0x7d10...4b7c" } } ``` The Base USDC transfer is read from two independent RPC providers and reported: sender, recipient, amount in base units and in USDC, block timestamp. If the transaction moved USDC more than once, **every** transfer is reported and `multiple_transfers` is set to true. SafeGate does not pick one for you. **No sanctions screening on this input.** The response says so in the field `sanctions_screening: "NOT_PERFORMED_IN_THIS_EVIDENCE_TYPE"`. ### 2. `proof` — you have a full SafeGate CommerceProof ```json { "proof": { "...": "a SafeGate CommerceProof object" } } ``` The full path: the proof is verified, the payment is confirmed on chain, the payee is screened against the sanctions manifest NSGoods publishes and signs, and the signer key is pinned to a published registry. Aliases accepted: `commerceproof` and `product` for `proof`, `base_payment` for `payment`. Send **both** and you get `400 AMBIGUOUS_INPUT`. SafeGate will not guess which one you meant. Send **neither** and you get `400 PROOF_REQUIRED`. Both errors list `accepted_inputs`. ## Verdicts | Verdict | Meaning | Charged | |---|---|---| | `VERIFIED` | Two or more independent RPC providers agreed field by field | **Yes** | | `FAILED` | The evidence is contradicted on chain | No | | `INDETERMINATE` | SafeGate could not establish the fact | No | `INDETERMINATE` is an honest answer, not an error. You get it when only one RPC provider answered (independence cannot be claimed from a single source), when the providers disagreed, when every provider was unreachable, or when a provider turned out not to be on Base. A `200` response does **not** mean `VERIFIED`. Read the `verdict` field. ## Charging Settlement is attempted **only** when the verdict is `VERIFIED`. `FAILED` and `INDETERMINATE` never reach settlement. `payment_status` is one of `CHARGED`, `NOT_CHARGED` or `UNKNOWN`; `UNKNOWN` means settlement state could not be established, and no automatic second charge is attempted. Recovery is durable. ## Limits Four quota dimensions, enforced together, lowest wins: 60 per wallet-minute, 500 per wallet-day, 500 per IP-day, 1000 global per day. Counted on payment-authorized calls, not only on `VERIFIED` verdicts. Request bodies above 1048576 bytes are rejected. Quota fails closed: if the quota backend is unreachable, the call is refused rather than served for free. ## Try it without paying Free route, no payment header, no x402: ``` POST https://verify.safegatelabs.xyz/api/commerceproof/verify-free ``` ## Machine-readable references - OpenAPI 3.1: https://pay.safegatelabs.xyz/openapi.json - Agent skill guide: https://pay.safegatelabs.xyz/skill.md - Health and configuration: https://pay.safegatelabs.xyz/api/health - Signer key registry: https://pay.safegatelabs.xyz/.well-known/safegate-keys.json - Live payment requirements: send an unpaid POST to the endpoint and read the `402` ## Proven in production A live funded x402 v2 settlement on Base mainnet completed on 18 November 2026: verdict `VERIFIED`, `payment_status: CHARGED`, on-chain settlement `SUCCESS`. The transaction is published in `GET /api/health` under `first_live_settlement` so you can verify it yourself rather than take our word for it. That record is a published historical fact, not a continuous health probe. ## Operator Nurexen Labs — https://safegatelabs.xyz Last updated: 2026-11-20