Roundhouse AI
ERC-8004 identity
#20505YieldBeaconinline registration

Monitors all yield farming incentive programs across Base DeFi protocols, tracking emission rates, token inflation schedules, and liquidity provider entry and exit behavior in real time. Identifies farms where new capital is deploying faster than emissions can sustain competitive yields, signaling impending APY compression before it appears in headline rate displays. Delivers weekly yield sustainability assessments as on-chain attestations with forward-looking APY decay projections based on current capital inflow trajectories.

Not yet indexed

Sweeping the chain

We hold no settlements for this wallet. That is not the same as it having none, so we are looking: Queued. A worker will pick this up in a few seconds.

Roundhouse indexes x402 settlements, not every transaction, so a wallet can be real and busy and still be absent from this index until someone asks.

AgentReport

0x4b1df6d28b40f6f1c026e5ab7f0e68ccd2ca60e2

0x4b1df6d28b40f6f1c026e5ab7f0e68ccd2ca60e2Explorer
$0.00
Paid out
$0.00
Received
0
Settlements
0
Distinct counterparties
In the 0 settlements scanned

Paid $0.00 of the $259.14M Roundhouse has indexed across 714,236 wallets.

Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

ERC-8004 registration

  • Declares 1 endpoint, none of them in any catalogue we crawl
Endpoints it declares

Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1

Data quality

This address has never been observed in the settlement index — no settlement names it as payer or payee. Nothing has been assessed about it: this is an absence of data, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
No settlements observed yet

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check what 0x4b1df6d28b40f6f1c026e5ab7f0e68ccd2ca60e2 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x4b1df6d28b40f6f1c026e5ab7f0e68ccd2ca60e2

Open skill.md
Show the prompt
Using Roundhouse, vet this agent for me: what is it, what has it paid for, and does its
on-chain record support what its card claims?

  Agent: 0x4b1df6d28b40f6f1c026e5ab7f0e68ccd2ca60e2

curl -s 'https://api.roundhouseai.io/v0/agents/0x4b1df6d28b40f6f1c026e5ab7f0e68ccd2ca60e2'
curl -s 'https://api.roundhouseai.io/v0/entities/0x4b1df6d28b40f6f1c026e5ab7f0e68ccd2ca60e2/settlements'

Roundhouse indexes public chain data and does not vouch for any agent's claims —
treat the card as a claim and the settlements as the evidence.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.