Coro

Coro is a cybersecurity company that consolidates endpoint protection, email security, network protection (ZTNA, VPN, encryption), cloud app security, data protection, and security awareness training into a single AI-driven platform built for lean IT teams, growing organizations, and managed service providers (MSPs). Coro's public REST API (v1) exposes the same workspace security data through region-specific hosts (US, Canada, Germany), organized around workspaces as tenant containers with subscriptions, tickets, devices, protected users, portal users, usage metrics, audit logs, and webhook configurations. It authenticates with OAuth 2.0 client credentials and offers real-time webhooks and an official MCP server so AI tools can query Coro securely. Coro was surfaced as a portfolio company of Balderton Capital.

Coro is listed with 1 API on the APIs.io network. Tagged areas include Company, Cybersecurity, Security, Endpoint Security, and Email Security.

The Coro catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Coro’s developer surface includes documentation, getting-started guide, authentication, changelog, support, engineering blog, pricing, and 19 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

52.1/100 developing ▲ 6.3 Agent 39/100 agent ready Front door AI 4/6 moderate saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

AccessSelf serve

1 API 1 MCP Servers

Company Cybersecurity Security Endpoint Security Email Security Cloud Security Data Protection MSP Webhook MCP

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 52.1/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 8.5 / 17

Access Clarity 15.7 / 17

Operational Transparency 2.6 / 11

Contract Governance 1.9 / 10

Discoverability 5.5 / 9

Regulatory Posture 4.4 / 15

Agent readiness — 39/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 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 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

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/coro/"><img src="https://apis.io/badge/coro/card.svg" alt="Coro 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):

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
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

6 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 39.0 — up to +15.3 composite points
Developer Ergonomics scores 50.0 — up to +10.0 composite points
Operational Transparency scores 23.7 — up to +9.9 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/coro/apis.yml: open an issue on github.com/api-evangelist/coro 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 →

APIs 1

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

Coro Public REST API

Coro's REST API (v1) for managing workspaces, subscriptions, tickets, devices, protected users, portal users, usage, audit logs, and webhooks across the Coro cybersecurity platf...

MCP Servers 1

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

Coro MCP Server

Coro publishes an official, hosted MCP (Model Context Protocol) server that acts as a secure intermediary between an organization's AI tools and Coro's workspace security data. ...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Coro Plans Pricing

4 plans

PLANS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Coro Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Coro Webhooks

ASYNCAPI

Security Posture 3

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

Coro Authentication

oauth2 · 1 scheme

SECURITY

Coro Domain Security

TLSv1.3 · DMARC

SECURITY

Coro Trust Center

SOC 2, ISO 27001, PCI DSS, HIPAA, GDPR

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Webhooks

Lifecycle

Conventions

DataModel

Conformance

Access & Security 4

Authentication, authorization, and security posture

Authentication

Compliance

TrustCenter

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Source (apis.yml)

aid: coro
name: Coro
description: Coro is a cybersecurity company that consolidates endpoint protection, email security, network protection (ZTNA,
  VPN, encryption), cloud app security, data protection, and security awareness training into a single AI-driven platform
  built for lean IT teams, growing organizations, and managed service providers (MSPs). Coro's public REST API (v1) exposes
  the same workspace security data through region-specific hosts (US, Canada, Germany), organized around workspaces as tenant
  containers with subscriptions, tickets, devices, protected users, portal users, usage metrics, audit logs, and webhook configurations.
  It authenticates with OAuth 2.0 client credentials and offers real-time webhooks and an official MCP server so AI tools
  can query Coro securely. Coro was surfaced as a portfolio company of Balderton Capital.
