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

BMC XIV Paid Check API

$1.00 USDC on Solana via x402.

BMC XIV Paid Check API is one of 3 APIs that BMC XIV publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include paid-check. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 3 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 0.1.5.

Requests are made against a single base URL, https://breach402.bmcxiv.com.

3 operations 3 paths 7 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.5
Base URL
https://breach402.bmcxiv.com
Authentication
HTTP Bearer
Contact
Breach402 security operator
Resource Areas
1

Authentication & Security 1

BMC XIV Paid Check API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (opaque-token) (bearerAuth).

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

paid-check 3

$1.00 USDC on Solana via x402.

POST
/v1/checks/prepare
Validate owner authorization before presenting a payment challenge
prepareOwnerBreachExposurePayment 1 param body → 201400404409410503
POST
/v1/checks/run
Run one exact verified-owner email breach check
runOwnerBreachExposureCheck 1 param body → 202402409
GET
/v1/checks/{check_id}
Retrieve a queued or completed sensitive breach report
getOwnerBreachExposureReport 1 param → 200404410

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are ExposureReport (16 properties), PreparedCheck (14 properties), CheckStatus (8 properties), CheckCreated (6 properties). Each schema is shown below with its type and property counts.

PrepareCheckRequest
object
2 properties 2 required
PreparedCheck
object
14 properties 10 required
RunCheckRequest
object
2 properties 2 required
CheckCreated
object
6 properties 4 required
Error
object
1 property 1 required
ExposureReport
object
Returns complete breach record objects to the verified paid customer, including credential, recovery, unknown-field, and instruction-like values when present.…
16 properties 15 required
CheckStatus
object
8 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bmcxiv-com-paid-check-api-openapi.yml Raw ↑

Other APIs BMC XIV publishes across the network.

BMC XIV Discovery API
BMC XIV Owner Verification API
Where this information came from

This is an independent, third-party profile of BMC XIV Paid Check API, 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.