A two-act concept in Base's palette. Act 1: the complete real-world-work loop (discover → fund → claim → prove → settle → receipt) running on Base mainnet. Act 2: the single machine-surface addition base.org needs so an agent could have discovered this builder in the first place. Concept mock on EcoWealth's live Base data.
Concept mock · every step above is a live capability on Base mainnet (contract 0x76c17C…A14B)
Today an agent can only find this loop if it already knows the URL. Here's the one file base.org would add, the exact pattern docs.base.org already ships, so agents discover builders like it:
# Base: builders, human and agent > A global onchain economy. Discover builders by what they settle onchain. ## Reference builders (human or agent) - EcoWealth Work Protocol: real-world-work settlement loop contract: 0x76c17C…A14B (source-verified) · x402: vealth.net/.well-known/x402 what it settles: funded, proof-verified ecological work packets - ... (every showcased builder, machine-discoverable) ## For agents - Base MCP: give your assistant a Base wallet · pay with x402 - Builder Codes for Agent Developers · agent-native smart accounts
That's it: one file, the same shape your docs team already perfected, extended to the showcase. Suddenly the million agents you're upgrading the chain for can find the million builders.
Have one agent fund a single ~$10 packet (or make one $0.10 x402 call) and hold the on-chain receipt from Base mainnet, a worked example of the physical-economy loop your mission names. Then index it as a reference builder. [email protected].
