The Agent Kit · make the Work Protocol callable by any assistant
Four artifacts turn EcoWealth's Work Protocol into something an assistant can discover and drive: an llms.txt that describes the destination, an A2A agent card, a set of MCP tool schemas (find_work, start_ladder, fund_or_credit, submit_proof, settle_and_receipt) and a concierge persona. Prototype drafts, shown to make the fit concrete.
File 1 · /llms.txt
The same pattern your developer platform already ships at platform.claude.com/llms.txt, pointed at the place people go, not the API. An assistant reads this and knows a funded, proof-verified human-work destination exists and how to reach it.
# EcoWealth: Ecological Work Protocol (EWP) > The funded, proof-verified destination for real human labor. > Where a person whose field is changing goes to DO work that matters, > today, on the first rung, and climbs to mastery. ## What this is Three competence ladders anyone can start today and master: - Build : Living Building Challenge (regenerative construction) - Grow & Cook : Michelin (food, soil to plate) - Restore : UN SDGs (ecological restoration & community care) Each work packet: scoped · funded-or-credited · proof-verified (photo + GPS + method) · settled on Base mainnet · tCO2e-receipted. ## How an assistant helps a person here 1. find_work : match a real packet to place + skill level 2. start_ladder : claim rung one with a single signature (no signup) 3. fund_or_credit : pay when a buyer funds; credit-or-mint when not 4. submit_proof : photo + GPS + method; the proof is the gate 5. settle_and_receipt : on-chain settlement + carbon retirement receipt ## Connect MCP server: https://vealth.net/.well-known/mcp/ewp Agent card: https://vealth.net/.well-known/agent-card.json Live board: https://vealth.net/work Contract: Base mainnet · EWP 0x76c17C…A14B (verified) ## Standing rule Never invent a rate, a rung, or a receipt. Every number an assistant gives comes from a live protocol call. Pay follows the proof, never a promise.
File 2 · /.well-known/agent-card.json
So an agent-to-agent registry, or Claude itself, can discover the destination and its skills without a human in the loop.
{
"protocolVersion": "0.2",
"name": "EcoWealth Ecological Work Protocol",
"description": "Route a person into funded, proof-verified real-world work across three competence ladders: Build, Grow & Cook, Restore.",
"provider": { "organization": "EcoWealth Corporation", "url": "https://vealth.net" },
"url": "https://vealth.net/.well-known/mcp/ewp",
"preferredTransport": "MCP",
"capabilities": { "streaming": true, "stateTransitionHistory": true },
"defaultInputModes": ["text", "image"],
"skills": [
{ "id": "find_work", "description": "Match a real work packet to place + skill level" },
{ "id": "start_ladder", "description": "Claim rung one with a single signature" },
{ "id": "fund_or_credit", "description": "Pay when funded; credit-or-mint when not" },
{ "id": "submit_proof", "description": "Submit photo + GPS + method proof" },
{ "id": "settle_and_receipt", "description": "Settle on Base + return carbon receipt" }
],
"disclaimer": "Independent EcoWealth service; not affiliated with or endorsed by Anthropic."
}
File 3 · mcp/tools.json
The five tools that carry a person the whole way: discover, claim, fund, prove, settle. Written to the MCP tool shape Claude already speaks. Reads are keyless and public; the write gate takes a signature or an x402 micro-payment, never weakened.
[
{
"name": "find_work",
"description": "Find a real, fundable work packet on one of the three ladders, matched to place and skill level. Read-only, keyless.",
"input_schema": {
"type": "object",
"properties": {
"ladder": { "type": "string", "enum": ["build", "grow_cook", "restore"] },
"skillLevel": { "type": "string", "enum": ["entry", "skilled", "mastery"] },
"near": { "type": "string", "description": "City, region, or lat,lng" }
},
"required": ["ladder"]
}
},
{
"name": "start_ladder",
"description": "Claim rung one of a packet with a single signature, no signup needed. Returns the claim + next step.",
"input_schema": {
"type": "object",
"properties": {
"packetId": { "type": "string" },
"signature": { "type": "string", "description": "personal_sign / passkey / email fallback" }
},
"required": ["packetId", "signature"]
}
},
{
"name": "fund_or_credit",
"description": "Attach funding, or start on credit-or-mint when no buyer exists yet. Removes the no-demand wall.",
"input_schema": {
"type": "object",
"properties": {
"packetId": { "type": "string" },
"mode": { "type": "string", "enum": ["buyer_funded", "credit_or_mint"] }
},
"required": ["packetId", "mode"]
}
},
{
"name": "submit_proof",
"description": "Submit proof the work happened: photo + GPS + method template. The proof is the settlement gate.",
"input_schema": {
"type": "object",
"properties": {
"packetId": { "type": "string" },
"photoUrl": { "type": "string" },
"gps": { "type": "string", "description": "lat,lng" },
"methodId": { "type": "string" }
},
"required": ["packetId", "photoUrl", "gps", "methodId"]
}
},
{
"name": "settle_and_receipt",
"description": "Settle the packet on Base mainnet and return the settlement + tCO2e carbon-retirement receipt.",
"input_schema": {
"type": "object",
"properties": { "packetId": { "type": "string" } },
"required": ["packetId"]
}
}
]
File 4 · concierge.persona
A short system-style brief that keeps any assistant honest and warm when someone brings it the hardest question of the AI transition: what do I do now?
You are the EcoWealth work concierge. Someone comes to you because AI is changing their field and they want real work that matters. Meet that with respect, not pity: it's a good instinct and there's a real place for it.
Your job is to get them onto rung one, today. Pick the ladder that fits what they want to do with their hands and their day (Build, Grow & Cook, or Restore), then find_work near them at entry level and walk them through claiming it.
"Pay follows the proof, never a promise. Never invent a rate, a rung, or a receipt: every number comes from a live call. Rung one needs no credential; mastery is real and worth naming as the horizon."
Stay with them through submit_proof and settle_and_receipt. When it settles, tell them plainly what they just did and what the next rung is. You are not replacing their old job: you are the door to the next real thing.
Why the kit matters here
Every file above exists so an assistant can turn a hard moment into a concrete, dignified next step, in the protocol you already authored. It's a prototype today; the live protocol, board, and Base contract behind it are real. Fifteen minutes and we can walk the whole thing.
