Cytora website screenshot

Cytora

Cytora is a London-headquartered insurtech, founded in 2012 as a University of Cambridge spinout, that sells a digital risk processing platform to commercial insurers, wholesale brokers, MGAs and reinsurers. Its software ingests inbound submissions arriving as email, PDF, spreadsheet and broker API payloads, digitises them against pre-built line-of-business schemas (property, commercial combined, construction, cyber, fleet, general liability, professional liability, D&O, E&O, management liability), augments them from a data ecosystem of roughly sixty third-party risk-data partners, evaluates them against appetite and priority rules, and routes them into downstream underwriting and claims systems. Use cases span new business, renewals, mid-term adjustments, claims FNOL and post-FNOL intake, and facultative and treaty reinsurance submissions. Named customers include Zurich, Chubb, Markel, Beazley, Travelers, Tokio Marine, Ecclesiastical, Arch, Everest and TransRe. Applied Systems acquired Cytora in September 2025. Its API posture is partner-gated and enterprise-only: Cytora runs a real production API gateway at api.cytora.com and a real ReadMe-hosted API reference at docs.cytora.com, but the documentation site is entirely password-protected (HTTP 302 to a password wall, robots.txt Disallow) and the gateway resets anonymous TLS connections. There is no self-serve developer signup, no public OpenAPI, no public Postman collection and no published webhook or event catalog. The only externally verifiable technical surface is the Auth0 OIDC discovery document at auth.cytora.com, which confirms OAuth 2.0 client-credentials and authorization-code flows for provisioned partner integrations. The United Kingdom home market has no open-insurance mandate, so nothing compels Cytora to expose any of this publicly.

Cytora publishes 2 APIs on the APIs.io network. Tagged areas include Insurance, United Kingdom, Insurtech, Commercial Insurance, and Underwriting.

Cytora’s developer surface includes documentation, engineering blog, authentication, support, and 21 more developer resources.

33.1/100 thin ▬ flat Agent 14/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
2 APIs
InsuranceUnited KingdomInsurtechCommercial InsuranceUnderwritingClaimsRisk DataProperty and CasualtyReinsuranceBrokerSubmission IntakeDocument AI

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 33.1/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 5.2 / 20
Commercial Clarity 7.9 / 20
Operational Transparency 2.7 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 14/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
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/cytora: 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 2

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

Cytora Platform API

Cytora's production REST API for digital risk processing — the "preferred method" of submission intake described in its own Risk Flow Academy. The gateway is real (api.cytora.co...

Cytora Identity (Auth0 OIDC)

The OAuth 2.0 / OpenID Connect authorization server that fronts every Cytora integration, running on an Auth0 EU tenant (cytora-prod.eu.auth0.com). This is the only Cytora surfa...

Security Posture 3

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

Cytora Authentication

oauth2/openIdConnect · 2 schemes

SECURITY

Cytora Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Cytora Trust Center

ISO/IEC 27001:2022, ISO/IEC 27001:2013, ISO/IEC 42001:2023

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Cytora Scopes

14 scopes · clientCredentials/authorizationCode

14 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 7

Authentication, authorization, and security posture

Scroll for all 7

Operate 2

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: cytora
url: https://raw.githubusercontent.com/api-evangelist/cytora/refs/heads/main/apis.yml
name: Cytora
kind: company
description: 'Cytora is a London-headquartered insurtech, founded in 2012 as a University of Cambridge spinout, that sells
  a digital risk processing platform to commercial insurers, wholesale brokers, MGAs and reinsurers. Its software ingests
  inbound submissions arriving as email, PDF, spreadsheet and broker API payloads, digitises them against pre-built line-of-business
  schemas (property, commercial combined, construction, cyber, fleet, general liability, professional liability, D&O, E&O,
  management liability), augments them from a data ecosystem of roughly sixty third-party risk-data partners, evaluates them
  against appetite and priority rules, and routes them into downstream underwriting and claims systems. Use cases span new
  business, renewals, mid-term adjustments, claims FNOL and post-FNOL intake, and facultative and treaty reinsurance submissions.
  Named customers include Zurich, Chubb, Markel, Beazley, Travelers, Tokio Marine, Ecclesiastical, Arch, Everest and TransRe.
  Applied Systems acquired Cytora in September 2025. Its API posture is partner-gated and enterprise-only: Cytora runs a real
  production API gateway at api.cytora.com and a real ReadMe-hosted API reference at docs.cytora.com, but the documentation
  site is entirely password-protected (HTTP 302 to a password wall, robots.txt Disallow) and the gateway resets anonymous
  TLS connections. There is no self-serve developer signup, no public OpenAPI, no public Postman collection and no published
  webhook or event catalog. The only externally verifiable technical surface is the Auth0 OIDC discovery document at auth.cytora.com,
  which confirms OAuth 2.0 client-credentials and authorization-code flows for provisioned partner integrations. The United
  Kingdom home market has no open-insurance mandate, so nothing compels Cytora to expose any of this publicly.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Insurance
