What the provider says
Paid OCSP Must-Staple (RFC 7633) cert-feature detector (cycle 138, x402 $0.001) - opens TLS to target host, parses leaf cert via cryptography.x509 to detect status_request TLS Feature extension (OID 1.3.6.1.5.5.7.1.24) or status_request_v2 (OID 1.3.6.1.5.5.7.1.25); detects must-staple commitment at the certificate level; pairs with /api/ocsp-staple-verify (c128, responder reachability) for end-to-end OCSP coverage. CAVEAT: stdlib ssl cannot directly inspect TLS extension negotiation for...
Quoted from PayAI
· source record
· read 2026-10-26
Facts and where they come from
- Price
-
0 USDC per call
Provider claim
Recorded value: 0 USDC per call.
- Unit
- per call
- Protocol
-
x402, REST
· transport: HTTP
Provider claim
- Auth
- x402
- Source
-
PayAI
· Public discovery API (provider-published records)
- Last checked
-
Endpoint called 2026-10-26
- First seen
- 2026-10-26
Payments and earnings
Verified earnings · 30d
Unknown
Measured days
0/30
Settled payments
—
Ledger computed
never
No settled payment on record. Earnings for this service are unknown — not zero.
Payment rails
Base
· exact · USDC
0xCa0a6c6Aa7A8F0D5893636CF166Ea2b44fb6500c
0 USDC
From source record
A payment rail is where the provider asks to be paid. It is not proof that anything was paid
through it. See evidence levels.
Input and output, as published
Request
{
"type": "http",
"method": "GET"
}
Response
{
"type": "json",
"example": {
"data": "<structured JSON per /openapi.json spec for /api/ocsp-must-staple>",
"success": true
}
}
Examples are the provider's own, not a call we made.
Provenance
One row per statement. “Verified” means we checked it ourselves and the finding is quoted.
“Provider claim” means we read it in the provider's own record. “Not found” is a statement about
our search, not proof of absence.
| Statement |
Status |
What we found |
Source |
Checked |
|
Endpoint
|
Provider claim |
https://6xrkjcfa3yrzvefcpvanurzou4.srv.us/api/ocsp-must-staple
Evidence
Als Resource-URL im Bazaar-Eintrag geführt.
|
facilitator.payai.network
|
2026-10-26 |
|
Input output
|
Provider claim |
Request/response examples published with the listing
Evidence
Beispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters.
|
facilitator.payai.network
|
2026-10-26 |
|
Payment
|
Provider claim |
1 rail: Base · payee 0xCa0a6c6Aa7A8F0D5893636CF166Ea2b44fb6500c
Evidence
Aus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt.
|
facilitator.payai.network
|
2026-10-26 |
|
Pricing
|
Provider claim |
0 USDC per call
Evidence
Atomic amount 0 = 0 USDC per call on Base. Netzwerk: Base.
|
facilitator.payai.network
|
2026-10-26 |
|
Protocol
|
Provider claim |
x402 (HTTP 402 payment challenge)
Evidence
Im x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http).
|
facilitator.payai.network
|
2026-10-26 |
|
Provider
|
Provider claim |
6xrkjcfa3yrzvefcpvanurzou4.srv.us
Evidence
Die Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter.
|
facilitator.payai.network
|
2026-10-26 |
|
Reachability
|
Verified |
HTTP 402 · 761 ms
Evidence
Eigene Anfrage am 2026-10-26 um 00:30 UTC an https://6xrkjcfa3yrzvefcpvanurzou4.srv.us/api/ocsp-must-staple (GET, ohne Anmeldung, ohne Bezahlung). Antwort: HTTP 402 mit Zahlungsaufforderung.
|
6xrkjcfa3yrzvefcpvanurzou4.srv.us
|
2026-10-26 |
Endpoint checks
| When |
URL |
Answer |
Latency |
Payment challenge |
| 2026-10-26 |
https://6xrkjcfa3yrzvefcpvanurzou4.srv.us/api/... |
HTTP 402 · payment required
|
761 ms |
0.001 USDC
eip155:8453
|
We call the documented URL once, unauthenticated and without paying. We never retry a
payment challenge and never sign in.
Tags