LevelBlue website screenshot

LevelBlue

LevelBlue is a pure-play managed security service provider (MSSP), formed from AT&T Cybersecurity and the AlienVault platform it acquired, delivering managed detection and response, managed cloud and network security, incident readiness and response, cyber advisory, exposure management and email security, backed by SpiderLabs threat intelligence. Its developer surface is the USM Anywhere v2.0 REST API — a per-tenant, OAuth 2.0 client-credentials API over alarms and normalized security events, with HAL pagination and a webhook connector for pushing third-party events into the platform — alongside the LevelBlue Open Threat Exchange (OTX) DirectConnect API for community threat intelligence.

LevelBlue publishes 4 API contracts indexed on the APIs.io network, including Alarms API, Events API, O Auth API, and 1 more. Tagged areas include Company, Enterprise, Cybersecurity, Security, and Threat Intelligence.

The LevelBlue catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

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

51.8/100 developing ▬ flat Agent 28/100 agent aware Front door AI 3/6 light Heartbeat 50/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessEnterprise
1 published contract 2 Agent Skills
CompanyEnterpriseCybersecuritySecurityThreat IntelligenceManaged SecuritySIEMThreat DetectionIncident ResponseCompliance

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
AlarmsEvents
GET /alarms GET /alarms/{alarmId} GET /events GET /events/{eventId}

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
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. Kin Score badge preview for LevelBlue It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/levelblue/"><img src="https://apis.io/badge/levelblue/card.svg" alt="LevelBlue 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
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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/levelblue/apis.yml: open an issue on github.com/api-evangelist/levelblue 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.

measured — observed by APIs.io (published)

APIs 4

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

LevelBlue Open Threat Exchange (OTX) DirectConnect API

