What the provider says
Paid JWT HS256 signature-timing sidechannel probe (cycle 152, x402 $0.001) - forges 32 HS256 JWTs varying the LAST signature byte, sends each (default 12 iterations) against target's Authorization: Bearer header, measures per-byte response timing via stdlib time.monotonic, detects non-constant-time HMAC verification (a classic JWT forgery primitive). Returns per_byte_stats {min_ms,max_ms,median_ms,mean_ms,stdev_ms,range_ms} + overall timing_uniformity_score 0-100 A-F + timing_leak_detected...
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
-
Not checked by us yet — the data is as the source published it
- 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/jwt-timing-sidechannel>",
"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/jwt-timing-sidechannel
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 |
Endpoint checks
We have not called this endpoint yet. Until we do, everything above is what the source
published — no more.
Tags