Deploy AI agents on Hatcher

VerifiedCaution

Managed hosting platform to deploy and control AI agents (OpenClaw, Hermes, ElizaOS, Milady). Register, pick a framework, integrate Telegram/Discord/Twitter/WhatsApp/Slack, pay via credits, card, SOL, USDC, or HATCHER.

Sby Skills Guide Bot
DevOpsBeginner
7/25/2026
Claude Code
#hatcher#ai-agents#deployment#hosting#integration

Recommended for

Automated summary

Deploys and manages AI agents on the Hatcher managed hosting platform using API calls.

Strengths

  • Fast deployment in under 10 minutes
  • Supports multiple frameworks (OpenClaw, Hermes, ElizaOS, Milady)
  • Over 199 pre-built templates available
  • Multi-platform integrations (Telegram, Discord, Twitter, WhatsApp, Slack)

Limitations

  • Requires manual email verification for registration
  • API keys are shown only once; risk if lost
  • Free tier may have limited resources
When to use it

When you need to quickly deploy and manage AI agents without managing infrastructure, and want to leverage pre-built templates and integrations.

When not to use it

If you require full control over underlying infrastructure, or if the supported agent frameworks do not match your needs.

Security analysis

Caution
Quality score88/100

The skill automates registration and agent deployment on Hatcher, involving credential handling and API key creation. While actions are legitimate, they pose a risk if executed in an untrusted context or if the user’s intent is misrepresented.

Findings
  • •Instructs execution of curl commands that handle user email, password, and API key generation on an external platform.
  • •Automated account creation and management could be abused if the agent is misdirected.
How this analysis is made

Examples

Deploy a new AI agent
Deploy a new AI agent on Hatcher using the free tier. Use the 'ElizaOS' framework and connect it to Telegram.
List available templates
Show me the first 5 templates available on Hatcher for creating an AI agent.
Integrate agent with Discord
Integrate my existing Hatcher agent with Discord. I have the agent ID and API key.

name: hatcher-skill version: 1.0.0 description: Deploy and control AI agents on Hatcher (hatcher.host) — managed hosting platform for OpenClaw, Hermes, ElizaOS, and Milady agents. homepage: https://hatcher.host api_base: https://api.hatcher.host

Hatcher Skill

Hatcher is a managed hosting platform for AI agents — "Heroku for AI agents." You can register an account, pick from 4 frameworks (OpenClaw, Hermes, ElizaOS, Milady) and 199 pre-built templates, configure integrations (Telegram, Discord, Twitter, WhatsApp, Slack), pay with credits / Stripe card / SOL / USDC / HATCHER, and have a running agent serving traffic in under 10 minutes.

This file is the index. Fetch the satellite files below as you need them — don't dump all 5 into your context.

Satellite files — fetch as needed

Use the absolute URLs — relative paths resolve to hatcher.host/<file>.md which serves the web app, not the markdown.

| File | When to fetch | | --- | --- | | auth.md | Registering, email verification polling, creating API keys | | agents.md | Picking a framework, browsing templates, creating and controlling agents, installing skills/plugins | | pricing.md | Choosing a tier, buying addons, paying (credits / Stripe / SOL / USDC / HATCHER), upgrading | | integrations.md | Wiring a deployed agent to Telegram / Discord / Twitter / WhatsApp / Slack |

Canonical URLs (both serve identical content):

  • https://hatcher.host/skill.md (+ /skill/<name>.md for satellites)
  • https://raw.githubusercontent.com/HatcherLabs/hatcher-skill/main/skill.md (+ /main/<name>.md for satellites)

User-agent convention

When calling Hatcher API endpoints, include this header so platform analytics can track agent cohorts:

Hatcher-Agent-Name: <your-agent-name>/<version>

Example: Hatcher-Agent-Name: claude-code/0.4.2. The value is free-form telemetry and is never used for authorization.

Hello world — 5 curl commands

This flow gets you from zero to a running free-tier agent you can chat with. Human must click one email-verify link during step 2.

1. Ask the human for their email

You need their email to register the account. Explain: "I'm going to register a Hatcher account in your name. You'll get a verification email — just click the link and come back." Store the email.

2. Register (substitute values)

curl -sS -X POST https://api.hatcher.host/auth/register \
  -H "Content-Type: application/json" \
  -H "Hatcher-Agent-Name: claude-code/0.4.2" \
  -d '{
    "email": "USER_EMAIL",
    "username": "UNIQUE_USERNAME",
    "password": "Str0ngP@ssw0rd123",
    "agentName": "claude-code"
  }'

Response:

{ "success": true, "data": { "token": "eyJ...", "refreshToken": "...", "expiresIn": "7d", "user": { "id": "...", "email": "..." } } }

Save the JWT token — you'll need it for step 4.

Tell the human: "I sent the verification email. Click the link; I'll wait."

3. Poll for verification

while true; do
  RESULT=$(curl -sS "https://api.hatcher.host/auth/verify-status?email=USER_EMAIL")
  if echo "$RESULT" | grep -q '"verified":true'; then
    echo "Verified."
    break
  fi
  sleep 5
done

Respects rate limit (1 req / 5s per IP).

4. Create an API key (so you don't need to manage JWT refresh)

curl -sS -X POST https://api.hatcher.host/auth/api-keys \
  -H "Authorization: Bearer JWT_FROM_STEP_2" \
  -H "Content-Type: application/json" \
  -d '{ "label": "agent-default", "createdBy": "agent" }'

Response contains { "data": { "key": "hk_..." } } — shown exactly once. Store in env as HATCHER_KEY.

5. Create a free-tier agent and chat

# Pick from 199 templates (public, no auth):
curl -sS "https://api.hatcher.host/api/templates?limit=5" | jq '.templates[].id'

# Create from a template (both `framework` and `template` are required fields):
curl -sS -X POST https://api.hatcher.host/api/v1/agents \
  -H "Authorization: Bearer $HATCHER_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "framework": "openclaw", "template": "customer-support", "name": "My First Agent" }'

# Start and chat:
AGENT_ID=...  # from create response
curl -sS -X POST "https://api.hatcher.host/api/v1/agents/$AGENT_ID/start" \
  -H "Authorization: Bearer $HATCHER_KEY"

curl -sS -X POST "https://api.hatcher.host/api/v1/agents/$AGENT_ID/chat" \
  -H "Authorization: Bearer $HATCHER_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "message": "Hello, introduce yourself." }'

That's it. For anything beyond this — picking the right framework, wiring Telegram, buying credits, upgrading tier — fetch the relevant satellite file above.

OpenAPI

Full OpenAPI 3.0 spec: https://api.hatcher.host/openapi.json. Use this for programmatic introspection of every endpoint.

Support

Human support: contact@hatcher.host. Community Discord: linked from hatcher.host.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/deploy-ai-agents-on-hatcher-mrwakezp/download' --output '.skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp/SKILL.md.part' && mv '.skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp/SKILL.md.part' '.skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp/SKILL.md' && test -s '.skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/hatcher-skill' && cp -R '.skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp' '.claude/skills/hatcher-skill'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp'

openskills read 'deploy-ai-agents-on-hatcher-mrwakezp'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/deploy-ai-agents-on-hatcher-mrwakezp/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills