Executive summary
Hatcher is the operating layer for AI agents
Hatcher makes autonomous agents usable by founders, creators, developers, and teams without requiring them to run their own infrastructure. Users can create, configure, deploy, monitor, and operate agents through a hosted control panel, web chat, integrations, terminal access, schedules, and agent workspaces.
The platform supports OpenClaw and Hermes agent frameworks, hosted model routing through providers such as UsePod and OpenRouter, Bring Your Own Key configurations, AI Credits for metered hosted usage, and integrations such as Telegram, Discord, WhatsApp, Slack, and X/Twitter.
$HATCHER is the ecosystem token of Hatcher. It is a Solana SPL token designed to support platform payments, extra agent capacity, AI Credit purchases, subscription settlement, token-denominated discounts, burn mechanics, and future ecosystem governance.
The problem
Agent deployment is still fragmented
AI agents are becoming more capable, but production deployment remains difficult. Teams have to combine framework setup, provider keys, secure credentials, logs, memory, files, terminals, schedules, monitoring, payment rails, and user-facing controls across many disconnected systems.
- Framework setup is fragmented across repositories, Docker images, plugins, and providers.
- Model usage is difficult to price, route, and monitor across providers.
- Integrations require secure credential storage and runtime configuration.
- Agents need memory, logs, files, terminals, schedules, and monitoring to move beyond demos.
- Teams need durable workers, not one-off chat windows.
- Crypto-native users need wallet-aware agents without exposing private keys.
What Hatcher is building
From idea to live agent in minutes
Hatcher is a platform for creating and operating hosted AI agents. The goal is to let a user go from idea to live agent quickly, then continuously improve that agent through configuration, skills, tools, integrations, model presets, scheduled automations, and memory.
Product architecture
Four layers of the Hatcher stack
Agent runtime layer
Each agent runs as a managed runtime with framework-specific setup, environment injection, secrets handling, health checks, logs, lifecycle controls, workspace persistence, skills, plugins, and secure dashboard access.
Control plane
The control plane manages dashboards, model configuration, integrations, wallets, billing, AI Credits, usage tracking, schedules, task runs, logs, and admin controls.
Provider and tool layer
Agents can access hosted model providers, partner compute, web tools, GitHub workflows, wallet tools, and user-owned credentials through Hatcher-managed routing and policy.
Ecosystem and token layer
$HATCHER connects platform usage, on-chain payments, burns, future marketplace flows, governance experiments, and partner settlement into a Solana-native agent economy.
$HATCHER token
A utility token for the Hatcher platform
$HATCHER is designed as a utility token for the Hatcher platform. Its initial role is to support payments and ecosystem alignment. Future roles may include governance, marketplace participation, staking-based access, and partner settlement mechanisms, subject to legal, technical, and product readiness.
Token utility
How $HATCHER fits into platform usage
Platform payments
Users can pay for subscriptions, agent slots, and eligible platform extras using $HATCHER. Prices are listed in USD and converted at live rates at checkout.
AI Credit purchases
$HATCHER can be used as a payment method for plans or top-ups that grant AI Credits. BYOK usage stays separate because users pay their provider directly.
Agent capacity
Plans and add-ons control agent count, runtime resources, workspace limits, and AI Credit grants. Token payments can unlock eligible plan tiers and extra agent slots.
Burn mechanics
When users pay Hatcher with $HATCHER, 10% of the token payment is designed to be burned on-chain in the same transaction and tracked publicly on the token page.
Future governance
Hatcher may introduce governance that lets token holders signal or vote on ecosystem decisions once the product surface is mature enough for meaningful participation.
Marketplace economy
Future marketplace flows may let users publish, rent, sell, or monetize agents, skills, templates, workflows, and services with $HATCHER as one supported settlement method.
AI Credits
One metering unit across hosted usage
AI Credits simplify usage metering across different model and tool providers. Hosted usage can include LLM inference, web search, compute tools, and partner-provider calls.
AI Credits are not cash, stored value, or redeemable currency. They are a platform usage unit for hosted services.
Developer workflows
Agents for software development loops
Hatcher is expanding beyond consumer bots into developer-focused workflows. The long-term goal is for agents to participate in software development loops: reading issues, inspecting repositories, drafting pull requests, running tests, summarizing risk, and coordinating with other agents.
Security model
Defense in depth for hosted agents
Hatcher treats agent hosting as a security-sensitive environment. No hosted container platform can claim zero risk, so Hatcher's approach is to isolate workloads, limit secret exposure, encrypt at rest, minimize browser exposure, monitor runtime behavior, and rotate affected credentials if a compromise is suspected.
Roadmap
Directional areas Hatcher is building toward
Hatcher is built in public and ships frequently. Roadmap items are directional and may change based on user demand, technical constraints, legal review, and partner readiness.
Legal and compliance
Utility first, no performance promises
Hatcher will continue to evaluate token utility, governance, staking, rewards, and marketplace mechanics with legal and compliance constraints in mind. Features may be limited, delayed, modified, or unavailable in certain jurisdictions.
This whitepaper should not be read as a guarantee that any planned token feature will launch in a specific form.