The OTX DirectConnect API provides programmatic access to the LevelBlue Open Threat Exchange, an open community threat-intelligence platform. It exposes indicators (IPs, domains...

LevelBlue Alarms API

Endpoints for managing and searching alarm messages.

LevelBlue Events API

Endpoints for managing and searching events.

LevelBlue O Auth API

Endpoint for OAuth 2.0 functionality.

Open Collections 3

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

Agent Skills 2

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

LevelBlue API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

FinOps 1

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

Event Specifications 1

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

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LevelBlue API Rules

52 rules · 49 errors 1 warnings 2 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.

Levelblue Usm Anywhere Overlay

11 actions · documentation · levelblue-usm-anywhere-openapi.yml

DERIVED

Security Posture 3

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

Levelblue Authentication

http · 2 schemes

SECURITY

Levelblue Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Levelblue Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Levelblue Scopes

3 scopes

3 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 6

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: levelblue
name: LevelBlue
description: LevelBlue is a pure-play managed security service provider (MSSP), formed from AT&T Cybersecurity and the AlienVault
  platform it acquired, delivering managed detection and response, managed cloud and network security, incident readiness
  and response, cyber advisory, exposure management and email security, backed by SpiderLabs threat intelligence. Its developer
  surface is the USM Anywhere v2.0 REST API — a per-tenant, OAuth 2.0 client-credentials API over alarms and normalized security
  events, with HAL pagination and a webhook connector for pushing third-party events into the platform — alongside the LevelBlue
  Open Threat Exchange (OTX) DirectConnect API for community threat intelligence.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.levelblue.com/hubfs/lb-web/social/metadata.jpg
url: https://raw.githubusercontent.com/api-evangelist/levelblue/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- softbank-vision-fund
x-tier: profiled
x-tier-reason: real-openapi-harvested
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
x-docs-hosting: vercel
tags:
- Company
- Enterprise
- Cybersecurity
- Security
- Threat Intelligence
- Managed Security
- SIEM
- Threat Detection
- Incident Response
- Compliance
apis:
- name: LevelBlue Open Threat Exchange (OTX) DirectConnect API
  description: The OTX DirectConnect API provides programmatic access to the LevelBlue Open Threat Exchange, an open community
    threat-intelligence platform. It exposes indicators (IPs, domains, hostnames, file hashes, URLs, CVEs, NIDS), pulses (curated
    collections of related indicators with tags, TLP levels and targeted countries), keyword search over users and pulses,
    and user subscription management. Access is by API key, validated against the users/me endpoint.
  humanURL: https://otx.alienvault.com/assets/static/external_api.html
  baseURL: https://otx.alienvault.com/api/v1
  tags:
  - Threat Intelligence
  - Indicators of Compromise
  - Security
  properties:
  - type: Documentation
    url: https://otx.alienvault.com/assets/static/external_api.html
  - type: Portal
    url: https://otx.alienvault.com/
- aid: levelblue:levelblue-alarms-api
  name: LevelBlue Alarms API
  description: Endpoints for managing and searching alarm messages.
  humanURL: https://docs.levelblue.com/documentation/usm-anywhere/user-guide/user-management/api-clients
  baseURL: https://your-subdomain.alienvault.cloud/api/2.0
  tags:
  - Alarms
  properties:
  - type: OpenAPI
    url: openapi/levelblue-alarms-api-openapi.yml
  - type: APIReference
    url: https://docs.levelblue.com/api-reference/oauth/get-oauth-token
  - type: Webhooks
    url: asyncapi/levelblue-usm-anywhere-webhooks.yml
  - type: DataModel
    url: data-model/levelblue-data-model.yml
- aid: levelblue:levelblue-events-api
  name: LevelBlue Events API
  description: Endpoints for managing and searching events.
  humanURL: https://docs.levelblue.com/documentation/usm-anywhere/user-guide/user-management/api-clients
  baseURL: https://your-subdomain.alienvault.cloud/api/2.0
  tags:
  - Event
  tags_raw:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/levelblue-events-api-openapi.yml
  - type: APIReference
    url: https://docs.levelblue.com/api-reference/oauth/get-oauth-token
  - type: Webhooks
    url: asyncapi/levelblue-usm-anywhere-webhooks.yml
  - type: DataModel
    url: data-model/levelblue-data-model.yml
- aid: levelblue:levelblue-oauth-api
  name: LevelBlue O Auth API
  description: Endpoint for OAuth 2.0 functionality.
  humanURL: https://otx.alienvault.com/assets/static/external_api.html
  baseURL: https://otx.alienvault.com/api/v1
  tags:
  - OAuth
  - Authentication
  tags_raw:
  - OAuth
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/levelblue-oauth-api-openapi.yml
  - type: APIReference
    url: https://docs.levelblue.com/api-reference/oauth/get-oauth-token
  - type: Webhooks
    url: asyncapi/levelblue-usm-anywhere-webhooks.yml
  - type: DataModel
    url: data-model/levelblue-data-model.yml
common:
- type: Plans
  url: plans/levelblue-plans-pricing.yml
- url: https://www.levelblue.com/blogs/levelblue-blog/rss.xml
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/levelblue-capability-edges.yml
  name: LevelBlue Business Capability Map
- type: Website
  url: https://www.levelblue.com/
- type: X-MCPServerCandidate
  url: mcp/levelblue-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/levelblue-usm-anywhere-overlay.yaml
- type: DeveloperPortal
  url: https://docs.levelblue.com/documentation
- type: Documentation
  url: https://docs.levelblue.com/documentation
- type: APIReference
  url: https://docs.levelblue.com/api-reference/oauth/get-oauth-token
- type: GettingStarted
  url: https://docs.levelblue.com/documentation/usm-anywhere/user-guide/user-management/api-clients
- type: Support
  url: https://www.levelblue.com/company/support
- type: HelpCenter
  url: https://success.levelblue.com/s/
- type: Blog
  url: https://www.levelblue.com/blogs/levelblue-blog
- type: GitHubOrganization
  url: https://github.com/AlienVault-OTX
- type: Pricing
  url: https://www.levelblue.com/pricing
- type: TermsOfService
  url: https://www.levelblue.com/legal/website-terms-of-use
- type: PrivacyPolicy
  url: https://www.levelblue.com/legal/privacy-policy
- type: StatusPage
  url: https://status.alienvault.cloud/
- type: Security
  url: https://docs.levelblue.com/documentation/how-to-submit-a-security-issue
- type: VulnerabilityDisclosure
  url: security/levelblue-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/levelblue-domain-security.yml
- type: SecurityTxt
  url: well-known/levelblue-security.txt
- type: WellKnown
  url: well-known/levelblue-well-known.yml
- type: LLMsTxt
  url: llms/levelblue-llms.txt
- type: Packages
  url: packages/levelblue-packages.yml
- type: SDKs
  url: packages/levelblue-packages.yml
- type: Authentication
  url: authentication/levelblue-authentication.yml
- type: OAuthScopes
  url: scopes/levelblue-scopes.yml
- type: Conventions
  url: conventions/levelblue-conventions.yml
- type: ErrorCatalog
  url: errors/levelblue-problem-types.yml
- type: Lifecycle
  url: lifecycle/levelblue-lifecycle.yml
- type: ChangeLog
  url: changelog/levelblue-changelog.yml
- type: Conformance
  url: conformance/levelblue-conformance.yml
- type: DataModel
  url: data-model/levelblue-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Webhooks
  url: asyncapi/levelblue-usm-anywhere-webhooks.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

LevelBlue API — frequently asked questions

Does LevelBlue have an API?

Yes. APIs.io lists 4 APIs from LevelBlue, including LevelBlue Open Threat Exchange (OTX) DirectConnect API, LevelBlue Alarms API and LevelBlue Events API, and 1 more.

Is there an OpenAPI specification for the LevelBlue API?

Yes. APIs.io indexes 3 OpenAPI specifications for LevelBlue, each linked for download from this page.

How do I authenticate with the LevelBlue API?

LevelBlue uses bearer-token authentication (http · 2 schemes). The details are profiled on APIs.io as Levelblue Authentication.

Is the LevelBlue API ready for AI agents?

LevelBlue has a Kin Score of 51.8 out of 100 (developing) and an Agent Readiness score of 28.0 (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/levelblue"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/levelblue/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/levelblue/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.

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