Nebulock website screenshot

Nebulock

Nebulock is an agentic, contextual security-analytics platform built for hunt-first security operations. A swarm of AI agents continuously hunts across cloud, SaaS, network, endpoint, and identity telemetry, maintaining a behavioral Context Graph to surface endpoint- and identity-based threats, close detection coverage gaps, and catch human and agentic insider threats before they escalate into incidents. The platform runs hypothesis-driven investigations, writes and deploys detection rules (Sigma and scheduled SQL), retrohunts historical data, simulates attacks, and maps coverage against MITRE ATT&CK. Nebulock exposes a customer-facing public API for Findings, Entities (actors/users/hosts correlation), Hunts, hunt suggestions and reports, and detection Rules, authenticated with per-organization API keys. The company raised a $25M Series A and is backed by Bain Capital Ventures.

Nebulock publishes 4 APIs on the APIs.io network, including Entities API, Findings API, Hunts API, and 1 more. Tagged areas include Company, Security, Threat Hunting, Threat Detection, and Security Operations.

Nebulock’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, authentication, and 18 more developer resources.

🌐 Visit website 📡 Source on GitHub
29.5/100 thin ▬ flat Agent 21/100 agent aware Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs
CompanySecurityThreat HuntingThreat DetectionSecurity OperationsDetection EngineeringAI AgentsSIEM

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Composite quality — 29.5/100 · thin
Contract Quality 12.2 / 23
Developer Ergonomics 5.9 / 18
Access Clarity 1.4 / 18
Operational Transparency 0.3 / 12
Contract Governance 0.5 / 11
Discoverability 6.8 / 9
Create-or-Update Ergonomics 0.0 / 10
Agent readiness — 21/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
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.
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 github.com/api-evangelist/nebulock: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

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

Nebulock Entities API

Actors, users, and hosts — the identity/asset correlation graph.

Nebulock Findings API

Retrieve and manage security findings and their comments.

Nebulock Hunts API

Threat hunts, hunt suggestions, and hunt reports.

Nebulock Rules API

Create, validate, and run detection rules (Sigma / scheduled SQL).

Open Collections 5

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

API Collection

OPEN COLLECTION

Nebulock Public Entities API

OPEN COLLECTION

Nebulock Public Entities Findings API

OPEN COLLECTION

Nebulock Public Entities Hunts API

OPEN COLLECTION

Nebulock Public Entities Rules API

OPEN COLLECTION

Arazzo Workflows 2

Multi-step API workflows described with the Arazzo specification.

Run a Nebulock hunt and generate a report

Create a hunt, add a follow-up directive, then generate and fetch its report.

ARAZZO

Validate and deploy a Nebulock detection rule

Validate rule content, create it inactive, then activate it.

ARAZZO

Security Posture 2

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

Nebulock Authentication

apiKey · 2 schemes

SECURITY

Nebulock Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

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

Nebulock Agentic Access

55 operations · 33 acting · 1 human-in-the-loop

55 operations · 33 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted
GettingStarted

Documentation 3

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference
 OpenAPI
OpenAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess
AgenticAccess
 X-MCPServerCandidate
X-MCPServerCandidate
 LLMsTxt
LLMsTxt
 AgentSkill
AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 Conventions
Conventions
 DataModel
DataModel
 Arazzo
Arazzo
 Arazzo
Arazzo

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

TrustCenter
TrustCenter
 Authentication
Authentication
 DomainSecurity
DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support
Support

Company 3

The organization behind the API

Blog
Blog
 BlogRSS
BlogRSS
 Website
Website

Other 1

Properties that don't map to a standard resource type

Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
aid: nebulock
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  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-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/nebulock.png
name: Nebulock
description: Nebulock is an agentic, contextual security-analytics platform built for hunt-first security operations. A swarm
  of AI agents continuously hunts across cloud, SaaS, network, endpoint, and identity telemetry, maintaining a behavioral
  Context Graph to surface endpoint- and identity-based threats, close detection coverage gaps, and catch human and agentic
  insider threats before they escalate into incidents. The platform runs hypothesis-driven investigations, writes and deploys
  detection rules (Sigma and scheduled SQL), retrohunts historical data, simulates attacks, and maps coverage against MITRE
  ATT&CK. Nebulock exposes a customer-facing public API for Findings, Entities (actors/users/hosts correlation), Hunts, hunt
  suggestions and reports, and detection Rules, authenticated with per-organization API keys. The company raised a $25M Series
  A and is backed by Bain Capital Ventures.