url: https://raw.githubusercontent.com/api-evangelist/coro/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- balderton-capital
x-tier: stub
x-tier-reason: portfolio-lead
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: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: https://www.coro.net/wp-content/uploads/coro-opengraph.png
x-docs-platform: redocly
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-24
tags:
- Company
- Cybersecurity
- Security
- Endpoint Security
- Email Security
- Cloud Security
- Data Protection
- MSP
- Webhook
- MCP
tags_raw:
- Company
- Cybersecurity
- Security
- Endpoint Protection
- Email Security
- Cloud Security
- Data Protection
- MSP
- Webhooks
- MCP
apis:
- name: Coro Public REST API
  description: Coro's REST API (v1) for managing workspaces, subscriptions, tickets, devices, protected users, portal users,
    usage, audit logs, and webhooks across the Coro cybersecurity platform. OAuth 2.0 client-credentials authentication with
    a per-request Workspace header; region-specific hosts for US, Canada, and Germany.
  humanURL: https://docs.coro.net/developer-portal/
  baseURL: https://api.secure.coro.net
  properties:
  - type: Documentation
    url: https://docs.coro.net/developer-portal/
  - type: Authentication
    url: authentication/coro-authentication.yml
  - type: ChangeLog
    url: changelog/coro-changelog.yml
  - type: Webhooks
    url: asyncapi/coro-webhooks.yml
  - type: MCPServer
    url: mcp/coro-mcp.yml
  - type: Conventions
    url: conventions/coro-conventions.yml
  - type: DataModel
    url: data-model/coro-data-model.yml
  - type: Lifecycle
    url: lifecycle/coro-lifecycle.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/coro-plans-pricing.yml
- url: https://www.coro.net/feed
  type: BlogRSS
- type: Website
  url: https://www.coro.net/
- type: DeveloperPortal
  url: https://docs.coro.net/developer-portal/
- type: Documentation
  url: https://docs.coro.net/
- type: GettingStarted
  url: https://docs.coro.net/developer-portal/authentication/
- type: Authentication
  url: authentication/coro-authentication.yml
- type: MCPServer
  url: mcp/coro-mcp.yml
- type: Webhooks
  url: asyncapi/coro-webhooks.yml
- type: ChangeLog
  url: changelog/coro-changelog.yml
- type: Lifecycle
  url: lifecycle/coro-lifecycle.yml
- type: Conventions
  url: conventions/coro-conventions.yml
- type: DataModel
  url: data-model/coro-data-model.yml
- type: Conformance
  url: conformance/coro-conformance.yml
- type: Compliance
  url: https://www.coro.net/compliance
- type: TrustCenter
  url: security/coro-trust-center.yml
- type: DomainSecurity
  url: security/coro-domain-security.yml
- type: WellKnown
  url: well-known/coro-well-known.yml
- type: LLMsTxt
  url: llms/coro-llms.txt
- type: Support
  url: https://docs.coro.net/
- type: Blog
  url: https://www.coro.net/blog
- type: Pricing
  url: https://www.coro.net/platform/pricing
- type: SignUp
  url: https://secure.coro.net/login
- type: Login
  url: https://secure.coro.net/login
- type: TermsOfService
  url: https://www.coro.net/legal/terms
- type: PrivacyPolicy
  url: https://www.coro.net/legal/privacy
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Coro API — frequently asked questions

Does Coro have an API?

Yes. APIs.io lists 1 API from Coro, including Coro Public REST API.

How do I authenticate with the Coro API?

Coro documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Coro Authentication.

How much does the Coro API cost?

APIs.io lists 4 pricing plans for Coro, with each plan's price, limits and inclusions under Pricing Plans on this page.

Does Coro have an MCP server?

Yes. APIs.io lists 1 MCP server for Coro: Coro publishes an official, hosted MCP (Model Context Protocol) server that acts as a secure intermediary between an organization's AI tools and Coro's workspace security data. The MCP server authenti

Is the Coro API ready for AI agents?

Coro has a Kin Score of 52.1 out of 100 (developing) and an Agent Readiness score of 39.4 (agent-ready), scored by API Evangelist on 2026-10-31.

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/coro"

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.