Ocean Security

Ocean Security (Ocean) is an AI-native, agentic email security platform that stops targeted, AI-powered email attacks that surface-level detection tools miss. At its core is Ray, an autonomous investigation engine that reviews every inbound email in real time — checking the sender, content, links, technical infrastructure, and business context to decide whether a message can be trusted — enabling enterprises to stop phishing, business email compromise (BEC), impersonation, and financial fraud. The platform pairs deep email investigation with autonomous SOC triage and real-time employee inbox guidance. Ocean's REST API gives security teams programmatic access to detected threats, phishing reports (SONAR), allow/deny list settings, and ROI/security metrics such as hours saved and financial loss prevented. Founded in Israel and backed by Lightspeed Venture Partners, Ocean protects hundreds of thousands of mailboxes across Global Fortune 500 organizations.

Ocean Security publishes 4 API contracts indexed on the APIs.io network, including Metrics API, Settings API, Sonar API, and 1 more. Tagged areas include Company, Security, Email Security, Cybersecurity, and Phishing.

The Ocean Security catalog on APIs.io includes 1 Spectral governance ruleset.

Ocean Security’s developer surface includes documentation, API reference, getting-started guide, engineering blog, signup flow, authentication, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.5/100 thin ▬ flat Agent 25/100 agent aware Front door AI 5/6 prominent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 4 Agent Skills

Company Security Email Security Cybersecurity Phishing Threat Detection Email Anti-Phishing Artificial Intelligence Threat Intelligence

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Cybersecurity Management

BC-620

MetricsSonarThreats

GET /api/v1/threats GET /api/v1/sonar/phishing-reports/aggs/mttr GET /api/v1/sonar/phishing-reports GET /api/v1/metrics/threats_over_time

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 38.5/100 · thin

Contract Quality 9.9 / 19

Developer Ergonomics 6.3 / 15

Access Clarity 5.1 / 15

Operational Transparency 0.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 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 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/ocean-security/"><img src="https://apis.io/badge/ocean-security/card.svg" alt="Ocean Security 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
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
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
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

9 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 34.2 — up to +13.2 composite points
Operational Transparency scores 0.0 — up to +13.0 composite points
Contract Quality scores 53.0 — up to +11.8 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/ocean-security/apis.yml: open an issue on github.com/api-evangelist/ocean-security 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 →

Standards implemented 1

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 4

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

Ocean Security Metrics API

Security metrics and analytics endpoints

Ocean Security Settings API

Manage tenant allow/deny list entries

Ocean Security Sonar API

Phishing report (SONAR) management and response analytics

Ocean Security Threats API

Operations for retrieving threat information

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Ocean Security Metrics API

OPEN COLLECTION

Ocean Security Metrics Settings API

OPEN COLLECTION

Ocean Security Metrics Sonar API

OPEN COLLECTION

Ocean Security Metrics Threats API

OPEN COLLECTION

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

Investigate SONAR phishing reports

AGENT SKILL

Manage the tenant allow/deny list

AGENT SKILL

Report security ROI and posture metrics

AGENT SKILL

Triage recent email threats

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Ocean Security API Rules

59 rules · 54 errors 4 warnings 1 info

SPECTRAL

OpenAPI 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.

Ocean Security Openapi Overlay

3 actions · update · ocean-security-openapi.yml

DERIVED

Security Posture 2

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

Ocean Security Authentication

apiKey · 1 scheme

SECURITY

Ocean Security Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Ocean Security Agentic Access

20 operations · 3 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

X-MCPServerCandidate

AgenticAccess

LLMsTxt

WellKnown

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Lifecycle

Lifecycle

Access & Security 3

Authentication, authorization, and security posture

TrustCenter

TrustCenter

Authentication

Authentication

DomainSecurity

DomainSecurity

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: ocean-security
name: Ocean Security
description: Ocean Security (Ocean) is an AI-native, agentic email security platform that stops targeted, AI-powered email
  attacks that surface-level detection tools miss. At its core is Ray, an autonomous investigation engine that reviews every
  inbound email in real time — checking the sender, content, links, technical infrastructure, and business context to decide
  whether a message can be trusted — enabling enterprises to stop phishing, business email compromise (BEC), impersonation,
  and financial fraud. The platform pairs deep email investigation with autonomous SOC triage and real-time employee inbox
  guidance. Ocean's REST API gives security teams programmatic access to detected threats, phishing reports (SONAR), allow/deny
  list settings, and ROI/security metrics such as hours saved and financial loss prevented. Founded in Israel and backed by
  Lightspeed Venture Partners, Ocean protects hundreds of thousands of mailboxes across Global Fortune 500 organizations.
url: https://raw.githubusercontent.com/api-evangelist/ocean-security/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- lightspeed-venture-partners
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
image: https://ocean.security/favicon.ico
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
x-docs-hosting: vercel
tags:
- Company
- Security
- Email Security
- Cybersecurity
- Phishing
- Threat Detection
- Email
- Anti-Phishing
- Artificial Intelligence
- Threat Intelligence
apis:
- aid: ocean-security:ocean-security-metrics-api
  name: Ocean Security Metrics API
  description: Security metrics and analytics endpoints
  humanURL: https://docs.ocean.security/api-reference/introduction
  baseURL: https://api.ocean.security
  tags:
  - Metrics
  properties:
  - type: OpenAPI
    url: openapi/ocean-security-metrics-api-openapi.yml
  - type: Documentation
    url: https://docs.ocean.security/api-reference/introduction
  - type: Authentication
    url: authentication/ocean-security-authentication.yml
  - type: ErrorCatalog
    url: errors/ocean-security-problem-types.yml
  - type: Conventions
    url: conventions/ocean-security-conventions.yml
  - type: DataModel
    url: data-model/ocean-security-data-model.yml
  - type: Conformance
    url: conformance/ocean-security-conformance.yml
