Daily transfers, volume and coverage →
api.blackforge.so · api.blackforge.so · Data & Finance
BlackForge crypto market data from the major spot exchanges: every column, 1-minute to daily buckets, 90-day lookback. Covers 100 billable rows; finer buckets and premium columns count as more than one row each.
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-31) | $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 |
|---|---|---|
| Polygon | 0x9723b022cebb47ba2af605144ef0b2cd8d85d832 | Exclusive to this catalogue serviceFrom source record · source: x402_bazaar |
| Arbitrum | 0x9723b022cebb47ba2af605144ef0b2cd8d85d832 | Exclusive to this catalogue serviceFrom source record · source: x402_bazaar |
| Base | 0x9723b022cebb47ba2af605144ef0b2cd8d85d832 | Exclusive to this catalogue serviceFrom source record · source: x402_bazaar |
All 6 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 | 0x73cc9400bd9f086d7427d3421d79195a68bb1ea4 | 1 | 2026-10-31 / 2026-10-31 | 2026-11-01 03:37:25 |
| Base | 0x8ec901f7e2710163387d70950f680f1ea2269d15 | 2 | 2026-10-31 / 2026-10-31 | 2026-11-01 03:37:25 |
| Base | 0xa1d1c0cf717402ff3651aa4873ccf96410b01978 | 1 | 2026-10-31 / 2026-10-31 | 2026-11-01 03:37:25 |
| Base | 0xaa34bd941511cc82a19878e2efbe0bd7077e1db3 | 2 | 2026-10-31 / 2026-10-31 | 2026-11-01 03:37:25 |
| Base | 0xc9c7b38c0942914fc8ea12063bc92dcd3b581670 | 1 | 2026-10-31 / 2026-10-31 | 2026-11-01 03:37:25 |
| Base | 0xf1f15ab1b66377d6d60b8938a737122551be57f9 | 1 | 2026-10-30 / 2026-10-30 | 2026-10-31 23:38:42 |
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 | 4,194 (63.2 %) |
|---|---|
| With a published price | 4,738 (71.4 %) |
| With attributable inflows | 129 (1.9 %) |
| Observed inflows · 30d | $167,760.93 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Send a Base token contract address, get an AI-written verdict: onchain metrics, a plain-language take, and a shareable verdict card. Entertainment, not trading advice.
Get SmartMoney trading activities on token (sorted by time descending)
Pay the send-token execution fee (ERC-20 transfer)
Get KOL trading activities on token (sorted by time descending)
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 |
|---|---|---|---|
| Arbitrum | exact | 0.005 | USDC |
| Base | exact | 0.005 | USDC |
| Polygon | exact | 0.005 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 5000 = 0.005 USDC per call on Base. 3 payment options published.
endpoint
https://api.blackforge.so/v1/series
{
"method": "GET",
"queryParams": {
"exchange": "binance",
"from": "2026-10-28T00:00:00Z",
"interval": "1h",
"metric": "downDepth5",
"symbol": "BTCUSDT",
"to": "2026-10-28T03:00:00Z"
},
"type": "http"
}
{
"example": {
"exchange": "binance",
"metric": "downDepth5",
"points": [
{
"quality": 0,
"qualityAll": 0,
"ts": 1793145600000,
"value": 47120334.1
},
{
"quality": 0,
"qualityAll": 0,
"ts": 1793149200000,
"value": 48211034.2
},
{
"quality": 0,
"qualityAll": 0,
"ts": 1793152800000,
"value": 46988120.7
}
],
"symbol": "BTCUSDT"
},
"type": "json"
}
Examples are the provider's own, not a call we made.
A price is published and the source counted 8 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 129 of 6638 services in this category have attributable inflows at all.
Services here that do show inflows →129 of 6,638 services (1.9%) in Data & Finance have attributable inflows; 4,194 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →BlackForge crypto market data from the major spot exchanges: every column, 1-minute to daily buckets, 90-day lookback. Covers 100 billable rows; finer buckets and premium columns count as more than one row each.
Quoted from x402 Bazaar · source record · read 2026-11-01
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.blackforge.so/v1/latest
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-11-01 |
| 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-11-01 |
| Payment | Provider claim |
3 rails: Base, Arbitrum, Polygon · payee 0x9723b022cebb47bA2af605144EF0B2cD8D85d832
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-11-01 |
| Pricing | Provider claim |
0.005 USDC per call
EvidenceAtomic amount 5000 = 0.005 USDC per call on Base. 3 payment options published. Netzwerk: Base, Arbitrum, Polygon. |
api.cdp.coinbase.com | 2026-11-01 |
| 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-11-01 |
| Provider | Provider claim |
api.blackforge.so
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-11-01 |
| Usage | Verified |
2 calls / 2 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-11-01. Letzter Aufruf laut Quelle: 2026-10-30T09:55:41.69Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-11-01 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.