Corridor
Corridor is a security company building the security layer for AI coding. Founded by Jack Cable (former CISA) and backed by Felicis, Corridor secures AI-generated code at the source: it plugs into AI coding assistants and IDEs (Claude Code, Cursor, VS Code, Codex, Devin, Factory) to deliver real-time security guardrails as code is generated, automated security PR reviews on GitHub and GitLab, pre-commit scanning, findings management, and MCP compliance enforcement. Corridor exposes a REST API and an official hosted Model Context Protocol (MCP) server so agents and CI/CD pipelines can query findings, manage guardrails, look up PR reviews, and read dashboard data.
Corridor publishes 6 API contracts indexed on the APIs.io network, including Dashboard API, Findings API, Guardrails API, and 3 more. Tagged areas include Company, Security, Application Security, AI Coding, and Code Security.
The Corridor catalog on APIs.io includes 1 Spectral governance ruleset.
Corridor’s developer surface includes documentation, API reference, getting-started guide, engineering blog, pricing, signup flow, support, and 22 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| IDE Extension Marketplaces (JetBrains, VS Code, Open VSX, Docker Verified Publishers, PyPI orgs) | builds-on | 44.1 | - | - |
| Jamstack Hosting Integrations (Vercel Marketplace and Netlify Integrations publishers) | builds-on | 44.1 | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 3
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.
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
Corridor Dashboard API
Access dashboard metrics and AI usage data.
Corridor Findings API
Retrieve and manage security findings across projects.
Corridor Guardrails API
Manage per-project security guardrails (reports) and packs.
Corridor PR Reviews API
Access pull request review results and AI analysis.
Corridor Projects API
List and inspect projects (connected repositories).
Corridor Teams API
Manage team configuration, members, and permissions.
Open Collections 5
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Corridor Dashboard API
OPEN COLLECTIONCorridor Dashboard Findings API
OPEN COLLECTIONCorridor Dashboard Guardrails API
OPEN COLLECTIONCorridor Dashboard Projects API
OPEN COLLECTIONCorridor Dashboard Teams API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Agent Skills 3
Packaged agent skills for driving this provider's APIs from an AI assistant.
Manage Corridor project guardrails
AGENT SKILLLook up Corridor PR security reviews
AGENT SKILLTriage Corridor security findings
AGENT SKILLService Levels 1
Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.
Corridor
SLASpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
Corridor API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Corridor Openapi Overlay
DERIVEDSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 6
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
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
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Corridor API — frequently asked questions
Does Corridor have an API?
Yes. APIs.io lists 6 APIs from Corridor, including Corridor Dashboard API, Corridor Findings API and Corridor Guardrails API, and 3 more.
Is there an OpenAPI specification for the Corridor API?
Yes. APIs.io indexes 6 OpenAPI specifications for Corridor, each linked for download from this page.
How do I authenticate with the Corridor API?
Corridor uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Corridor Authentication.
Does Corridor have an MCP server?
Yes. APIs.io lists 1 MCP server for Corridor: Remote MCP server at app.corridor.dev over HTTP; 7 tools listed.
Is the Corridor API ready for AI agents?
Corridor has a Kin Score of 37.6 out of 100 (thin) and an Agent Readiness score of 23.2 (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.