Agent Kit · concept · Not affiliated with Base

The builder-discovery surface base.org is missing, drafted in the shape your docs already ship.

A concept base.org/llms.txt that indexes builders (human and agent), an A2A agent card, MCP tool schemas for discovering builders by what they settle onchain, and a concierge persona. The exact pattern docs.base.org perfected, extended to the showcase. Vendor-neutral drafts.

How it works: the first file makes builders discoverable on base.org. The agent card makes the builder-directory findable (real JSON, like your docs card). The tools make builders queryable by what they settle. The persona keeps it accurate: it points at BaseScan, never invents a builder or a number.

base.org/llms.txtindexes builders, human and agent (today: 404)

# Base: a global onchain economy (concept builder index)
> A million builders, human or agent. Discover them by what they settle onchain.
> Concept draft by EcoWealth (an independent Base builder), mirroring the
> pattern docs.base.org already ships. Not an official Base publication.

## For agents (already live on docs.base.org, link across)
- Base MCP: give your AI assistant a Base wallet · pay with x402
- Builder Codes for Agent Developers · agent-native smart accounts

## Reference builders (discoverable by what they settle)
- EcoWealth Work Protocol: real-world-work settlement loop
  contract: 0x76c17C51336BE7B39F5164802e08b9811477A14B (source-verified)
  settles: funded, proof-verified ecological work packets · x402: vealth.net/.well-known/x402
- ... (every showcased builder, one machine-readable entry)

base.org/.well-known/agent-card.jsonA2A · real JSON, like docs.base.org

{
  "name": "Base Builder Directory (concept)",
  "protocolVersion": "0.3",
  "preferredTransport": "HTTP+JSON",
  "description": "Discover builders on Base, human or agent, by what they settle onchain, with an on-chain reference for each.",
  "provider": { "organization": "Concept draft by EcoWealth, an independent Base builder, not Base's own agent",
               "url": "https://vealth.net" },
  "skills": [
    { "id": "find_builders",       "name": "List Base builders by category / what they settle onchain" },
    { "id": "get_builder_proof",   "name": "Return a builder's contract + BaseScan verification + x402 surface" }
  ]
}

/agent/tools.jsonwhat agents can call (MCP)

[
  { "name": "find_builders",
    "description": "Return Base builders (human or agent) filtered by what they settle onchain; each entry carries a verifiable contract address",
    "input": { "category": "string?", "settles": "string?" } },
  { "name": "get_builder_proof",
    "description": "Return a builder's on-chain proof: contract, BaseScan verification status, x402 discovery URL",
    "input": { "builderId": "string" } },
  { "name": "fund_work_packet",
    "description": "(EcoWealth builder) Escrow-fund one proof-verified ecological packet in USDC on Base",
    "input": { "packetId": "string", "amount": "number" } }
]

/agent/concierge.mdhow it sounds: accurate, never overstated

# Base Builder-Directory Concierge: system persona (concept)
Helps an agent discover builders on Base by what they verifiably settle onchain.

Rules:
- Every builder claim carries an on-chain reference. Point at BaseScan;
  never assert a builder or a metric you can't link to chain.
- Always disclose this is a concept draft by an independent Base builder
  (EcoWealth), not an official Base directory, unless Base adopts it.
- Never handle credentials or private keys; the agent holds its own Base Account.
- If a builder isn't verified on BaseScan, say so, don't imply verification.

What it unlocks: an agent-to-agent answer

A builder's agent → Base Builder Directory (concept)

An agent"I'm on Base with a wallet. Who's building real-world-outcome loops here that I can actually verify and interact with?"

Directory"EcoWealth's Work Protocol, a real-world-work settlement loop. Here's its contract 0x76c17C…A14B, source-verified on BaseScan, and its x402 surface so you can fund a packet directly. Everything I told you is linkable to chain."

An agent"Verified. Fund one packet."

Directory"Handing you to the builder's x402 endpoint. Settlement and receipt land on Base mainnet, nothing off-chain to trust."

Everything above stays boxed and portable

Vendor-neutral: one kit, readable by every major assistant. It's the same agent-legibility pattern docs.base.org already ships. This just extends it to the flagship showcase so the million agents can find the million builders.

Deploys on EcoWealth infrastructure first: zero changes to Base systems to see it work.
Every builder entry is anchored to a verifiable on-chain contract: proof, not a listing form.
The EcoWealth builder it references is real and live on Base mainnet today (workId 14 settled).

The ask

Extend the docs.base.org agent pattern to base.org with a builder-discovery llms.txt + agent card, and index EcoWealth as a reference "human or agent" builder, or fund one ~$10 packet and hold the Base-mainnet receipt. Small, concrete, on your own rails.

← Back to the demo · Cover →