url: https://raw.githubusercontent.com/api-evangelist/nebulock/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bain-capital-ventures
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Security
- Threat Hunting
- Threat Detection
- Security Operations
- Detection Engineering
- AI Agents
- SIEM
apis:
- aid: nebulock:nebulock-entities-api
  name: Nebulock Entities API
  description: Actors, users, and hosts — the identity/asset correlation graph.
  humanURL: https://docs.nebulock.io/reference/getting-started-with-the-nebulock-findings-api
  baseURL: https://api.nebulock.io
  tags:
  - Entities
  properties:
  - type: OpenAPI
    url: openapi/nebulock-entities-api-openapi.yml
  - type: Documentation
    url: https://docs.nebulock.io/
  - type: APIReference
    url: https://docs.nebulock.io/reference/getting-started-with-the-nebulock-findings-api
  - type: Authentication
    url: authentication/nebulock-authentication.yml
- aid: nebulock:nebulock-findings-api
  name: Nebulock Findings API
  description: Retrieve and manage security findings and their comments.
  humanURL: https://docs.nebulock.io/reference/getting-started-with-the-nebulock-findings-api
  baseURL: https://api.nebulock.io
  tags:
  - Findings
  properties:
  - type: OpenAPI
    url: openapi/nebulock-findings-api-openapi.yml
  - type: Documentation
    url: https://docs.nebulock.io/
  - type: APIReference
    url: https://docs.nebulock.io/reference/getting-started-with-the-nebulock-findings-api
  - type: Authentication
    url: authentication/nebulock-authentication.yml
- aid: nebulock:nebulock-hunts-api
  name: Nebulock Hunts API
  description: Threat hunts, hunt suggestions, and hunt reports.
  humanURL: https://docs.nebulock.io/reference/getting-started-with-the-nebulock-findings-api
  baseURL: https://api.nebulock.io
  tags:
  - Hunts
  properties:
  - type: OpenAPI
    url: openapi/nebulock-hunts-api-openapi.yml
  - type: Documentation
    url: https://docs.nebulock.io/
  - type: APIReference
    url: https://docs.nebulock.io/reference/getting-started-with-the-nebulock-findings-api
  - type: Authentication
    url: authentication/nebulock-authentication.yml
- aid: nebulock:nebulock-rules-api
  name: Nebulock Rules API
  description: Create, validate, and run detection rules (Sigma / scheduled SQL).
  humanURL: https://docs.nebulock.io/reference/getting-started-with-the-nebulock-findings-api
  baseURL: https://api.nebulock.io
  tags:
  - Rules
  properties:
  - type: OpenAPI
    url: openapi/nebulock-rules-api-openapi.yml
  - type: Documentation
    url: https://docs.nebulock.io/
  - type: APIReference
    url: https://docs.nebulock.io/reference/getting-started-with-the-nebulock-findings-api
  - type: Authentication
    url: authentication/nebulock-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Documentation
  url: https://docs.nebulock.io/
- type: APIReference
  url: https://docs.nebulock.io/reference/getting-started-with-the-nebulock-findings-api
- type: GettingStarted
  url: https://docs.nebulock.io/docs/access
- type: Blog
  url: https://nebulock.io/blog
- type: BlogRSS
  url: https://nebulock.io/blog/rss.xml
- type: GitHubOrganization
  url: https://github.com/nebulock
- type: Support
  url: https://docs.nebulock.io/docs/help
- type: TrustCenter
  url: https://trust.nebulock.io/
- type: OpenAPI
  url: openapi/_original/nebulock-openapi.yml
- type: Authentication
  url: authentication/nebulock-authentication.yml
- type: AgenticAccess
  url: agentic-access/nebulock-agentic-access.yml
- type: DomainSecurity
  url: security/nebulock-domain-security.yml
- type: X-MCPServerCandidate
  url: mcp/nebulock-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/nebulock-overlay.yaml
- type: Conformance
  url: conformance/nebulock-conformance.yml
- type: ErrorCatalog
  url: errors/nebulock-problem-types.yml
- type: Lifecycle
  url: lifecycle/nebulock-lifecycle.yml
- type: Conventions
  url: conventions/nebulock-conventions.yml
- type: DataModel
  url: data-model/nebulock-data-model.yml
- type: LLMsTxt
  url: llms/nebulock-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Arazzo
  name: Run a Nebulock hunt and generate a report
  url: arazzo/nebulock-run-hunt-and-report.yml
- type: Arazzo
  name: Validate and deploy a Nebulock detection rule
  url: arazzo/nebulock-validate-and-deploy-rule.yml
- type: Website
  url: https://nebulock.io/
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 19
  pass: local-v1

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/nebulock"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/nebulock/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/nebulock/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.