Linzumi

Linzumi is a Y Combinator (Spring 2026) company in San Francisco building a Slack-shaped team chat that runs a fleet of AI coding agents inside every channel. Engineering teams kick off work, watch agent activity in real time, review output, and ship code without leaving the thread. Unlike sandboxed cloud agent products, Linzumi runs agents on the developer's own machine through a local "Commander" runner installed from the @linzumi/cli npm package, so agents work against real environment variables, dotfiles, and branches inside explicitly trusted folders. The product adds a decision inbox that surfaces only the choices needing a human, continuously compiled team context, git safety snapshots taken before each agent turn, and a bundled local MCP server that lets coding agents read scoped Linzumi message, thread, and channel context. It supports OpenAI Codex today with Claude Code announced as coming soon. The service is in beta via a macOS desktop app and a web workspace; there is no public developer API program, documentation portal, or published OpenAPI at this time.

Linzumi is listed with 1 API on the APIs.io network. Tagged areas include Company, Artificial Intelligence, Developer Tools, Coding Agents, and Team Chat.

Linzumi’s developer surface includes pricing, support, CLI, authentication, changelog, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

22.2/100 emerging ▬ flat Agent 5/100 agent aware Front door AI 4/6 moderate saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaidSelf serve

1 API 1 MCP Servers

Company Artificial Intelligence Developer Tools Coding Agents Team Chat Collaboration MCP Command Line Interface Y Combinator

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 22.2/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 4.0 / 17

Access Clarity 7.4 / 17

Operational Transparency 1.7 / 11

Contract Governance 0.0 / 10

Discoverability 6.2 / 9

Regulatory Posture 1.6 / 15

Agent readiness — 5/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 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

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/linzumi/"><img src="https://apis.io/badge/linzumi/card.svg" alt="Linzumi on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

11 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 23.8 — up to +15.2 composite points
Contract Governance scores 0.0 — up to +12.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/linzumi/apis.yml: open an issue on github.com/api-evangelist/linzumi to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Linzumi Runner API

The private product API behind the Linzumi web workspace and the local Commander runner, served from serve.linzumi.com under a /api/v2 URI-versioned path. It is not a published ...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Linzumi MCP Server

Local (stdio) MCP server; 4 tools listed.

MCP SERVER

Linzumi API pricing

Prices published by Linzumi, read 2026-10-07 from linzumi.com/. A free plan or tier is listed.

Plan	Price
Personal	Free Includes: One person, unlimited channels; coding agents in chat; runs on your machine with your own keys; live
Company	$100/ month Includes: Everything in Personal; all agents, all context, unlimited agent-hours; shared channels; voice, phon
Enterprise	Let's talk Includes: Everything in Company; SSO/SAML and SCIM; self-hosting, VPC, or your own cloud; SOC 2, audit logs; c

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Linzumi Plans Pricing

3 plans

PLANS

Security Posture 2

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

Linzumi Authentication

oauth2-device-code/oauth2-authorization-code · 3 schemes

SECURITY

Linzumi Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

LLMsTxt

LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

ErrorCatalog

ErrorCatalog

Lifecycle

Lifecycle

Build 2

SDKs, sample code, and the tooling you integrate with

Packages

Packages

CLI

CLI

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

Download

Download

Profile

Profile

Source (apis.yml)

aid: linzumi
name: Linzumi
description: Linzumi is a Y Combinator (Spring 2026) company in San Francisco building a Slack-shaped team chat that runs
  a fleet of AI coding agents inside every channel. Engineering teams kick off work, watch agent activity in real time, review
  output, and ship code without leaving the thread. Unlike sandboxed cloud agent products, Linzumi runs agents on the developer's
  own machine through a local "Commander" runner installed from the @linzumi/cli npm package, so agents work against real
  environment variables, dotfiles, and branches inside explicitly trusted folders. The product adds a decision inbox that
  surfaces only the choices needing a human, continuously compiled team context, git safety snapshots taken before each agent
  turn, and a bundled local MCP server that lets coding agents read scoped Linzumi message, thread, and channel context. It
  supports OpenAI Codex today with Claude Code announced as coming soon. The service is in beta via a macOS desktop app and
  a web workspace; there is no public developer API program, documentation portal, or published OpenAPI at this time.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Paid · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://storage.googleapis.com/ployai/d195dfe3-6a0f-4051-8d67-1a4376685f60/user/3e1aeaf5-og-home-en.jpg
