x402 reliability infrastructure

Your x402 service can be
online and still be broken.

CORTX makes controlled paid test calls and verifies payment terms, settlement, delivery and response schema — so you catch failures before users do, on a schedule you control.

Monitor a ServiceView Methodology
usecortx.dev/services/wallet-research
Wallet Research API
Degraded
x402.bankr.bot/research · checked 3m ago
✓
Availability
200 OK
✓
Payment terms
valid
✓
Price
0.001 USDC
✓
Payment
settled
✓
Delivery
received
✓
JSON parse
valid
✕
Schema
missing: result.summary
Incident #3 opened·Alert sent·Posted
Base mainnet
Real on-chain payments
Real USDC test calls
Not simulated — on-chain
7-stage verification
Full payment journey
Spending caps
Configurable budget limits
The problem

A successful HTTP response is not successful service delivery.

Your server can respond while the payment flow, returned JSON or expected schema is broken. Traditional monitoring does not check any of this.

Traditional monitoring
✓
Endpoint responded
200 OK
—
Payment terms valid
not checked
—
Price within range
not checked
—
Payment accepted
not checked
—
Result delivered
not checked
—
Schema valid
not checked
Service appears healthy. Users report broken results.
CORTX
✓
Endpoint responded
200 OK
✓
Payment terms valid
valid
✓
Price within range
0.001 USDC
✓
Payment accepted
settled
✓
Result delivered
valid JSON
✕
Schema valid
invalid
Degraded. Incident opened. Alert sent.
How it works

CORTX tests the service like a real customer.

Using a safe payload, dedicated testing wallet and strict spending limit, CORTX runs the complete paid request and records evidence at every stage.

01
Configure
Add your endpoint, a safe test payload, expected price range, and the JSON Schema for a valid response.
02
Pay
CORTX performs a real EIP-3009 USDC authorization from a dedicated synthetic wallet on Base mainnet, within your defined price cap.
03
Verify
Every stage is checked independently — payment terms, price, settlement, delivery, JSON validity, and schema conformance.
04
Alert
On repeated failure, CORTX opens an incident and notifies you via Telegram before your users notice.
Evidence

Stop guessing where the request failed.

See the exact payment terms, response body, schema errors and stage timings behind every incident. Evidence stored for every check run.

Summary
Payment
Response
Schema Diff
{
"http_status": 200,
"payment_status": "settled",
"observed_price_usdc": 0.001,
"response_json_valid": true,
"schema_valid": false,
"missing_fields": ["result.summary"],
"latency_ms": 4632
}
Safety

Real payments, controlled exposure.

Set the maximum price, test frequency and monthly budget. CORTX blocks calls when quoted terms exceed your policy.

Builder-defined price cap
CORTX blocks any call where the quoted price exceeds your maximum.
Dedicated synthetic wallet
Tests run from an isolated wallet, separate from any production funds.
Configurable interval
Choose how frequently CORTX tests your service, balancing cost and coverage.
Monthly spend cap
Set an absolute USDC budget for the month. Checks pause when it's reached.
Auto-blocked on price change
If quoted price changes unexpectedly, the call is blocked and an alert fires.
Public status pages

Turn reliability into public proof.

Share a public CORTX status page with users, agents and partners. Updated automatically after every check run.

usecortx.dev/status/bankr
Example
All systems operational
Updated 47s ago
Wallet Research API
Tested by CORTX · 90d
90 days agotoday
Market Data Feed
Tested by CORTX · 90d
90 days agotoday
View your status page →
Private beta · Bankr x402 on Base

Catch failures before your users do.

Monitor one Bankr x402 service in the CORTX private beta.

Monitor a Service

Currently supports Bankr-hosted x402 JSON APIs on Base mainnet.
Private beta. No token. No marketplace.