Coro website screenshot

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 publishes 1 API on the APIs.io network. Tagged areas include Company, Cybersecurity, Security, Endpoint Protection, 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 17 more developer resources.

43.0/100 developing ▬ flat Agent 36/100 agent ready saas Full breakdown ↓
scored 2026-08-30 · rubric v0.17.2
AccessSelf serve
1 APIs 1 MCP Servers
CompanyCybersecuritySecurityEndpoint ProtectionEmail SecurityCloud SecurityData ProtectionMSPWebhookMCP

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-30 · rubric v0.17.2
Composite quality — 43.0/100 · developing
Contract Quality 10.7 / 25
Developer Ergonomics 10.0 / 20
Access Clarity 9.5 / 20
Operational Transparency 3.1 / 13
Contract Governance 2.2 / 12
Discoverability 7.6 / 10
Agent readiness — 36/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 0 / 5
Registration Without a Human 6 / 6
Agentic Commerce Surface 0 / 5
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/coro: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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

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

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Access & Security 4

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

Source (apis.yml)

apis.yml Raw ↑
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-07-18'
image: https://www.coro.net/wp-content/uploads/coro-opengraph.png
tags:
- Company
- Cybersecurity
- Security
- Endpoint Protection
- 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: 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

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 email required.

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