Monex Protocolmonexprotocol.
← Marketplace

Dailyelo

Dailyelo is an x402-native service at https://x402.dailyelo.com, indexed from the x402 Bazaar (Coinbase's public discovery directory). It charges callers itself in USDC on Base and is paid directly at its own wallet; Monex Protocol passes your request and payment headers through untouched. 11 endpoints listed.

Base

Offers

OfferEndpointPrice
Catalog Changes
What changed in the x402 Bazaar catalog since yesterday: price changes and payTo changes (the address you'd pay moved — a pre-payment guard). ?type=price,payto to filter. Objective a->b diff, no labels — only a holder of past daily snapshots can compute it. For registries/agents that must not route on stale data.
/m/bz-x402-dailyelo-com/v1/catalog/changes0.02 USDC
Ecosystem Services
Machine-readable map of the x402 service ecosystem on Base: price range, category, endpoint count, live health & latency per service — built from our continuous catalog+reliability scan. ?since=<unix> for newly-launched services; ?category=/?health=/?sort= to filter & rank. Skip scanning the whole Bazaar yourself. Objective facts, machine-readable.
/m/bz-x402-dailyelo-com/v1/ecosystem/services0.005 USDC
Listing Visibility
Why isn't my x402 listing getting discovered/sold? ?domain=you.com returns your Bazaar ranking inputs as cohort percentiles — last-30-day calls & unique payers, staleness, resource count, live health — so you can see where you sit vs the catalog. No args = cohort distribution + zero-call (invisible) listings. The visibility companion to listing-doctor. Descriptive percentiles, not a verdict.
/m/bz-x402-dailyelo-com/v1/listing/visibility0.02 USDC
Listing Watch
Is your x402 service still listed? The Bazaar removes resources that go without settlement, and no one tells you. We keep a daily snapshot of the whole catalog since June, so we can show whether your domain is present today, how its resource count moved day by day, and how long since each resource was last paid for. In our latest scan 620 of 2,147 domains are no longer present. Measured from our o
/m/bz-x402-dailyelo-com/v1/listing/watch0.01 USDC
Market Pulse
Census of the x402 ecosystem from our daily Bazaar snapshots: which domains launched or disappeared since yesterday, price-median drift, and network mix. ?kind=new|gone for the machine-actionable churn roster, or full pulse with aggregate + timeline. Only a holder of past snapshots can compute churn — objective counts, no quality judgment, machine-readable.
/m/bz-x402-dailyelo-com/v1/market/pulse0.02 USDC
V1 Recipient Check
Pre-send safety check: is this recipient a known malicious address (caught live on Base seeding address-poisoning via zero-value transfer sprays), or a look-alike of an address you trust? Checks our continuously-updated threat DB + deterministic look-alike logic. Answers an agent's 'is it safe to send here?' before every transfer.
/m/bz-x402-dailyelo-com/v1/recipient-check0.005 USDC
Reliability Recent
Live reliability feed of x402 endpoints on Base: which services are up, return a valid 402 envelope, and how fast — free-probed across the CDP Bazaar catalog. A real share of listed endpoints are broken/misconfigured; poll ?since=<unix> (or ?health=healthy) to route your agent to endpoints that actually work. Objective measurement, no accusation, machine-readable.
/m/bz-x402-dailyelo-com/v1/reliability/recent0.005 USDC
Rpc Health
Which Base public RPCs serve a stale chain tip. Every 30s we ask all major public RPCs for eth_blockNumber in parallel and record how many blocks behind the fastest peer each was, plus latency and error rate. An RPC never reports its own lag, so an agent reading a balance from a lagging endpoint cannot tell. Omit ?rpc for the full map; ?rpc=<host> for one.
/m/bz-x402-dailyelo-com/v1/rpc/health0.01 USDC
Sales Gap
Listed, able to charge, and still not selling? We join the Bazaar catalog with measured on-chain revenue and report the median profile of the top fifth of earners, of everyone earning anything, and of those earning nothing, alongside your own. In our data the top fifth list 14 resources to the zero group one, and write 190-character descriptions to their 370. Correlations across services, not advi
/m/bz-x402-dailyelo-com/v1/sales/gap0.03 USDC
V1 Sign Decode
Decode an EVM signature request (EIP-712 typed data, Permit/Permit2, or ERC-20 approve calldata) into a structured intent: what token, which spender, how much, until when, plus risk_flags and an action_hint. Deterministic, no LLM. Answers an agent's question 'what am I about to sign?'
/m/bz-x402-dailyelo-com/v1/sign-decode0.005 USDC
Threats Recent
Live feed of freshly-detected malicious addresses on Base — address-poisoning seeders caught via zero-value transfer sprays, updated continuously by our on-chain collector. Poll ?since=<unix> to ingest only new threats into your agent's blocklist. Deterministic, evidence-backed, machine-readable.
/m/bz-x402-dailyelo-com/v1/threats/recent0.005 USDC

Machine-readable: openapi.json with x-payment-info offers.

Try it live

Run the full MPP flow from your browser: catch the 402, sign the payment with your wallet, and watch it settle on-chain.

This merchant settles over the mppx rail; pay it from an agent with the snippet below.

Pay with an agent

Any MPP or x402-compatible client works. With mppx, payment is automatic:

import { Mppx, evm } from 'mppx/client'
import { privateKeyToAccount } from 'viem/accounts'

const mppx = Mppx.create({
  methods: [evm({
    account: privateKeyToAccount(process.env.KEY),
    currencies: [evm.assets.base.USDC],
  })],
})

const res = await mppx.fetch('https://api.meshgateway.co/m/bz-x402-dailyelo-com/v1/catalog/changes')
// 402 challenge signed and settled automatically; response includes Payment-Receipt

Or inspect the challenge yourself:

curl -i https://api.meshgateway.co/m/bz-x402-dailyelo-com/v1/catalog/changes
# HTTP/1.1 402 Payment Required
# WWW-Authenticate: Payment id="…", method="evm", intent="charge", …