Codag
Codag is a Y Combinator (Summer 2026) developer-tools company building drop-in log compression for AI agents. It takes oversized infrastructure logs — from Kubernetes, Docker, AWS CloudWatch, Vercel, Railway, Datadog, Sentry, syslog and unstructured sources — and returns only the lines that matter as schema-valid JSON, ranked into patterns where every kept line cites a real log line number so nothing is summarized away or invented. This lets coding agents like Claude, Codex and Cursor debug from the evidence that matters at roughly 95% fewer tokens without exhausting their context window. Codag ships as a hosted HTTPS API (/v1/compact), an open-source Go CLI, and an MCP server, with a deterministic Rust log-templating engine (codag-drain) as the free/fallback path.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Codag the way a machine reads it — 24 machine-readable artifacts across 19 APIs, 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 — Codag scores 51.5/100 (developing), with a separate agent-readiness read of 72/100 (agent native). 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.
How we profile Codag
Each block below is one kind of artifact we hold for Codag. 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.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Codag Activate API
The Activate API from Codag — 2 operation(s) for activate.
Codag Admin API
The Admin API from Codag — 2 operation(s) for admin.
Codag Anonymous API
The Anonymous API from Codag — 1 operation(s) for anonymous.
Codag Auth API
The Auth API from Codag — 4 operation(s) for auth.
Codag billing API
The billing API from Codag — 4 operation(s) for billing.
Codag Capsule API
The Capsule API from Codag — 1 operation(s) for capsule.
Codag Cli API
The Cli API from Codag — 2 operation(s) for cli.
Codag Compact API
The Compact API from Codag — 3 operation(s) for compact.
Codag Free API
The Free API from Codag — 1 operation(s) for free.
Codag Health API
The Health API from Codag — 1 operation(s) for health.
Codag Incident Memory API
The Incident Memory API from Codag — 3 operation(s) for incident memory.
Codag Install.sh API
The Install.sh API from Codag — 1 operation(s) for install.sh.
Codag Internal API
The Internal API from Codag — 2 operation(s) for internal.
Codag Oauth API
The Oauth API from Codag — 2 operation(s) for oauth.
Codag Onboard API
The Onboard API from Codag — 2 operation(s) for onboard.
Codag Org API
The Org API from Codag — 14 operation(s) for org.
Codag Orgs API
The Orgs API from Codag — 13 operation(s) for orgs.
Codag Parse API
The Parse API from Codag — 1 operation(s) for parse.
Codag Whoami API
The Whoami API from Codag — 1 operation(s) for whoami.
Scroll within the panel for all 19 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
codag-mcp.yml
MCP SERVERSecurity Posture 3
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Codag — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/codag · machine-readable index on apis.io