Sirveil Exposure Verification API

Sirveil verifies personal-data exposure on a named domain and returns evidence, not an opinion.

POST /api/v1/verify takes an identity and a domain and returns a verdict in about a second. The verdict has three states, not two: indexed, not_indexed, and indeterminate. "We could not tell" is a first-class answer and is never disguised as a clean negative.

Every response carries the evidence inline - source URL, page title, snippet, and retrieval timestamp - along with a calibrated probability and the linkage strength behind it.

POST /api/v1/scan runs a full exposure sweep for one identity across the broker registry. Scans take minutes rather than seconds, so the endpoint supports an asynchronous job contract: submit, receive a job id, and poll for the shaped result.

Reproducible and versioned. Pipeline, linkage-weight and calibration versions ride on every response, including every error. Any historical answer can be replayed against the exact logic that produced it. That is the audit artifact regulated buyers ask for.

The limits of the method are published in the response. A negative comes with the boundary of what that negative is worth, as a contract field, so an engineer knows what they are relying on without reading a blog post.

Coverage is your list, not ours. Verification is domain-addressed: you name the site. There is no waiting on a roadmap for a domain to be added.

Spend ceilings, not surprise invoices. Every account carries a hard USD ceiling enforced server-side. A runaway integration stops rather than compounding.

Built for agents as well as engineers. A read-only MCP server ships alongside REST, so AI agents can call the API natively. OpenAPI 3.1 and Postman artifacts are generated from the live spec.

All API traffic is encrypted in transit. Requests are authenticated with a bearer API key scoped to your account. A synchronous verification does not persist the identity submitted to it; an asynchronous scan job retains its result for 24 hours so that the job can be polled, and expires after that. Every response, including every error, carries the version stamps that produced it, so any call can be reproduced on request.

1. Subscribe through AWS Marketplace and choose Set up your account.
2. AWS returns you to the Sirveil registration page. Enter the email address that should own the account.
3. Your API key is issued on that page, and your subscription status stays visible in your key console.
4. Call POST /api/v1/verify with an identity and a domain to get your first verdict.
5. Read the response: verdict, evidence URL, snippet, calibrated probability and version stamps.

Documentation, the OpenAPI 3.1 specification and a generated Postman collection are published at https://ai.sirveil.ai/docs/api 

• Privacy and removal vendors needing independent before-and-after proof from a party that is not grading its own homework.
• Digital executive protection teams running per-principal checks on the domains that matter.
• Identity, fraud and KYC platforms treating exposure as a risk signal.
• Cyber and identity insurers who need underwriting and claims evidence with a timestamp and a reproducible method.

Metered per call. Verification is billed at $0.10 per call; a full scan is billed at $0.35 per scan. You pay for what you use, with no minimum commitment, billed through your AWS account.