- aid: ocean-security:ocean-security-settings-api
  name: Ocean Security Settings API
  description: Manage tenant allow/deny list entries
  humanURL: https://docs.ocean.security/api-reference/introduction
  baseURL: https://api.ocean.security
  tags:
  - Settings
  properties:
  - type: OpenAPI
    url: openapi/ocean-security-settings-api-openapi.yml
  - type: Documentation
    url: https://docs.ocean.security/api-reference/introduction
  - type: Authentication
    url: authentication/ocean-security-authentication.yml
  - type: ErrorCatalog
    url: errors/ocean-security-problem-types.yml
  - type: Conventions
    url: conventions/ocean-security-conventions.yml
  - type: DataModel
    url: data-model/ocean-security-data-model.yml
  - type: Conformance
    url: conformance/ocean-security-conformance.yml
- aid: ocean-security:ocean-security-sonar-api
  name: Ocean Security Sonar API
  description: Phishing report (SONAR) management and response analytics
  humanURL: https://docs.ocean.security/api-reference/introduction
  baseURL: https://api.ocean.security
  tags:
  - Sonar
  properties:
  - type: OpenAPI
    url: openapi/ocean-security-sonar-api-openapi.yml
  - type: Documentation
    url: https://docs.ocean.security/api-reference/introduction
  - type: Authentication
    url: authentication/ocean-security-authentication.yml
  - type: ErrorCatalog
    url: errors/ocean-security-problem-types.yml
  - type: Conventions
    url: conventions/ocean-security-conventions.yml
  - type: DataModel
    url: data-model/ocean-security-data-model.yml
  - type: Conformance
    url: conformance/ocean-security-conformance.yml
- aid: ocean-security:ocean-security-threats-api
  name: Ocean Security Threats API
  description: Operations for retrieving threat information
  humanURL: https://docs.ocean.security/api-reference/introduction
  baseURL: https://api.ocean.security
  tags:
  - Threats
  properties:
  - type: OpenAPI
    url: openapi/ocean-security-threats-api-openapi.yml
  - type: Documentation
    url: https://docs.ocean.security/api-reference/introduction
  - type: Authentication
    url: authentication/ocean-security-authentication.yml
  - type: ErrorCatalog
    url: errors/ocean-security-problem-types.yml
  - type: Conventions
    url: conventions/ocean-security-conventions.yml
  - type: DataModel
    url: data-model/ocean-security-data-model.yml
  - type: Conformance
    url: conformance/ocean-security-conformance.yml
common:
- type: CapabilityMap
  url: capabilities/ocean-security-capability-edges.yml
  name: Ocean Security Business Capability Map
- type: AgentSkill
  url: skills/ocean-security-investigate-phishing-reports.md
- type: X-MCPServerCandidate
  url: mcp/ocean-security-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.'
- type: Overlay
  url: overlays/ocean-security-openapi-overlay.yaml
- type: AgenticAccess
  url: agentic-access/ocean-security-agentic-access.yml
- type: DeveloperPortal
  url: https://docs.ocean.security/
- type: Documentation
  url: https://docs.ocean.security/api-reference/introduction
- type: APIReference
  url: https://docs.ocean.security/api-reference/introduction
- type: GettingStarted
  url: https://docs.ocean.security/documentation/getting-started
- type: Website
  url: https://ocean.security
- type: Blog
  url: https://ocean.security/resources/blog
- type: TrustCenter
  url: https://trust.ocean.security/
- type: TermsOfService
  url: https://ocean.security/legal/terms-of-use
- type: PrivacyPolicy
  url: https://ocean.security/legal/privacy-policy
- type: SignUp
  url: https://ocean.security/demo
- type: LLMsTxt
  url: llms/ocean-security-llms.txt
- type: Authentication
  url: authentication/ocean-security-authentication.yml
- type: DomainSecurity
  url: security/ocean-security-domain-security.yml
- type: Conventions
  url: conventions/ocean-security-conventions.yml
- type: Lifecycle
  url: lifecycle/ocean-security-lifecycle.yml
- type: WellKnown
  url: well-known/ocean-security-well-known.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 18
  pass: local-v1

Ocean Security API — frequently asked questions

Does Ocean Security have an API?

Yes. APIs.io lists 4 APIs from Ocean Security, including Ocean Security Metrics API, Ocean Security Settings API and Ocean Security Sonar API, and 1 more.

Is there an OpenAPI specification for the Ocean Security API?

Yes. APIs.io indexes 4 OpenAPI specifications for Ocean Security, each linked for download from this page.

How do I authenticate with the Ocean Security API?

Ocean Security uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Ocean Security Authentication.

Is the Ocean Security API ready for AI agents?

Ocean Security has a Kin Score of 38.5 out of 100 (thin) and an Agent Readiness score of 24.7 (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.

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/ocean-security"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/ocean-security/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.