Project: Nemo

project-nemo Project Page

active project

Project

Overview

AI email agent. Receives inbound email via Postmark webhook, processes it with Claude (Opus 4.6) via the Anthropic API, and takes action through client project APIs.

Nemo is the brain layer — client apps (Rails, FastAPI, etc.) are the hands. Each client project gets a projects/<project>/ directory with a workflow guide that teaches Nemo how to use that project's API.

Architecture

Python service (FastAPI + Anthropic SDK) deployed to the Hetzner k3s cluster. Two responsibilities:

Webhook receiver — accepts Postmark inbound email POST, routes to project agent
Agent loop — uses Claude Opus 4.6 to process emails and execute workflows with tool use

Email flow: Postmark inbound → Nemo webhook → Claude decides action → calls client API → sends via Postmark outbound.

Repos

ldraney/nemo — Python service repo (Forgejo)

User Stories

story:billing-follow-up

As Marcus (admin), I want an AI agent that emails me billing drafts for each player and waits for my approval before sending, so that I can process billing follow-ups via email without needing to log into any app.

First project. 17 remaining players owe money for tournament fees and monthly dues. Nemo pulls data from the westside-basketball Rails API, drafts emails, gets Marcus's approval via Postmark email thread, sends to parents.

Board

Board: board-nemo

Key People

Lucas Draney — superadmin, monitors Nemo's operation, handles technical issues
Marcus Draney — admin, approves/adjusts billing emails via email reply