url: https://raw.githubusercontent.com/api-evangelist/linzumi/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- y-combinator
x-tier: profiled
x-tier-reason: enriched-from-public-sources
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Artificial Intelligence
- Developer Tools
- Coding Agents
- Team Chat
- Collaboration
- MCP
- Command Line Interface
- Y Combinator
apis:
- aid: linzumi:runner-api
  name: Linzumi Runner API
  description: The private product API behind the Linzumi web workspace and the local Commander runner, served from serve.linzumi.com
    under a /api/v2 URI-versioned path. It is not a published developer API — there is no portal, reference, or OpenAPI —
    but it is partially observable through the publicly published @linzumi/cli client, which documents the device-authorization
    endpoint and speaks WebSocket to wss://serve.linzumi.com for runner traffic. Captured here as an observed surface, not
    a supported public contract.
  humanURL: https://www.npmjs.com/package/@linzumi/cli
  baseURL: https://serve.linzumi.com/api/v2
  tags:
  - Coding Agents
  - Team Chat
  properties:
  - type: Authentication
    url: authentication/linzumi-authentication.yml
  - type: Conventions
    url: conventions/linzumi-conventions.yml
  - type: ErrorCatalog
    url: errors/linzumi-problem-types.yml
common:
- type: Pricing
  url: https://linzumi.com/
- type: Plans
  url: plans/linzumi-plans-pricing.yml
- type: Website
  url: https://linzumi.com/
- type: Login
  url: https://serve.linzumi.com/
- type: Support
  url: mailto:hello@linzumi.com
- type: Download
  url: https://downloads.linzumi.com/macos-beta/linzumi_macos_latest.dmg
- type: Profile
  url: https://www.ycombinator.com/companies/linzumi
- type: Packages
  url: packages/linzumi-packages.yml
- type: CLI
  url: cli/linzumi-cli.yml
- type: MCPServer
  url: mcp/linzumi-mcp.yml
- type: Authentication
  url: authentication/linzumi-authentication.yml
- type: Conventions
  url: conventions/linzumi-conventions.yml
- type: ErrorCatalog
  url: errors/linzumi-problem-types.yml
- type: Lifecycle
  url: lifecycle/linzumi-lifecycle.yml
- type: ChangeLog
  url: changelog/linzumi-changelog.yml
- type: DomainSecurity
  url: security/linzumi-domain-security.yml
- type: LLMsTxt
  url: llms/linzumi-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Linzumi API — frequently asked questions

Does Linzumi have an API?

Yes. APIs.io lists 1 API from Linzumi, including Linzumi Runner API.

How do I authenticate with the Linzumi API?

Linzumi uses bearer-token authentication (oauth2-device-code/oauth2-authorization-code · 3 schemes). The details are profiled on APIs.io as Linzumi Authentication.

How much does the Linzumi API cost?

Linzumi publishes its prices; its Company plan is $100/ month as of 2026-10-07. APIs.io lists 3 pricing plans for Linzumi, with each plan's price, limits and inclusions under Pricing on this page.

Does Linzumi have an MCP server?

Yes. APIs.io lists 1 MCP server for Linzumi: Local (stdio) MCP server; 4 tools listed.

Is the Linzumi API ready for AI agents?

Linzumi has a Kin Score of 22.2 out of 100 (emerging) and an Agent Readiness score of 5.4 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/linzumi"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/linzumi/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/linzumi/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.