Events x402 REST usage
Query Ethereum contract event logs via eth_getLogs - filter by contract, topic, and block range
Daily transfers, volume and coverage →
api.compatify.io · api.compatify.io · Infrastructure
Will these two products work together, asked in plain language? Reads the device and the accessory out of a free-text question and resolves both against the catalogue. Returns the verdict with confidence, source, last-verified date and the products it read out of the question. Call when the user's q
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-30) | $0.00 | 0 |
| Last 7 days | $0.00 | 0 |
| Last 30 days | $0.00 | 0 |
| 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 |
|---|---|---|
| Base | 0x13273fe5cfee0c289ee30dac40ea58d4fb823c36 | Exclusive to this catalogue serviceFrom source record · source: x402_bazaar |
All 1 retained sending addresses are listed below. Source: on-chain transfer scans. Dates are UTC days.
| Network | Full wallet address | Transfers | First / last observed | Last scanned (UTC) |
|---|---|---|---|---|
| Base | 0x3d0ae0b0c76aba656128c550d81d6031501fafb4 | 4 | 2026-10-31 / 2026-10-31 | 2026-10-31 21:46:55 |
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 | 972 (16.0 %) |
|---|---|
| With a published price | 1,116 (18.4 %) |
| With attributable inflows | 19 (0.3 %) |
| Observed inflows · 30d | $63.56 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Query Ethereum contract event logs via eth_getLogs - filter by contract, topic, and block range
Check if a URL is up: status, latency, redirects, title.
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...
Get a client token for direct upload to Vercel Blob
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 |
|---|---|---|---|
| Base | exact | 0.05 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 50000 = 0.05 USDC per call on Base.
endpoint
https://api.compatify.io/v1/query
{
"body": {
"query": "Does the Apple silicone case fit the iPhone 17 Pro?"
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
{
"example": {
"answered_at": "2026-10-28T12:00:00Z",
"available_categories": null,
"canonical_accessory_id": "apple_silicone_case_iphone_17_pro",
"canonical_device_id": "apple_iphone_17_pro",
"compatibility_notes": null,
"compatible": true,
"confidence": 0.75,
"data_category": "phone_cases",
"extraction_confidence": 0.9,
"freshness_reason": null,
"freshness_status": "never_verified",
"last_verified_at": null,
"message": null,
"notes": "Device model is on the accessory's manufacturer fitment list.",
"parsed_accessory": "Apple silicone case",
"parsed_device": "iPhone 17 Pro",
"query_intent": "compatibility_check",
"source": "Apple",
"source_method": "rule_engine",
"source_tier": "manufacturer_spec",
"source_type": "rule_engine",
"source_url": "https://www.apple.com/shop/buy-iphone/iphone-17-pro/silicone-case-with-magsafe",
"under_review": false,
"under_review_reason": null,
"verified_at": "2026-10-28T12:00:00Z"
},
"type": "json"
}
Examples are the provider's own, not a call we made.
A price is published and the source counted 1 calls, yet no transfer reached the payout address in the last 30 days (the address is scanned daily). Either the buyers pay elsewhere, the volume is below one cent, or the endpoint is dormant. Only 19 of 6058 services in this category have attributable inflows at all.
Services here that do show inflows →19 of 6,058 services (0.3%) in Infrastructure have attributable inflows; 972 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →Will these two products work together, asked in plain language? Reads the device and the accessory out of a free-text question and resolves both against the catalogue. Returns the verdict with confidence, source, last-verified date and the products it read out of the question. Call when the user's question names the products in prose rather than by identifier.
Quoted from x402 Bazaar · source record · read 2026-10-31
Price published
· confidence low
The provider publishes a price. Nothing has been observed arriving at a payout address, and no receipt is on record.
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 $0.00 arriving at the payout address in 30 days — that is volume, and a lower bound: transfers can be refunds, treasury moves, or payments for something else entirely.
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 |
https://api.compatify.io/v1/printer-compatibility
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-31 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-10-31 |
| Payment | Provider claim |
1 rail: Base · payee 0x13273fE5CfEe0C289EE30DAC40ea58D4Fb823c36
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. |
api.cdp.coinbase.com | 2026-10-31 |
| Pricing | Provider claim |
0.05 USDC per call
EvidenceAtomic amount 50000 = 0.05 USDC per call on Base. Netzwerk: Base. |
api.cdp.coinbase.com | 2026-10-31 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-10-31 |
| Provider | Provider claim |
api.compatify.io
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-31 |
| Usage | Verified |
1 calls / 1 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-31. Letzter Aufruf laut Quelle: 2026-10-31T14:27:11.332Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-31 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.