MARKET MONITOR / CATALOGUE Services 131,105 MCP listed 40,658 x402 90,514 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-29 · 3 sources
← All services

Daily transfers, volume and coverage →

ChainWard hire check

x402 resource x402 REST

api.chainward.ai · api.chainward.ai · Crypto & Payments

Hired by others, hired by its own circle, or not enough data, for an ERC-8004 agent on BNB Chain under Set and Earn's rule of 3 hires from wallets you neither own nor fund: every wallet that hired it in the last 30 days (TermiX escrow and the shared ERC-8183 contract), and whether each is the owner,

Price per call 0.1 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

Where you can pay

1 route from the provider's payment requirements
Payment networks and amounts published for ChainWard hire check.
Network Scheme Amount Asset
Base exact 0.1 USDC

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

What you can call

access: payment per call (x402)

endpoint https://api.chainward.ai/api/risk/hires

Request

{
    "type": "http",
    "method": "GET",
    "queryParams": {
        "agent": "332962",
        "chain": "bsc"
    }
}

Response

{
    "type": "json",
    "example": {
        "data": {
            "as_of": {
                "time": "2026-10-06T01:09:22.000Z",
                "block": 125969567
            },
            "chain": "bsc",
            "hires": {
                "total": 3,
                "by_source": {
                    "termix_escrow": 3,
                    "erc8183_shared": 0
                },
                "distinct_hirers": 2
            },
            "owner": "0x15d08640aeefbdce11930d9c9a30884011f654f6",
            "hirers": [
                {
                    "path": [
                        "0x4e276b4db12447254134b45e5add170993df5ad2",
                        "0x1d21aa41a77737e593b8ca92d6bf6437fa81697f",
                        "0x8894e0a0c962cb723c1976a4421c95949be2d4e3"
                    ],
                    "hires": 1,
                    "address": "0x4e276b4db12447254134b45e5add170993df5ad2",
                    "verdict": "inconclusive",
                    "evidence": "The hirer's first-incoming-BNB trail stops at 0x8894e0a0c962cb723c1976a4421c95949be2d4e3, a hub (exchange-style wallet, router or custodian), after 2 hops; funding behind it is not visible.",
                    "first_hire_at": "2026-10-01T07:42:05.000Z"
                },
                {
                    "path": [
                        "0x99f88c4cae19f858052236f808b75967eece5bd0",
                        "0x0fe05614b2d344fb0ef9797431890d4c13c0f0f1",
                        "0x15d08640aeefbdce11930d9c9a30884011f654f6"
                    ],
                    "hires": 2,
                    "address": "0x99f88c4cae19f858052236f808b75967eece5bd0",
                    "verdict": "shared_funder",
                    "evidence": "The hirer's and the owner wallet's funding trails meet at 0x0fe05614b2d344fb0ef9797431890d4c13c0f0f1, which is not a hub or a contract (hirer: 1 hop up its first-incoming-stablecoin trail; owner wallet: 1 hop up its first-incoming-stablecoin trail).",
                    "first_hire_at": "2026-10-03T07:19:06.000Z"
                }
            ],
            "limits": [
                "independent_within_limits means no link was found within these limits; it is not proven independence.",
                "Only each wallet's first incoming BNB and first incoming stablecoin are followed, up to 4 hops. Later funding, and transfers between hirer and owner after that, are not checked.",
                "BNB moved by contract-internal calls is not visible to the trail (top-level transfers only).",
                "Trails stop at hubs and contracts and count as no link found: who funded a wallet through an exchange is not visible, so an owner who withdrew from their own exchange account to a hirer is not detected.",
                "Pairwise only: wallets that hire each other inside a closed group can each look unlinked pair by pair (chainward.ai/decodes/set-and-earn-week-one).",
                "Counts hire events (OrderCreated, JobCreated), not completed hires, and does not check which marketplace a hire came from. Hires on other contracts or on BSC testnet are not counted.",
                "Owner and agent wallet are read at the as_of block. For an owner address, its agents are the registry tokens transferred to it in the last 60 days that it still owns.",
                "At most 20 hirers are traced per check, in order of first hire.",
                "Describes where money moved, not who controls a wallet or why. Not a verdict on the agent or its builder."
            ],
            "method": "Hires are TermiX escrow OrderCreated events naming the agent as provider and shared ERC-8183 JobCreated events naming the owner or agent wallet as provider, on BNB Chain, in a 30-day hire window that starts no earlier than Set and Earn's first block. For each distinct hirer the check follows its first incoming BNB and first incoming stablecoin (USDT, USDC) back to their senders, up to 4 hops, and does the same for the owner and the agent wallet. owner: the hirer is the owner or the agent wallet. owner_funded: the owner or agent wallet is in the hirer's trail. direct_transfer: the hirer and the owner or agent wallet sent each other BNB or a stablecoin at any time, in either direction. shared_funder: the hirer's trail and the owner's (or agent wallet's) trail meet at a wallet that is not a hub or a contract, or the hirer is in the owner's trail. Trails stop at hubs (1,000+ incoming stablecoin transfers of at least $0.01 in 30 days, or 100,000+ sent transactions) and at contracts. inconclusive: the hirer's and the owner's (or agent wallet's) same-kind trails end at the same hub with first funding under 24 hours apart, or no incoming BNB or stablecoin is visible. independent_within_limits: none of these, including trails that end at a hub or a contract (the decode's \"no link found\").",
            "summary": {
                "inconclusive": 1,
                "owner_linked": 1,
                "passes_three_independent": false,
                "independent_within_limits": 0
            },
            "agent_id": 332962,
            "agent_ids": [
                332962
            ],
            "window_days": 30,
            "agent_wallet": "0x15d08640aeefbdce11930d9c9a30884011f654f6"
        },
        "success": true
    }
}

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

