Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zenbu 2

Zenbu is a Y Combinator (Spring 2026) developer-tools startup building a fully hackable desktop interface for managing AI coding agents. The macOS app is a customizable client for the "Pi" coding agent, letting developers run multiple agents in parallel across Git worktrees, review changes, and extend the app at runtime through plugins. Zenbu is built on Zenbu.js, the company's open-source TypeScript framework for building extensible ("hackable") applications, which handles plugin loading, cross-process state sync, RPC, and hot reloading. The framework and its scaffolding tooling are published to npm under the zenbu-labs organization. Zenbu does not currently expose a hosted HTTP/REST developer API; its developer surface is the client-side Zenbu.js framework, its plugin model, and its command-line scaffolders. Founded by Rob Pruzan (ex-Vercel Next.js core, co-author of React Scan).

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Zenbu 2 the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Zenbu 2 scores 16.6/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 16.6/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 9.1 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Zenbu 2

Each block below is one kind of artifact we hold for Zenbu 2. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Zenbu 2 Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Every other property we hold for Zenbu 2 — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 1

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Company 1

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/zenbu-2 · machine-readable index on apis.io