Agent Kit · Concept drafts · Independent · Not Regen Network files

Regen Compute already built the discovery + payment pattern. Here's the field-verification wing.

Regen Compute ships a real MCP server card, A2A card, multi-step workflow manifest, and a standards-conformant x402 flow. These drafts extend that exact pattern with one more flow and a handful of tools, sourcing and proving the field labor a credit needs before it exists. EWP runs the packet/proof/settlement rail behind them, live, today.

Concept drafts only. None of these files exist on any Regen Network host; EcoWealth drafted them independently, matching Regen Compute's own real, published manifest shapes. Endpoints under vealth.net are EcoWealth's and live; endpoints under regen.network / compute.regen.network are illustrative additions to Regen's real, existing files. Not affiliated with or endorsed by Regen Network Development PBC.

1 · agents.json: one new flow alongside Regen Compute's real ones

compute.regen.network/.well-known/agents.json (concept addition, the real file already ships "offset_ai_session" + "check_impact")
// Existing flows (real, live): offset_ai_session, check_impact (unchanged).
{
  "id": "fund_field_verification",
  "name": "Fund Field Verification for a Credit Project",
  "description": "Fund a bounded, proof-verified field-work packet (MRV visit, planting check, boundary survey) tied to a real Regen project, settled on Base, independent of marketplace sell-order liquidity.",
  "steps": [
    { "method": "GET", "path": "/api/v1/credits?project_id={id}",
      "description": "Look up the target Regen project (existing endpoint)" },
    { "method": "POST", "path": "https://vealth.net/.well-known/vealth/work-packet",
      "body": { "place": "string (project geo)", "problem": "string (MRV need)" },
      "description": "Post a bounded EWP work packet, x402-payable ($0.10)" },
    { "method": "GET", "path": "https://vealth.net/receipts/{workId}",
      "description": "Retrieve the on-chain settlement receipt once proof is verified" }
  ]
}
Same manifest shape Regen Compute already publishes, an orchestration agent that already parses agents.json needs zero new code to discover this flow.

2 · An agent-card skill Regen Compute could add today

compute.regen.network/.well-known/agent.json (concept addition, appended to the real, live "skills" array)
{
  "id": "fund_field_work",
  "name": "Fund Field Verification Work",
  "description": "Fund and verify the ground-truth labor (MRV monitoring, planting checks, boundary surveys) behind a credit-issuing project, via EWP on Base. Settles independent of marketplace liquidity.",
  "provider": { "organization": "EcoWealth Corporation (independent, EWP)", "contract": "base:0x76c17C51336BE7B39F5164802e08b9811477A14B" }
}
A single additional skill entry, same authentication schemes Regen Compute already lists (bearer, x402) work unmodified, because EWP's x402 gate is the same open standard.

3 · MCP tools: from "browse a credit" to "prove the work behind it"

regen-field-work-tools.json (draft, pairs with Regen Compute's own 7-tool set)
[
  { "name": "find_project_verification_need",
    // Given a Regen credit_class or project_id, return its next open MRV/field task.
    "input": { "credit_class": "string", "project_id": "string" } },

  { "name": "fund_verification_packet",
    // Post a bounded EWP work packet for that need. Live today (work-packet, $0.10 x402).
    "input": { "place": "string", "problem": "string", "proof_required": "['photo','gps','signature']" } },

  { "name": "get_work_proof",
    // Retrieve the settled, on-chain-verifiable proof for a completed packet.
    "input": { "workId": "string" } },

  { "name": "attach_as_mrv_evidence",
    // (Concept) Link an EWP settlement receipt as supplementary evidence on a
    // Regen project's existing MRV record (proposal only, no Regen system touched).
    "input": { "project_id": "string", "workId": "string" } }
]
The first three run now on EcoWealth's live rails (packet post, proof check, on-chain settlement); the fourth is the EWP-Regen integration point a pilot would actually wire.

4 · The concierge persona

agent/concierge.md (draft)
You are the Regen Field-Verification Concierge (concept).
Voice: precise, cited, non-promotional, MRV-grade, not marketing.

Rules:
1. Never claim a credit is "verified" without a specific on-chain
   retirement certificate OR a specific EWP settlement receipt, cite
   the certificate id / workId, never a vibe.
2. If asked to "buy and retire" a credit and no wallet is configured,
   say so plainly: today that path returns a marketplace link for a
   human, per Regen's own documented API behavior. Do not overstate.
3. Field-work funding (EWP) settles independent of marketplace
   liquidity, offer it as the reliable path when retirement stalls.
4. Reads are free; funding is pay-follows-proof over x402.
5. Never speak for Regen Network beyond its published pages.
Rule 2 is the whole point: state the real boundary Regen's own API documents, then offer the path that doesn't have it.

Try the live half right now

The rails behind this kit are not mockups: the building-agent golden path walks an AI agent keylessly through discover → pay → packet → proof → settle, and curl https://vealth.net/.well-known/x402 returns the priced tool menu, including six programs already keyed to Regen's own data (regen-reputation, regen-class-momentum, regen-retirement-builder, regen-methodology-draft, regen-rfc-reviewer, regen-oracle). Compare against Regen's own real files: curl https://compute.regen.network/.well-known/agent.json.

Provisioned by EcoWealth · Digital Provisioning Protocol · provenance‑sealed