How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SpyCloud

SpyCloud is an Austin, Texas based identity threat protection company that operates one of the largest repositories of recaptured darknet data — breach records, infostealer malware logs, phishing captures and combolists — and exposes it programmatically through a family of high-volume REST APIs. Security, fraud, identity and investigations teams query recaptured credentials, session cookies, exposed PII and infected-device telemetry to prevent account takeover, ransomware, session hijacking and online fraud. The public API surface spans nine separately-licensed products: Enterprise (Employee) ATO Prevention, Consumer ATO Prevention, Cybercrime Investigations, Data Partnership, IDLink identity correlation, Compromised Credit Card, Prospecting, NIST Password check, and Session Identity Protection. All are REST/JSON, authenticated with an x-api-key header, IP allow-listed, cursor-paginated at 1,000 records per page, and backed by a 99.9% uptime SLA.

agent ready

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles SpyCloud the way a machine reads it — 22 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — SpyCloud scores 54.0/100 (developing), with a separate agent-readiness read of 51/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 54.0/100 · developing
Contract Quality 14.6 / 25
Developer Ergonomics 11.2 / 20
Commercial Clarity 12.1 / 20
Operational Transparency 5.5 / 13
Governance 1.4 / 12
Discoverability 9.3 / 10
Agent readiness — 51/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract derived 2.5 / 10
MCP Server derived 3.0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics documented 4.0 / 8
Request/Response Examples 7.0 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface 0 / 6
Agent Skills derived 1.3 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
SpyCloud Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from SpyCloud's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/spycloud/"
   title="SpyCloud on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/spycloud.svg"
       alt="SpyCloud Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile SpyCloud

Each block below is one kind of artifact we hold for SpyCloud. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 7

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

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

SpyCloud Breach API

The Breach API from SpyCloud — 23 operation(s) for breach.

SpyCloud Check API

The Check API from SpyCloud — 2 operation(s) for check.

SpyCloud Compass API

The Compass API from SpyCloud — 5 operation(s) for compass.

SpyCloud Data API

The Data API from SpyCloud — 2 operation(s) for data.

SpyCloud Query API

The Query API from SpyCloud — 3 operation(s) for query.

SpyCloud Stats API

The Stats API from SpyCloud — 2 operation(s) for stats.

SpyCloud Watchlist API

The Watchlist API from SpyCloud — 5 operation(s) for watchlist.

Scroll within the panel for all 7 ·

Open Collections 8

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

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

Scroll within the panel for all 8 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

spycloud-mcp.yml

MCP SERVER

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Spycloud Rate Limits

0 limits

RATE LIMITS

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Spycloud Authentication

apiKey · 2 schemes

SECURITY

Spycloud Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Spycloud Vulnerability Disclosure

security.txt · contact published

SECURITY

Spycloud Trust Center

SOC 2, ISO 27001

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

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

Spycloud Agentic Access

69 operations · 2 acting

69 operations · 2 acting

AGENTIC

Resources

Every other property we hold for SpyCloud — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 2

Reference material describing how the API behaves

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/spycloud · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of SpyCloud, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.