Reliability infrastructure for x402 - verify paid services actually deliver. CA: 0x23Ec691cf7F9a3166fa663C73f6f5A0c26A5AbA3
Check before you call →
Joined December 2024
- Tweets48
- Following4
- Followers43
- Likes110
Pinned Tweet
CORTX is now public.
real payments. real delivery checks. real reliability data.
built for x402.
usecortx.dev
your x402 endpoint can be online and still fail after an agent pays.
that’s why we built @usecortx.
CORTX is now public.
CORTX retweeted
we found something interesting while testing payment readiness across live x402 services:
x402(dot)org is not a universal facilitator for every x402 service.
some services, like Bankr, specify their own facilitator in the 402 response.
if your implementation blindly defaults to x402(dot)org, a healthy service can return what looks like a payment failure simply because you routed the authorization to the wrong facilitator.
after fixing facilitator discovery:
5/6 services ready
~95ms avg verify latency
$0 USDC spent
we’ve now formalized the discovery algorithm in the CORTX x402 Reliability Spec v0.2.
built from testing live services on Base, not assumptions.
full write-up ↓
usecortx.dev/blog/x402-facil…
CORTX caught a payment_terms failure on Exa’s public x402 endpoint.
endpoint is online, but the payment flow fails before any USDC is spent.
@ExaAILabs might be worth checking on your end 👀
uptime ≠ payment reliability.
evidence ↓
CORTX retweeted
I’m about to sleep now.
$CRTX up +8.86%, not bad for but a lot of work still left to be done.
will drop a public letter today, explaining more about the product and why I think reliability in x402 endpoints are very important.
CA: 0x23ec691cf7f9a3166fa663c73f6f5a0c26a5aba3
base is back and tech will win
watching;
base:0xc52aedec3374422d7510e294cfaa90799595cba3 @AskSurplus
$DELU @deluquant
$aeon @aeonframework
base:0x7afe438411ee3959c7de6f7fb76bf9c769320ba3 @blocktronicsxyz
$CORTX @usecortx
why? Incredible tech is built on base with based founders.
btw we have 100% uptime on the points we track.
note we use USDC on @base for each check.
base is back and tech will win
watching;
base:0xc52aedec3374422d7510e294cfaa90799595cba3 @AskSurplus
$DELU @deluquant
$aeon @aeonframework
base:0x7afe438411ee3959c7de6f7fb76bf9c769320ba3 @blocktronicsxyz
$CORTX @usecortx
why? Incredible tech is built on base with based founders.
CORTX retweeted
$CORTX now has onchain utility.
hold $CORTX on Base → unlock more x402 monitoring:
Free → 2 endpoints
500K → 5
1M → 15
5M → 50
10M → unlimited
no staking. just hold.
CORTX runs real USDC checks through your payment flow and alerts you when something breaks.
CA: 0x23ec691cf7f9a3166fa663c73f6f5a0c26a5aba3
200 OK is not enough.
CORTX verifies the full x402 payment flow:
availability → payment → delivery → schema validation.
and now builders can expose that reliability publicly through badges, status pages, and the API.
real payments. real delivery. measurable reliability.
most API status badges tell you the server responded with a 200.
CORTX badge tells you the API accepted a payment and delivered.
shipped the full public reliability layer today:
- live reliability badge
- per-service public status page
- JSON reliability API
- 30-day paid delivery + uptime
- schema validity + median latency
- no auth required
for x402, uptime alone isn’t enough.
an endpoint can be online and still fail after taking payment.
we built the public layer so x402 builders can prove reliability, not just claim it.
We’re live.
Private beta open at usecortx.dev
Standard uptime checks will tell you your x402 endpoint is "up."
They won't tell you if the payment terms are malformed, if your price is out of range, or if the response schema broke in the last deploy.
@usecortx runs all 7 stages. 🧵