Send native x402 REST usage
Pay the send-native execution fee (native coin transfer)
Daily transfers, volume and coverage →
x402.nichospt.net · x402.nichospt.net · Other services
The provider publishes no description of this service. What follows is what the sources record, nothing more.
The payout address is also published by 21 other service(s); the volume cannot be attributed to one of them.
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-28) | — | — |
| Last 7 days | — | — |
| Last 30 days | — | — |
| Growth, 7d against the 7 before | not comparable | |
Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.
Receiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.
| Network | Full wallet address | Evidence |
|---|---|---|
| Polygon | 0x954c90740b8247e4b0d4a3f92201167895405555 | Shared address · activity cannot be assigned to this serviceFrom source record · source: payai |
No sending wallet addresses have been retained for this service. Buyer wallets are unknown; daily totals and reported payer counts do not reveal their addresses.
Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
| With a measured call count | 2,096 (13.5 %) |
|---|---|
| With a published price | 3,443 (22.2 %) |
| With attributable inflows | 91 (0.6 %) |
| Observed inflows · 30d | $115.94 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Pay the send-native execution fee (native coin transfer)
Chainlink For Agents: submit a signed operation payload.
Compute a SHA-256, SHA-384, or SHA-512 digest of UTF-8 text; returns hexadecimal output (default SHA-256).
Access the exclusive horror story collection (pay-per-read).
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.
| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Polygon | exact | 0.001 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 1000 = 0.001 USDC per call on Polygon.
endpoint
http://x402.nichospt.net/text-to-cron
The payout address is shared with 21 other service(s). That is normal for facilitator and platform addresses, and it is why this profile shows no inflow figure. The volume exists — it just cannot be split without inventing a rule.
How attribution works →91 of 15,505 services (0.6%) in Other services have attributable inflows; 2,096 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →The source record carries no description beyond the name. We did not write one for it.
Quoted from PayAI · source record · read 2026-10-29
Attribution blocked
· confidence low
The payout address is also published by 21 other service(s); the volume cannot be attributed to one of them.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is nothing measurable: no price, no attributable address, no receipt. The payout address is also published by 21 other service(s); the volume cannot be attributed to one of them.
No daily history has been archived for this service yet. Open the full daily history →
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
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 |
http://x402.nichospt.net/text-to-cron
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
facilitator.payai.network | 2026-10-27 |
| Payment | Provider claim |
1 rail: Polygon · payee 0x954c90740b8247e4b0d4a3f92201167895405555
EvidenceAus 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-27 |
| Pricing | Provider claim |
0.001 USDC per call
EvidenceAtomic amount 1000 = 0.001 USDC per call on Polygon. Netzwerk: Polygon. |
facilitator.payai.network | 2026-10-27 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
facilitator.payai.network | 2026-10-27 |
| Provider | Provider claim |
x402.nichospt.net
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
facilitator.payai.network | 2026-10-27 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.