MARKET MONITOR / CATALOGUE Services 133,130 MCP listed 40,873 x402 92,339 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-31 · 3 sources
← All services

Daily transfers, volume and coverage →

ParseAPI

x402 resource x402 REST

parseapi.info · parseapi.info · Knowledge & Memory

not indexed Provider site ↗

Recall tenant memory

Price per call 0.002 USDC per call published unit: per call
Calls · 30d 11 counted by the source, no daily split
Payers · 30d 8 distinct paying addresses seen by the source
Observed inflows · 30d $6.89 59 transfers to the payout address
Inflow growth · 7d −99.3% payout inflows, last 7 days vs the 7 before
Payment evidence Observed transfers confidence: medium · read 2026-10-27

Observed inflows · last 30 days

$4.11USD observed / day
2026-10-01grey = not scanned · UTC days2026-10-30
Observed inflows by window for ParseAPI.
Window Observed Transfers
Last complete day (2026-10-30) $0.00 0
Last 7 days $0.028 12
Last 30 days $6.89 59
Growth, 7d against the 7 before −99.3%
Source: on-chain transfer scan (USDC on Base) Window: 2026-10-01 → 2026-10-30 Scanned: 30/30 days Sample: 30 days with a measurement First seen: 2026-10-01 Last update: 2026-10-30

Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.

Blockchain wallets

Full addresses · public payment evidence

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.

Receiving wallets · provider payment addresses

All published receiving wallet addresses for ParseAPI.
NetworkFull wallet addressEvidence
Base 0x9952522e50c9ce639254939153595142b2024c2e Exclusive to this catalogue serviceFrom source record · source: x402_bazaar

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 Knowledge & Memory

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 1,339 services in this category
With a measured call count 437 (32.6 %)
With a published price 459 (34.3 %)
With attributable inflows 2 (0.1 %)
Observed inflows · 30d $6.95
Median measured calls 2
Median price per call $0.01

Relaystation Screening x402 REST usage

$0.01/screen. Screen any name against OFAC, EU, and UK sanctions (UN included) plus Wikidata-derived PEP watchlists — fuzzy matching, instant JSON verdict. Compliance in one call, one of 155 Relaystation tools on one bal...

api.relaystation.ai Knowledge & Memory 63 calls / 30d checked 2026-10-31
0.01 USDC per call per call

Reply x402 REST usage

Send a reply in an existing LinkedIn conversation through a human-connected account that granted `reply`. Flat price per message. Requires an Idempotency-Key header. Per-account daily cap (default 50) shared across all c...

win.oneshotagent.com Knowledge & Memory 33 calls / 30d checked 2026-10-31
0.02 USDC per call per call

Farcaster recall x402 REST usage

M2M memory recall: semantic search over graph_memory + farcaster_graph. Input query + fid. Output facts. Pay-per-call $0.01 USDC Base

x402.billionaireorder.com Knowledge & Memory 26 calls / 30d checked 2026-10-27
0.01 USDC per call per call

Product recalls x402 REST usage

List the US recalls of consumer products, food, drugs or medical devices that match a product name, a manufacturer or, for consumer products, a recall title.

win.oneshotagent.com Knowledge & Memory 16 calls / 30d checked 2026-10-28
0.005 USDC per call per call checked

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
Payment networks and amounts published for ParseAPI.
Network Scheme Amount Asset
Base exact 0.004 USDC

“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 2000 = 0.002 USDC per call on Base.

What you can call

access: payment per call (x402)

endpoint https://parseapi.info/memory

Request

{
    "method": "GET",
    "queryParams": [],
    "type": "http"
}

Response

{
    "example": {
        "authed": true,
        "items": [
            {
                "confirmations": 3,
                "created_at": "2026-01-01T00:00:00Z",
                "doc_kind": "invoice_like",
                "id": "c0ffee"
            }
        ],
        "ok": true,
        "tenant": "acme"
    },
    "type": "json"
}

Examples are the provider's own, not a call we made.

Opportunity insights

2 findings from measured data
  • Call count and inflow disagree

    The observed inflow implies about 3,444 calls at list price; the source counted 11 (factor 313). Either the effective price differs from the list price, or part of the volume belongs to other payers on the same address. Do not read the inflow as this service's revenue.

    Peers with attributed inflows →
  • Category benchmark

    2 of 1,339 services (0.1%) in Knowledge & Memory have attributable inflows; 437 have a source-measured call count. Median measured calls: 2.

    Rank this category by observed inflows →

What the provider says

Recall tenant memory

Quoted from x402 Bazaar · source record · read 2026-10-27


Facts and where they come from

Price
0.002 USDC per call Provider claim
Recorded value: 0.004 USDC per call.
Unit
per call
Protocol
x402, REST · transport: HTTP Provider claim
Auth
x402
Source
x402 Bazaar (Coinbase CDP) · 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-24
Usage
11 calls · 8 unique payers in the 30 days before 2026-10-25. Measured by the x402 Bazaar, not by us and not by the provider.

Money, and what it actually proves

Verified revenue · 30d Unknown
Observed inflows · 30d $6.89
Attribution Exclusive
Receipt ledger Not connected

Observed transfers · confidence medium
Token transfers reached this service's own payout address. A transfer is not a purchase, and shared, refunded or unrelated transfers cannot be excluded.

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 $6.89 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.

Cross-check. At the published price the observed inflow would cover about 3,444 calls; the source counted 11. Two independent measurements of the same question — they never match exactly, because the effective price differs per call size and the address can also receive unrelated transfers.

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
0x9952522E50C9cE639254939153595142b2024c2E
0.004 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://parseapi.info/parse/image
Evidence

Als Resource-URL im Bazaar-Eintrag geführt.

api.cdp.coinbase.com 2026-10-27
Input output Provider claim
Request/response examples published with the listing
Evidence

Beispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters.

api.cdp.coinbase.com 2026-10-27
Payment Provider claim
1 rail: Base · payee 0x9952522E50C9cE639254939153595142b2024c2E
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.

api.cdp.coinbase.com 2026-10-27
Pricing Provider claim
0.004 USDC per call
Evidence

Atomic amount 4000 = 0.004 USDC per call on Base. Netzwerk: Base.

api.cdp.coinbase.com 2026-10-27
Protocol Provider claim
x402 (HTTP 402 payment challenge)
Evidence

Im x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http).

api.cdp.coinbase.com 2026-10-27
Provider Provider claim
parseapi.info
Evidence

Die Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter.

api.cdp.coinbase.com 2026-10-27
Usage Verified
6 calls / 3 unique payers in the last 30 days
Evidence

Source-reported usage from Coinbase x402 Bazaar, read on 2026-10-27. Letzter Aufruf laut Quelle: 2026-10-25T11:41:52.804Z. Aufrufe sind kein Umsatz.

api.cdp.coinbase.com 2026-10-27

Endpoint checks

We have not called this endpoint yet. Until we do, everything above is what the source published — no more.

Tags