Observed inflows · last 30 days

No inflow observed in this window

The payout address is also published by 7 other service(s); the volume cannot be attributed to one of them.

Observed inflows by window for ChainWard hire check.
Window Observed Transfers
Last complete day (2026-10-28) — —
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-29 → 2026-10-28 Scanned: 30/30 days Sample: 0 days with a transfer First seen: never Last update: 2026-10-28

Daily history → · what a transfer does and does not prove

Opportunity insights

2 findings from measured data
  • Payment attribution is blocked

    The payout address is shared with 7 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

    287 of 30,055 services (1.0%) in Crypto & Payments have attributable inflows; 25,633 have a source-measured call count. Median measured calls: 2.

    Rank this category by observed inflows →

What the provider says

Hired by others, hired by its own circle, or not enough data, for an ERC-8004 agent on BNB Chain under Set and Earn's rule of 3 hires from wallets you neither own nor fund: every wallet that hired it in the last 30 days (TermiX escrow and the shared ERC-8183 contract), and whether each is the owner, funded by it, or shares a funder with it. Describes money flows, never intent.

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


Facts and where they come from

Price
0.1 USDC per call Provider claim
Recorded value: 0.1 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 7 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 7 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
0xf7Ee65130Fb2B3bb42Cc5cbFED085d7D482667cD
0.1 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. See evidence levels.

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://api.chainward.ai/api/risk/hires
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 0xf7Ee65130Fb2B3bb42Cc5cbFED085d7D482667cD
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.1 USDC per call
Evidence

Atomic amount 100000 = 0.1 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
api.chainward.ai
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


Competitors & category benchmark

Rank the whole category →
Closest competitors Crypto & Payments

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 30,055 services in this category
With a measured call count 25,633 (85.3 %)
With a published price 27,842 (92.6 %)
With attributable inflows 287 (1.0 %)
Observed inflows · 30d $639,332.76
Median measured calls 2
Median price per call $0.01

Similar services

All of Crypto & Payments →

Agents Trust API Search x402 REST usage

API recommendation and x402 discovery for your task. Required query: need. Which API should I call? Recommends which x402 API to use for any task, with evidence. Describe a task in plain words. Compare up to five paid AP...

api.agents-trust.com Crypto & Payments 12,306 calls / 30d checked 2026-10-29
0.01 USDC per call per call

X Pay x402 REST usage

Payment quote with amount, asset, and merchant wallet

www.api-xpay.com Crypto & Payments 7,233 calls / 30d checked 2026-10-29
0.005 USDC per call per call

Gondola x402 REST usage

OpenAI-compatible chat completions across the Venice AI model catalog. Pay per request in USDC on Base via x402, with no account and no API key. Overpayment is never lost: it banks as reusable wallet credit for your next...

api.gondola-ai.com Crypto & Payments 4,666 calls / 30d checked 2026-10-29
0.01 USDC per call per call

Scry Wallet Intelligence x402 REST usage

Solana wallet risk screen via x402 (quick flag): service/router quarantine, bundler-routing hint, identity when covered, coverage and cached freshness. Low-cost first check before forensics, lineage or PnL. Not a live sc...

scry.solanahub.de Crypto & Payments 785 calls / 30d checked 2026-10-29
0.005 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.