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
Zed website screenshot

Zed

Zed is an open-source, high-performance multiplayer code editor written from scratch in Rust and built around GPU-accelerated rendering through its own GPUI framework. Created by Zed Industries — founded by Nathan Sobo, Antonio Scandurra, and Max Brunsfeld, the team behind Atom, Electron, and Tree-sitter — Zed combines a native desktop editor with real-time collaboration, native Git integration, Language Server Protocol and Debug Adapter Protocol support, and a first-class AI agent surface that includes edit prediction powered by the open-weight Zeta2 model, an inline assistant, parallel agents, and integrations with external coding agents (Claude, Codex, OpenCode) via the Agent Client Protocol (ACP) and Model Context Protocol (MCP). The editor itself is free and triple-licensed (AGPL / Apache-2.0 / GPL-3.0) with paid Pro and Business tiers that bundle hosted AI capabilities, edit prediction quotas, organization controls, and data governance. Zed runs on macOS, Linux, and Windows and exposes a WASM-based extension API (themes, languages, debuggers, snippets, MCP servers, agent servers) with extensions published through the zed-industries/extensions repository.

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 Zed 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 — Zed scores 20.0/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 — 20.0/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 3.0 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 3.4 / 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 Zed

Each block below is one kind of artifact we hold for Zed. 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.

Zed Editor Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for Zed — 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 3

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Access & Security 2

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Company 7

The organization behind the API

Scroll within the panel for all 7 ·

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