CoroNet

Coro (CoroNet) is a cybersecurity company delivering a unified, AI-native security platform for lean IT teams, growing organizations, and managed service providers (MSPs). A single platform and dashboard consolidate endpoint protection, email protection, network protection (ZTNA/VPN), cloud app security, data governance, and security awareness training. The Coro Public API lets service providers and developers build applications that integrate with the platform: it is organized around workspaces (regular, channel, and child tenants) and exposes endpoints for managing workspaces, subscriptions, portal users, protected users and devices, device licensing, tickets, audit logs, and usage. Authentication uses OAuth2 client-credential pairs exchanged for a 24-hour bearer token, and Coro publishes a webhook surface with HMAC-signed events for billing and workspace automation.

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

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

CoroNet’s developer surface includes documentation, API reference, getting-started guide, changelog, engineering blog, pricing, signup flow, and 19 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

50.3/100 developing ▲ 6.3 Agent 17/100 agent aware saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

AccessSelf serve

1 API

Company Enterprise Cybersecurity Security Endpoint Security Email Security Network Security Cloud Security Managed Service Providers Compliance Webhook

Kin Score

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

Composite quality — 50.3/100 · developing

Contract Quality 8.4 / 21

Developer Ergonomics 9.7 / 17

Access Clarity 13.0 / 17

Operational Transparency 4.4 / 11

Contract Governance 0.5 / 10

Discoverability 5.6 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 17/100 · agent aware

Machine-Readable Contract 18 / 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 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 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

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

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
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)

10 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.6 — up to +15.1 composite points
Contract Governance scores 4.5 — up to +11.5 composite points
Developer Ergonomics scores 57.1 — up to +8.6 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/coronet/apis.yml: open an issue on github.com/api-evangelist/coronet 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 API

The Coro Public API enables service providers and developers to build applications that integrate with the Coro Cybersecurity platform. Organized around workspaces (regular, cha...

Pricing Plans 1

Published pricing tiers and plan structures.

Coronet Plans Pricing

4 plans

PLANS

FinOps 1

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

Coronet Finops

FINOPS

Event Specifications 1

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

Coro Public API Webhooks

Coro sends real-time, HMAC-signed webhook events to a subscriber-configured URL over HTTP POST (JSON), facilitating automation for billing and workspace management. This documen...

ASYNCAPI

Security Posture 2

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

Coronet Authentication

oauth2 · 1 scheme

SECURITY

Coronet Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

AsyncAPI

AsyncAPI

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

Webhooks

Lifecycle

Conformance

DataModel

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 4

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

StatusPage

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: coronet
name: CoroNet
description: 'Coro (CoroNet) is a cybersecurity company delivering a unified, AI-native security platform for lean IT teams,
  growing organizations, and managed service providers (MSPs). A single platform and dashboard consolidate endpoint protection,
  email protection, network protection (ZTNA/VPN), cloud app security, data governance, and security awareness training. The
  Coro Public API lets service providers and developers build applications that integrate with the platform: it is organized
  around workspaces (regular, channel, and child tenants) and exposes endpoints for managing workspaces, subscriptions, portal
  users, protected users and devices, device licensing, tickets, audit logs, and usage. Authentication uses OAuth2 client-credential
  pairs exchanged for a 24-hour bearer token, and Coro publishes a webhook surface with HMAC-signed events for billing and
  workspace automation.'
url: https://raw.githubusercontent.com/api-evangelist/coronet/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- kleiner-perkins
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
- Enterprise
- Cybersecurity
- Security
- Endpoint Security
- Email Security
- Network Security
- Cloud Security
- Managed Service Providers
- Compliance
- Webhook
tags_raw:
- Company
- Enterprise
- Cybersecurity
- Security
- Endpoint Security
- Email Security
- Network Security
- Cloud Security
- Managed Service Providers
- Compliance
- Webhooks
- API
apis:
- name: Coro Public API
  description: The Coro Public API enables service providers and developers to build applications that integrate with the
    Coro Cybersecurity platform. Organized around workspaces (regular, channel, child), it covers workspace lifecycle, subscriptions,
    portal users, protected users and devices, device licensing, tickets, audit logs, and usage, with an HMAC-signed webhook
    event surface.
  humanURL: https://docs.coro.net/developer-portal/
  baseURL: https://api.secure.coro.net
  tags:
  - Cybersecurity
  - Workspace
  - MSP
  - Webhook
  tags_raw:
  - Cybersecurity
  - Workspaces
  - MSP
  - Webhooks
  properties:
  - type: Documentation
    url: https://docs.coro.net/developer-portal/
  - type: Authentication
    url: https://docs.coro.net/developer-portal/authentication
  - type: Authentication
    url: authentication/coronet-authentication.yml
  - type: Conventions
    url: conventions/coronet-conventions.yml
  - type: Webhooks
    url: https://docs.coro.net/developer-portal/what-is-webhook
  - type: Webhooks
    url: asyncapi/coronet-webhooks-asyncapi.yml
  - type: AsyncAPI
    url: asyncapi/coronet-webhooks-asyncapi.yml
  - type: ChangeLog
    url: changelog/coronet-changelog.yml
  - type: Lifecycle
    url: lifecycle/coronet-lifecycle.yml
  - type: Conformance
    url: conformance/coronet-conformance.yml
  - type: DataModel
    url: data-model/coronet-data-model.yml
  - type: X-MCPServerCandidate
    url: mcp/coronet-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/coronet-plans-pricing.yml
- url: https://www.coro.net/feed
  type: BlogRSS
- type: DomainSecurity
  url: security/coronet-domain-security.yml
- type: Website
  url: https://www.coro.net
- type: DeveloperPortal
  url: https://docs.coro.net/developer-portal/
- type: Documentation
  url: https://docs.coro.net/
- type: APIReference
  url: https://docs.coro.net/developer-portal/
- type: GettingStarted
  url: https://docs.coro.net/developer-portal/what-is-api
- type: ChangeLog
  url: https://docs.coro.net/developer-portal/changelog
- type: ChangeLog
  url: changelog/coronet-changelog.yml
- type: StatusPage
  url: https://coro.statuspage.io
- type: Blog
  url: https://www.coro.net/blog
- type: Pricing
  url: https://www.coro.net/pricing
- type: SignUp
  url: https://secure.coro.net
- type: Support
  url: https://www.coro.net/contact
- type: TermsOfService
  url: https://www.coro.net/terms
- type: PrivacyPolicy
  url: https://www.coro.net/privacy
- type: LLMsTxt
  url: llms/coronet-llms.txt
- type: Authentication
  url: authentication/coronet-authentication.yml
- type: Conventions
  url: conventions/coronet-conventions.yml
- type: Webhooks
  url: asyncapi/coronet-webhooks-asyncapi.yml
- type: AsyncAPI
  url: asyncapi/coronet-webhooks-asyncapi.yml
- type: Lifecycle
  url: lifecycle/coronet-lifecycle.yml
- type: Conformance
  url: conformance/coronet-conformance.yml
- type: DataModel
  url: data-model/coronet-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/coronet-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

CoroNet API — frequently asked questions

Does CoroNet have an API?

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

How do I authenticate with the CoroNet API?

CoroNet uses bearer-token authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Coronet Authentication.

How much does the CoroNet API cost?

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

Is the CoroNet API ready for AI agents?

CoroNet has a Kin Score of 50.3 out of 100 (developing) and an Agent Readiness score of 16.5 (agent-aware), 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/coronet"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/coronet/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.