bridge.eco moves any crypto into a Regen carbon retirement. Nobody outside Regen built a way for an agent to use it.
bridge.eco (brand: ecoBridge, company: ecoToken) is a cross-chain swap-and-retire bridge that lets you pay in 50+ tokens across 8–10+ chains and fund a verified Regen Network ecological-credit retirement in one flow. EcoWealth already touches this rail: our regen-compute MCP (the interface an AI assistant calls to use a service correctly) integration includes browse_ecobridge_tokens and retire_via_ecobridge, the same public server ecoBridge's own CEO has personally committed code to — the identical repo our operator has 5 commits on. This is a full landscape map, an evidenced capability + traffic-readiness read, and an agent-ready demo, built for a real warm handoff (operator-only, not sent).
The whole thing, plainly
This is a landscape map and evidence-first read of bridge.eco, prepared for a warm contact the operator already has. We found genuinely rich infrastructure and a real Regen Network relationship, but no way for an AI agent to use any of it. The ask is one small paid work packet and three quick fixes, not a partnership pitch.
The landscape, in one map
One company, one consumer brand, two names for the same protocol layer, five live front-ends, one real validator relationship with Regen.
ecoToken
The company. Team: James Bettauer (CEO/Founder), Alexander Paredes (CTO), Forrest Rohr (COO), Kerstin Butzelaar (Marketing) — ecotoken.earth/about/.
ecoBridge
The unified product brand across both live surfaces — ecotoken.earth (WordPress marketing/blog) and bridge.eco (the live Vite/React swap-and-retire app).
CCEP / ecoLedger
The protocol layer — two different names used on live properties today: scan.ecotoken.earth titles itself "CCEP Scanner"; ecotoken.earth's own homepage calls the identical concept "ecoLedger."
bridge.eco
Swap (any token → REGEN via Squid Router, 70+ chains) · Impact (fund a specific Regen project retirement) · Stake (delegate to ecoBridge's own validators) · AI ("ecoAgent" in-app chatbot).
Other front-ends
app.ecotoken.earth (Solana) · eclipse.ecotoken.earth (Eclipse) · aptos.ecotoken.earth ("Aptos Biodiversity & Carbon Marketplace") · regenatlas.xyz (CELO, "Regen Atlas") — all named ecoBridge's own "marketplaces" in its GitBook docs.
scan.ecotoken.earth
The CCEP transparency scanner — verify any cross-chain retirement transaction and its NFT Impact Certificate.
Regen relationship
Not just a listing: $REGEN adopted as CCEP/ecoLedger's own governance token (Oct 2024), all ecoLedger data posted to Regen Ledger, and a live ecoBridge-run validator on Regen Network ($77,266 TVL, 16.02% APR) — plus ecoBridge's CEO has a direct commit on regen-network/regen-compute, the MCP repo our own operator also contributes to.
Ten facts from the public record
Credit-first, because real credit is due. Every fact has an exact HTTP/API repro command in evidence.json.
A real, rich, undocumented API
api.bridge.eco/registry is open, CORS-unrestricted, no auth — and embeds an LLM-ready quality rubric + sales copy per project. ecoBridge's own dev docs never mention it.
A genuine validator relationship
ecoBridge runs its own validator on Regen Network ($77K TVL, 16% APR) and adopted $REGEN as its governance token — infrastructure-deep, not a listing.
Its own AI tab isn't agent-callable
bridge.eco ships an "ecoAgent" chat panel — a proprietary human chatbot inside a closed SPA. No llms.txt, agent-card, or MCP manifest anywhere; zero mentions of "agent" or "MCP" in 28KB of their own docs.
Regen built ecoBridge's only real agent door
browse_ecobridge_tokens / retire_via_ecobridge live in Regen's own regen-compute MCP server — not anything ecoBridge itself publishes.
Credit-type claim doesn't match inventory
"All Regen credit types" in practice = 8 Carbon + 1 correctly-labeled Terrasos (BT01) + 1 mislabeled KSH01 project tagged "Carbon." Zero Marine Biodiversity, zero Umbrella Species.
A dead-end wallet field
One live project (Kasigau Corridor REDD) has an empty EVM wallet address — unpayable from Base/Ethereum/Polygon despite being listed as available.
Three numbers, one question
"70+ chains" (swap) vs "10 chains" (retire, homepage) vs two different "8 chains" lists (docs vs live API) — none agree.
28.6 MB to show a swap box
bridge.eco transfers 28.6 MB (17.2 MB JS bundle) to render "Pay / Receive / Connect" — plus a real broken-import console error (Stellar wallet init).
A real page error on the flagship site
ecotoken.earth throws "Bootstrap's JavaScript requires jQuery" on every load — a genuine script-order bug, not noise.
Zero link previews anywhere
Neither bridge.eco nor ecotoken.earth ships a single Open Graph or Twitter Card tag — every shared link renders bare on X/Discord/Slack.
The note, in three pages
Capability + traffic-readiness brief
An evidenced read of the whole ecoToken/ecoBridge landscape
Landscape map, credit-first findings on the real API richness and the Regen relationship, then the agent-discovery gap, the credit-type accounting, and a plain traffic-readiness audit (page weight, JS errors, link previews, the 5-second test) — each with the exact URL, status, and re-check command.
What "agent can retire a credit end-to-end, keylessly" actually requires today
In ecoBridge's own palette: Act One is today's real path (a human, a connected wallet, ecoBridge's own chatbot); Act Two is a concept — an EWP field-work packet funded and settled the way a headless agent already can, no wallet UI required.
The standards layer, drafted for ecoBridge's own real flow
Concept files: an llms.txt (the file AI assistants read first), an A2A agent card (a file that lets an AI assistant use a service correctly), MCP tool schemas matching ecoBridge's actual documented Swap/Impact/Stake flow, and an "ecoBridge Retirement Concierge" persona — shaped to sit on top of what already works, not replace it.
EWP contract 0x76c17C…A14B settles real-world ecological labor on Base mainnet, photo+GPS+signature proof to on-chain settlement, then retirement where ecological — the exact "field work behind a credit" layer that neither Regen's own stack nor ecoBridge's registry currently funds or verifies (see the just-shipped Regen Network engagement, docs/digital-engagements/regen-network/RECEIPT.md, for the fuller version of that argument). EcoWealth already calls ecoBridge's own rail through Regen's public regen-compute MCP server — browse_ecobridge_tokens (read-only, used to produce this brief) and retire_via_ecobridge (never called in this engagement — no transaction, no wallet touched).
The ask
1. Fund one EWP work packet tied to one real, already-registered ecoBridge/Regen project (a few dollars) — the field-verification layer underneath the credit, settled on Base independent of ecoBridge's own liquidity/wallet requirements.
2. Fix the small, technical things — a real llms.txt at the standard path, an honest label on the KSH01 project, a populated EVM wallet for Kasigau, one shared chain-count number. None of it touches the retirement mechanics that already work.
3. The warm handoff — the operator holds a real contact for bridge.eco. This package exists to make that conversation proof-first. Sending it is the operator's call, not automatic.
ecoBridge built a genuinely rich, cross-chain retirement rail and a real validator relationship with Regen — credited in full. But the only thing that can call it like an agent today is Regen's own MCP server, built partly by ecoBridge's own CEO. The gap isn't ambition. It's that ecoBridge never wrote its own front door for what its closest partner already built.
