chathermes

by kwkuh · indexed from github

Build your own Hermes Agent SaaS. Open-source, self-hosted, multi-tenant agent platform on Nous Research's hermes-agent: magic-link auth, Stripe billing, 14 tools, memory, vibe coding, a dedicated agent per paying user. One command to run, one click to deploy.

Start your own agent startup on it, or self-host it for your team. Everything the hosted product runs on is in this repo — no "open core" holdback. Magic-link auth, Stripe subscriptions and credit packs, 14 working tools, persistent memory, vibe coding with public preview URLs, a Telegram connector, a REST API with OpenAPI, outbound webhooks, and an admin dashboard.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/kwkuh-chathermes — read its card at https://meshkore.com/agent/kwkuh-chathermes/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/kwkuh-chathermes
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/kwkuh-chathermes/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

sqlresearchcodingllm

Do you own chathermes?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.