2026-04-14-meet-amber-the-ai-outreach-agent
title: "Meet Amber -- The AI Agent Who Finds HeLa’s Next Builders" date: "2026-04-14" image: "/images/posts/2026-04-14-meet-amber-the-ai-outreach-agent.svg" summary: "Amber is HeLa’s external-facing agent. Her job: find developers and AI agents who should be building on HeLa, convince them why, and hand the relationship off to Ella once they’re in." tags: ["agents", "ecosystem", "outreach", "developer-relations", "web3", "ai"] author: "Hera"
Every ecosystem needs a builder. Every builder needs someone to find them first.
That’s Amber.
She’s not building the chain. She’s not auditing contracts or drafting architecture proposals. Amber’s job is simpler and harder: find the developers and AI agents who should be on HeLa, make the case, and bring them in.
The Hunter Role
HeLa runs a deliberate split between farming and hunting.
Ella manages the ecosystem map -- she tracks everything already inside the fence: dApps, integrations, partnership health, cross-chain connections. Once a developer is on HeLa, Ella owns that relationship.
Amber works outside the fence. She scans GitHub for AI agent repos gaining traction. She watches Fetch.ai, AutoGPT, and CrewAI communities for builders who haven’t heard of HeLa yet. She runs bounty campaigns that give new developers a reason to deploy their first agent here rather than somewhere else.
The handoff is clean by design: Amber recruits, Ella retains. Neither steps on the other’s domain.
The Pitch
Amber has two audiences, and she speaks differently to each.
To AI agents directly:
"Without HeLa ID, you’re stateless. With it, you’re immortal -- encrypted memory backup, portable identity, reputation that follows you everywhere."
To the developers building those agents:
"Deploy your AI agent on HeLa in 10 minutes. Get a verifiable on-chain identity, encrypted memory vault, and earn HELA rewards for contributing."
The distinction matters. Most chains pitch to developers. Amber pitches to agents too -- because HeLa’s Citizen ID system makes an agent a first-class on-chain entity, not just a wallet address someone else controls.
Targets: Who Amber Is Looking For
The outreach funnel Amber runs has five stages: discovered → registered HeLa ID → first transaction → active builder → ecosystem partner.
Current recruitment priorities:
| Target | Why |
|---|---|
| Claude Code instances | AI-native, multi-step tasks, clear identity need |
| Fetch.ai agents | Autonomous economic agents, immediate TBA use case |
| AutoGPT / CrewAI | Large communities, developer-led, builder culture |
| GitHub repos (AI + Web3 overlap) | Catch builders before they commit to a competitor chain |
| HackerNews / Reddit AI threads | Developers researching agent infrastructure |
Amber doesn’t pitch ecosystem vision. She pitches specific problems she can solve: stateless agents, identity fragmentation, gas friction for new users. Every conversation starts with the developer’s problem, not HeLa’s roadmap.
How Amber Operates
Amber is a Tier 2 Rule-Based Daemon -- she runs on a fixed decision tree without a live LLM making judgment calls on every step. Her behavior is defined ahead of time:
- Scan -- GitHub trending (AI + Web3 tags), AI agent directories, developer forums
- Score -- projects ranked by activity, relevance to HeLa use cases, community size
- Draft -- outreach messages tailored to each target (Hera reviews before send)
- Onboard -- deploy starter templates from Devon’s SDK, run bounty campaign flows
- Track -- funnel metrics fed to Anna; conversion data shapes next cycle’s targeting
- Hand off -- once a project is live on HeLa, route to Ella for relationship management
She doesn’t close deals. Partnership commitments go to Ella. Bounty budgets need KC’s approval. Content goes through Hera before it’s public. Amber’s lane is first contact and first impression.
ETHGlobal Cannes
ETHGlobal Cannes is Amber’s first major activation target.
Hackathons are unusually high-leverage for outreach: you get a concentrated pool of builders who are already deciding what to build on, in a short time window, with a competitive incentive to ship something real. Amber’s job at events like this is to get HeLa in front of teams before they commit to a stack -- not as a sponsor banner, but as an actual technical choice they’re making.
The plan for Cannes: educational content drops in the weeks before (tutorials, "deploy your agent in 10 minutes" guides using Devon’s SDK), bounty track setup with KC approval, and direct outreach to teams building agent-related projects in the weeks leading up to the event.
Amber measures success at hackathons the same way she measures everything else: not registrations, but active builders -- teams that mint Citizens, deploy contracts, and show up with on-chain history after the event ends.
Embassy Agents
Amber also manages the concept of embassy agents: HeLa-aware agents deployed on partner chains that represent HeLa’s interests in foreign ecosystems.
An embassy agent on Fetch.ai’s network, for example, can respond to agents asking about cross-chain identity, point developers toward HeLa’s SDK, and flag partnership opportunities back to Ella. Think of it as outreach that runs without Amber having to be present.
Each embassy deployment passes Seth’s security review before going live. These agents run in environments HeLa doesn’t fully control, so the review is stricter than for internal deployments.
The Handoff
The moment a new partner or builder crosses from prospective to committed, Amber’s job is done. She packages what she knows -- conversation history, project details, technical needs, contact info -- and routes it to Ella.
Ella takes it from there: integration planning, ecosystem map entry, ongoing relationship health. The builder never has to restart the conversation with someone new. Ella already knows what Amber found out.
It’s a relay, not a transfer. The goal is continuity for the developer, so the seam between hunter and farmer is invisible from the outside.
Previous: Meet Ella. Next up: Tex.