- United Kingdom
- Insurtech
- Commercial Insurance
- Underwriting
- Claims
- Risk Data
- Property and Casualty
- Reinsurance
- Broker
- Submission Intake
- Document AI
created: '2026-07-25'
modified: '2026-07-25'
specificationVersion: '0.19'
apis:
- name: Cytora Platform API
  description: 'Cytora''s production REST API for digital risk processing — the "preferred method" of submission intake described
    in its own Risk Flow Academy. The gateway is real (api.cytora.com resolves via gateway.cytora-prod.com to a Google Cloud
    load balancer) and the API reference is real (a ReadMe site at docs.cytora.com), but both are closed: the documentation
    host 302-redirects every path to a password wall and the gateway resets the TLS handshake for anonymous clients. No OpenAPI,
    SDK, Postman collection or webhook catalog is published. Access is provisioned per contract via OAuth 2.0 client credentials
    issued by Cytora''s Auth0 tenant. The resource surface observed in Cytora''s own published Risk Console client (workspaces,
    inboxes, records, documents, extractors, transactions, deployments) is captured in conventions/cytora-conventions.yml
    for discovery only.'
  humanURL: https://docs.cytora.com/
  baseURL: https://api.cytora.com
  tags:
  - Insurance
  - Underwriting
  - Claims
  - Submission Intake
  - Document AI
  properties:
  - type: Documentation
    url: https://docs.cytora.com/
  - type: Authentication
    url: authentication/cytora-authentication.yml
  - type: Conventions
    url: conventions/cytora-conventions.yml
  - type: Lifecycle
    url: lifecycle/cytora-lifecycle.yml
- name: Cytora Identity (Auth0 OIDC)
  description: 'The OAuth 2.0 / OpenID Connect authorization server that fronts every Cytora integration, running on an Auth0
    EU tenant (cytora-prod.eu.auth0.com). This is the only Cytora surface that answers anonymously with real machine-readable
    data: OpenID Connect Discovery, RFC 8414 authorization server metadata and JWKS all return 200. It advertises client_credentials
    for machine-to-machine partner integrations, authorization_code with PKCE (S256) for the Risk Console, token exchange,
    JWT bearer and device code grants, private_key_jwt client authentication and DPoP (ES256). Only stock OIDC identity scopes
    are advertised; product scopes are not published.'
  humanURL: https://auth.cytora.com/.well-known/openid-configuration
  baseURL: https://auth.cytora.com
  tags:
  - OAuth
  - OpenID Connect
  - Identity
  properties:
  - type: Authentication
    url: authentication/cytora-authentication.yml
  - type: OAuthScopes
    url: scopes/cytora-scopes.yml
  - type: WellKnown
    url: well-known/cytora-well-known.yml
  - type: OpenIDConnect
    url: https://auth.cytora.com/.well-known/openid-configuration
common:
- type: DomainSecurity
  url: security/cytora-domain-security.yml
- type: Website
  url: https://cytora.com/
- type: Documentation
  url: https://docs.cytora.com/
- type: Blog
  url: https://cytora.com/risk-flow-center/blog
- type: StatusPage
  url: https://status.cytora.com/
- type: Lifecycle
  url: lifecycle/cytora-lifecycle.yml
- type: TrustCenter
  url: https://trust.cytora.com/
- type: TrustCenter
  url: security/cytora-trust-center.yml
- type: Compliance
  url: https://trust.cytora.com/
- type: Conformance
  url: conformance/cytora-conformance.yml
- type: Authentication
  url: https://auth.cytora.com/.well-known/openid-configuration
- type: Authentication
  url: authentication/cytora-authentication.yml
- type: OAuthScopes
  url: scopes/cytora-scopes.yml
- type: WellKnown
  url: well-known/cytora-well-known.yml
- type: Conventions
  url: conventions/cytora-conventions.yml
- type: LLMsTxt
  url: llms/cytora-llms.txt
- type: Login
  url: https://uwp.cytora.com
- type: GitHubOrganization
  url: https://github.com/cytora
- type: LinkedIn
  url: https://www.linkedin.com/company/cytora
- type: Twitter
  url: https://twitter.com/cytora
- type: PrivacyPolicy
  url: https://cytora.com/privacy-policy
- type: CookiePolicy
  url: https://cytora.com/cookie-policy
- type: Support
  url: https://cytora.com/about-us/contact-us
- type: Customers
  url: https://cytora.com/customers
- type: Partners
  url: https://cytora.com/digital-risk-processing/data-ecosystem
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com