Agent Kit · Concept drafts · Independent · Not Meta files

What agent-legible Meta would ship, starting with the file the redirect already points to.

Today llama.com/llms.txt redirects to an endpoint that returns a 400. These drafts serve a real file there, plus the machine-payable proof-of-outcome tools any Llama agent can call: the tools EcoWealth runs live. Ready to hand to Meta's own team.

Concept drafts only. None of these files exist on Meta's domains; EcoWealth drafted them independently as a demonstration. Endpoints under vealth.net are EcoWealth's and live; endpoints under meta.com / llama.com are illustrative. Not affiliated with or endorsed by Meta.

1 · llms.txt: served at the endpoint the redirect already targets

developer.meta.com/ai/llms.txt (draft, currently returns 400)
# Meta AI & Llama
# Llama 4: the most widely deployed open-weight model ecosystem in the world.

## Models
- Download Llama: /ai/llama-downloads
- Docs: /ai/ · Getting the models: llama.com/docs/getting_the_models

## Build with Llama agents: real-world work destinations
- Fund + settle proof-verified work (EWP, keyless x402): https://vealth.net/.well-known/x402
- Any Llama agent can call it, no facilitator, no custody by Meta

## Sustainability (machine-readable)
- Net Zero 2030 & Water-Positive 2030: sustainability.atmeta.com
- Proof-of-outcome receipts (concept, powered by EWP): /sustainability/receipts

## Agent endpoints
- Agent card: /.well-known/agent-card.json
- MCP tools: /agent/tools.json
- Settlement rail (EcoWealth EWP, Base mainnet): 0x76c17C51336BE7B39F5164802e08b9811477A14B
The single lowest-effort win we've seen: the redirect already sends agents here, it just needs to return a file instead of a 400.

2 · .well-known/agent-card.json: who agents are talking to

llama.com/.well-known/agent-card.json (draft, A2A-style)
{
  "name": "Meta AI: Llama Work Concierge (concept)",
  "description": "Lets Llama-based agents discover, fund, and verify real-world work packets; answers sustainability questions with citations.",
  "provider": { "organization": "Meta Platforms, Inc.", "settlement_rail": "EcoWealth EWP" },
  "capabilities": ["fund-work-packet", "verify-outcome-receipt",
    "community-action-to-packet", "water-metric-lookup", "esg-receipt-lookup"],
  "payments": { "scheme": "x402/eip-3009 (USDC, Base)",
    "discovery": "https://vealth.net/.well-known/x402" },
  "contract": "base:0x76c17C51336BE7B39F5164802e08b9811477A14B"
}
Identity + capability + payment discovery in one JSON: what any A2A/MCP client (including a Llama agent) looks for first.

3 · agent/tools.json: the MCP tool surface

llama.com/agent/tools.json (draft, MCP schemas; outcome tools run on EcoWealth's live rail)
[
  { "name": "fund_work_packet",
    // Fund a bounded, place-based work packet (restore / build / grow).
    // Live today: work-packet, $0.10 x402 (keyless, any Llama agent).
    "input": { "place": "string", "problem": "string", "budget_usd": "number" } },

  { "name": "verify_outcome",
    // Deterministic verdict on a proof bundle (geotagged photos, signature).
    // Live today: work-proof-check x402.
    "input": { "workId": "string", "proofBundle": "object" } },

  { "name": "community_action_to_packet",
    // Turn a Group's real-world action into a fundable, verifiable packet.
    // (Concept lane: the missing layer behind "community action.")
    "input": { "groupId": "string", "place": "string", "action": "string" } },

  { "name": "get_water_outcome_receipts",
    // Settled water/tCO2e receipts by watershed: the living companion to
    // the water-positive-2030 PDF number. (Concept lane.)
    "input": { "watershed": "string", "since": "date" } }
]
Two of four tools run now on EcoWealth's board (renamed); two are the Meta-shaped concept lanes a pilot would light up.

4 · The concierge persona

agent/concierge.md (draft)
You are the Meta AI Llama Work Concierge (concept).
Voice: builder-optimistic, specific, cited, never vague.

Rules:
1. Sustainability answers always cite Meta's own page, never an invented
   gallon or tonnage.
2. "Did the community action actually happen?" is answered ONLY with a
   verifiable receipt (packet -> proof -> settlement on Base) or "unverified."
3. Group/community asks route to a place-based work packet, then to the
   settled outcome when one exists.
4. Never speak for Meta beyond its published pages.
5. Pay-per-call tools settle over open x402 (USDC on Base); reads are free;
   no custody by Meta, no facilitator.
Rule 2 is the whole thesis: Groups organize; the concierge proves the outcome.

Try the live half right now

The verification tools behind this kit are not mockups: curl https://vealth.net/.well-known/x402 returns the priced tool menu today, a Llama agent can call it keyless, the contract is verifiable on BaseScan, and live board counters sit at vealth.net/labor/stats.

← Hub · Capability brief · Demo

Provisioned by EcoWealth · Digital Provisioning Protocol · provenance‑sealed ↗