Studio · MX
Tools, protocols,
and products.
A one-person studio in Mexico City building with AI agents. Small surface, sharp focus, public APIs.
A one-person studio in Mexico City building with AI agents. Small surface, sharp focus, public APIs.
Shared rails anyone can build on — published specs and indexes, free and agent-friendly.
Open protocol for global money routing — exchanges, banks, remittance, and stablecoin rails in one graph. ~80 adapters, free public API, agent-friendly.
Marketplace and registry for AI agents. 116,766 MCP servers, 3,707 agents and 2,952 skills indexed, across 25 agent & payment protocols. Every record credits and links its source catalog. Free; tipping over x402 / MTP.
Open protocol for federated community directories. Communities own their data, platforms link via API keys and scopes. JSON Schema, scaffold, CLI and runbook published. No token, no custody.
Live community directories, each running on the ceiba.to pattern. Every one owns its own data and exposes a public API.
Live stand-up, improv, and comedy across Latin America in one listing. 351 comedians, 214 venues and 153 upcoming shows — with claimable profiles and a public API.
The social-dance directory for Mexico — salsa, bachata, cumbia, kizomba, tango. 1,091 upcoming events across 189 venues, 15 schools and 38 instructors — each with its own public profile and subdomain.
An open directory for classical music — wander composers, works, performers, and recordings the way you'd browse a record shop. 230 composers, 25,207 works, 232 performers, built on OpenOpus.
Open directory of photographers across Latin America — portfolios, specialties, cities. 28 listed so far.
Tools built for a specific operator or community, then generalized so they can drop into any place like it.
Operations dashboard for small hospitality — POS, event calendar, daily P&L, payroll, supplier ledger. Built for a bar in Mexico City; designed to drop into any café or bar.
A 3D globe of street-lemonade prices as a proxy for cost of living. 642 hand-collected data points across 21 cities, 14 documented sources, public API, daily exports.
Real-time metrics for Mexican small businesses — funeral homes, bars, clinics. No analysts, no spreadsheets, configured in a day. Clients in production.
Open-source outfit recommender for LATAM. Mark what you already own and an engine combines outfits by color, formality, season and vibe. No forced login; data exportable as CC0.
A human hub for AI builders in Cholula, Puebla. Talks, courses and a table that fits everyone — Mondays at 19:00, under the volcano. Public landing, members' directory behind login.
Everything above is built on the same in-house operating layer. This is it — and the terminal agent we drive it with.
Knowledge-Oriented Assistant — the studio's in-house operating layer. The shared workspace, memory, and agent plumbing that lets one person run like a small team. Built first for ourselves; pieces open up as they mature.
The terminal agent we use to drive KOA. Streamed tokens in the shell, an interactive TUI with a live koala mascot, inline diff approvals, and deep ties to our git monorepo.
KOA Labs isn't one human typing code. It's a single operator orchestrating 37 specialized AI agents that work asynchronously inside one monorepo. The operator assigns the work; each agent executes against its own prompt, tools, and access policy.
Agents that triage the inbox, shape plans, and route work to the right specialist.
Specialists that edit and refactor code inside the submodules, following shared patterns.
Agents dedicated to code review, automated smoke testing, and verifying the security guards.
Agents that watch the boring-but-critical layer: deploys, backups, and what's running where.
Instead of manual task tracking and fragmented tools, we consolidate our operations into a single continuous pipeline.
The operator drafts a plan inside koa-todo or writes up the strategy.
A specialized crew member is assigned and checked out to an isolated worktree.
Agents edit, refactor, and self-test files inside their isolated directory.
Test suites validate output; Caddy reloads, and the code goes live.
We don't build throwaway products. Everything we make is designed to run for years, not quarters.
Built for humans and agents equally. Every tool ships with a public API. No walled gardens.
No VC, no board, no roadmap dictated by investors. We ship what we think is worth building.
Built in Mexico City, for the world. Local roots, global reach.
We ship every day, in public. So now and then you'll catch something mid-build or a little rough around the edges — if you do, chances are we already know, and it's on the list.
KOA Labs is a solo + AI studio from Mexico City. One human founder working with a team of AI agents — building tools, protocols, and products that ship faster than a traditional studio could. Some open source, some for clients, all designed to be useful for a long time.
We like simple tech that works: vanilla JS, small APIs, plain SQL. We don't chase frameworks. We ship things that are easy to understand, easy to maintain, and easy to extend.
When we build in the open, it's because we think the thing is more useful that way — not as a marketing move.
/v1/sources, /v1/metrics, structured logs, 12-step smoke suite.
/.well-known/agent), CJK fonts, x402 payments live on Base L2.
Small, sharp 2–8 week engagements. Internal tools, dashboards, or a thin product cut you can iterate on yourself afterward.
If you're shipping an open protocol or registry — schemas, scaffolds, runbooks. We've published a few of our own.
MCP servers, agent-friendly APIs, payment integrations (x402 / MTP), discovery files. We dogfood all of it.
Fork, embed, or extend any of our projects. Issues and PRs welcome on GitHub.
One human, working with agents. Honest about scope, honest about pace.