Build for Stashville
Stashville has a public API. Anything that runs on a developer's machine, in a browser, or in a pipeline can send activity events and light up their city. Build your integration against the same API Perch, the daemon, and Claude Code use.
Start here
ResourceWhat it is
/docsHuman-readable developer docs. Covers auth, event shapes, rate limits, real-time streaming (SSE), an integration checklist, and a full reference of every Claude Code hook we consume.
/llms-full.txtComplete API reference formatted for LLM agents. Hand this URL to Claude/Cursor/Copilot with “build me a Stashville integration” and it should produce a compliant client in one shot. Source-of-truth; every number (rate limits, TTLs, thresholds) is pulled from the same constants the server uses to enforce them, so it can't drift.
/partners/brandBrand kit: logos, colors, voice guide, approved copy blocks, naming convention. How to present Stashville on your site, in your docs, in press releases.
/api/integrations/openapiMachine-readable OpenAPI spec (auth-gated — requires a key).
What you can build
- Editor / IDE extensions. VS Code, JetBrains, Zed, Sublime — any editor that can POST JSON can emit events.
- Tiling window managers and desktop overlays. Perch is the reference implementation — consumes the SSE stream, shows project state on every tile.
- Browser extensions. Track GitHub review activity, docs reading, issue triage — anywhere work happens in the browser.
- CLI tools and CI/CD pipelines. Emit GIT_COMMIT from GitHub Actions, FILE_CHANGE from deploy hooks, CUSTOM events from anything else.
- Chat bots. Slack/Discord bots that post state transitions, surface quests, broadcast Friday ceremony summaries.
- Anything else. If it runs code and has network access, it can integrate.
How submission works
Stashville's integrations directory is curated for now — we review every submission before listing. This keeps the directory useful and gives us a chance to check that your integration follows the integration checklist (honors rate limits, handles auth correctly, doesn't leak data). Turnaround is usually a few days.
- Build your integration against the public API.
- Walk the checklist and fix any gaps.
- Submit the integration — name, URL, description, who built it.
- We review, ping you with questions if any, and add it to the directory when approved.
As the directory grows, we'll move to fully self-service (instant listing for well-formed submissions, manual review for flagged ones). For now, every submission gets a human look.