MARKET MONITOR / CATALOGUE Services 131,523 MCP listed 40,662 x402 90,934 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-30 · 3 sources
← All services

Daily transfers, volume and coverage →

ghtrend

x402 resource x402 REST

x402-ghtrend.shablony-pro.workers.dev · x402-ghtrend.shablony-pro.workers.dev · Dev & Code

not indexed Provider site ↗

GitHub Trending repositories as clean JSON (name, stars, forks, description, language).

Price per call 0.003 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.

Observed inflows by window for ghtrend.
Window Observed Transfers
Last complete day (2026-10-29) — —
Last 7 days — —
Last 30 days — —
Growth, 7d against the 7 before not comparable
Source: on-chain transfer scan (USDC on Base) Window: 2026-09-30 → 2026-10-29 Scanned: 30/30 days Sample: 0 days with a measurement First seen: never Last update: 2026-10-29

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 ghtrend.
NetworkFull wallet addressEvidence
Base 0x5a8dbd4788584f9c4b59eb64087a1a18fc2f7952 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 Dev & Code

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 3,166 services in this category
With a measured call count 911 (28.8 %)
With a published price 1,115 (35.2 %)
With attributable inflows 28 (0.9 %)
Observed inflows · 30d $134.26
Median measured calls 2
Median price per call $0.01

Similar services

All of Dev & Code →

GitHub Repo & User Data x402 REST usage

GitHub data. Repository stats, user profiles, and code-search results (stars, forks, language, topics, issues) via the GitHub REST API.

api.kadec0.xyz Dev & Code 126 calls / 30d checked 2026-10-30
0.02 USDC per call per call

Read contract x402 REST usage

Call a read-only (view/pure) function on any deployed contract via eth_call and get the decoded result. Give the contract address and a human-readable signature (e.g. 'balanceOf(address) view returns (uint256)') plus arg...

chain.openverbs.com Dev & Code 72 calls / 30d checked 2026-10-30
0.006 USDC per call per call

VIN decoder (NHTSA) x402 REST usage

Decode a vehicle VIN via the US NHTSA vPIC database: make, model, year, trim, body class, engine, fuel type, plant and vehicle type. Accepts full or partial VINs. Use it when an agent holds a VIN and needs the vehicle's...

agent402.tools Dev & Code 67 calls / 30d checked 2026-10-30
0.004 USDC per call per call

Decode x402 REST usage

Normalized NHTSA vPIC VIN decode (?vin=) — make/model/year/engine/body/… with fetch provenance, plus ORIGINAL factory new-vehicle warranty terms (basic/powertrain/corrosion/roadside/EV battery) keyed off make + model-yea...

api.vindexapi.dev Dev & Code 65 calls / 30d checked 2026-10-30
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
Payment networks and amounts published for ghtrend.
Network Scheme Amount Asset
Base exact 0.003 USDC

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

What you can call

access: payment per call (x402)

endpoint https://x402-ghtrend.shablony-pro.workers.dev/trend

Request

{
    "type": "http",
    "method": "GET",
    "queryParams": {
        "schema": {
            "queryParams": {
                "type": "object",
                "properties": {
                    "lang": {
                        "type": "string",
                        "required": false,
                        "description": "Programming language filter (e.g. python, rust). Empty = all"
                    },
                    "since": {
                        "type": "string",
                        "required": false,
                        "description": "daily|weekly|monthly (default daily)"
                    }
                }
            }
        }
    }
}

Response

{
    "type": "json",
    "example": []
}

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

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

    28 of 3,166 services (0.9%) in Dev & Code have attributable inflows; 911 have a source-measured call count. Median measured calls: 2.

    Rank this category by observed inflows →

What the provider says

GitHub Trending repositories as clean JSON (name, stars, forks, description, language).

Quoted from PayAI · source record · read 2026-10-29


Facts and where they come from

Price
0.003 USDC per call Provider claim
Recorded value: 0.003 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
0x5a8DbD4788584f9C4B59eB64087a1A18fc2f7952
0.003 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://x402-ghtrend.shablony-pro.workers.dev/trend
Evidence

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

facilitator.payai.network 2026-10-29
Input output Provider claim
Request/response examples published with the listing
Evidence

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

facilitator.payai.network 2026-10-29
Payment Provider claim
1 rail: Base · payee 0x5a8DbD4788584f9C4B59eB64087a1A18fc2f7952
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.

facilitator.payai.network 2026-10-29
Pricing Provider claim
0.003 USDC per call
Evidence

Atomic amount 3000 = 0.003 USDC per call on Base. Netzwerk: Base.

facilitator.payai.network 2026-10-29
Protocol Provider claim
x402 (HTTP 402 payment challenge)
Evidence

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

facilitator.payai.network 2026-10-29
Provider Provider claim
x402-ghtrend.shablony-pro.workers.dev
Evidence

Die 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.

Tags