Events x402 REST usage
Query Ethereum contract event logs via eth_getLogs - filter by contract, topic, and block range
0.005 USDC per call
per call
← All services
Daily transfers, volume and coverage →
Catalog
x402 resource x402 RESTexactgate-x402.insertnameheree.chatgpt.site · exactgate-x402.insertnameheree.chatgpt.site · Infrastructure
not indexed
Provider site ↗
Free ExactGate integration catalog with paid Base diagnostic routes, prices, and request examples.
Price per call
0 USDC per call
published unit: per call
Calls · 30d
—
not reported by any source
Payers · 30d
—
not reported by any source
Observed inflows · 30d
—
not attributable
Inflow growth · 7d
—
not comparable (baseline under $1 or window incomplete)
Payment evidence
Attribution blocked
confidence: low
· read 2026-10-29
Observed inflows · last 30 days
No inflow observed in this window
The payout address is also published by 1 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.
Blockchain wallets
Full addresses · public payment evidenceReceiving 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.
Receiving wallets · provider payment addresses
| Network | Full wallet address | Evidence |
|---|---|---|
| Base | 0xc7926ebcb4c89933a87739030e02bbe6be26b01c | Shared address · activity cannot be assigned to this serviceFrom source record · source: payai |
Sending wallets · observed counterparties
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.
Competitors & category benchmark
Rank the whole category →
Closest competitors
Infrastructure
- Events 209 calls · 0.005 USDC per call —
- Agent Web Tools 65 calls · 0.001 USDC per call $0.227
- Pulse 63 calls · 0.003 USDC per call —
- StableStudio 58 calls · 0.01 USDC per call —
- neo timestamp 57 calls · 0.01 USDC per call —
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.
Category benchmark
6,005 services in this category
| With a measured call count | 944 (15.7 %) |
|---|---|
| With a published price | 1,083 (18.0 %) |
| With attributable inflows | 19 (0.3 %) |
| Observed inflows · 30d | $66.56 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Similar services
All of Infrastructure →Agent Web Tools x402 REST usage
Check if a URL is up: status, latency, redirects, title.
0.001 USDC per call
per call
Pulse x402 REST usage
China pulse, cheap enough to POLL: what China is talking about RIGHT NOW and what is NEW since your last call - built for agents that monitor continuously. Returns `consensus` (phrases trending on 2+ of Weibo/Baidu/Douyi...
0.003 USDC per call
per call
StableStudio x402 REST usage
Get a client token for direct upload to Vercel Blob
0.01 USDC per call
per call
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.
Service details, payment routes and source evidence
Where you can pay
1 route from the provider's payment requirements| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Base | exact | 0 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 0 = 0 USDC per call on Base.
What you can call
access: payment per call (x402)endpoint
https://exactgate-x402.insertnameheree.chatgpt.site/v1/catalog
Opportunity insights
2 findings from measured data-
Payment attribution is blocked
The payout address is shared with 1 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 → -
Category benchmark
19 of 6,005 services (0.3%) in Infrastructure have attributable inflows; 944 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →
What the provider says
Free ExactGate integration catalog with paid Base diagnostic routes, prices, and request examples.
Quoted from PayAI · source record · read 2026-10-29
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
Money, and what it actually proves
Verified revenue · 30d
Unknown
Observed inflows · 30d
—
Attribution
Shared
Receipt ledger
Not connected
Attribution blocked
· confidence low
The payout address is also published by 1 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 1 other service(s); the volume cannot be attributed to one of them.
Daily market statistics — the ledger view, day by day
No daily history has been archived for this service yet. Open the full daily history →
Payment rails
Base
· exact · USDC
0xc7926ebCb4c89933A87739030e02BBE6bE26B01C
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.
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://exactgate-x402.insertnameheree.chatgpt.site/v1/catalog
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
facilitator.payai.network | 2026-10-29 |
| Payment | Provider claim |
1 rail: Base · payee 0xc7926ebCb4c89933A87739030e02BBE6bE26B01C
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-29 |
| Pricing | Provider claim |
0 USDC per call
EvidenceAtomic amount 0 = 0 USDC per call on Base. Netzwerk: Base. |
facilitator.payai.network | 2026-10-29 |
| 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-29 |
| Provider | Provider claim |
exactgate-x402.insertnameheree.chatgpt.site
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
facilitator.payai.network | 2026-10-29 |
Endpoint checks
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.