Skip to content
Vendor Evidence Drift

Vendor trust center change monitoring API

Monitor vendor trust-center changes from supplied evidence

Capture evidence through your approved process, then compare the prior and current states. Vendor Evidence Drift returns auditable changes and control impact.

Run the keyless demo Create a sandbox key
Customer-supplied input No key for the demo No card for a sandbox account

Exact use case

A vendor updates certification scope, subprocessors, residency, policy content, insurance, or service levels after the original review.

Input you provide

Two customer-supplied vendor evidence states with certifications, subprocessors, policies, SLAs, residency, attestations, and capture dates.

Output you receive

Stable drift codes, severity, evidence, affected controls, risk contribution, and a completed change assessment.

What the API does

Compares supplied evidence states and makes each drift finding auditable.

Authenticated first value

A successful authenticated POST /v1/checks that returns evidence drift, control impact, and risk output.

OpenAPI-grounded keyless demo

Check the evidence

Edit the supplied example, send it to /v1/demo/check, and inspect the service’s unedited JSON response. The demo stores nothing and consumes no account quota.

Request body Ready

This sample matches the published request contract for /v1/demo/check. Do not paste secrets or personal data.

Response
Run the demo to see the API response.

A successful response demonstrates the bounded classification or calculation shown here. It is not evidence of a deployed connector, autonomous external action, customer outcome, or commercial performance.

Capability boundary

What this page does not promise

It does not crawl trust centers, supply continuous external data, provide a full TPRM workflow, scan attack surface, or issue a cyber rating.

  • The demo qualifies the transformation only; account verification, key creation, and a successful authenticated primary-value request are required for activation.
  • Inputs and outputs must be reviewed in the context of your own data rights, policies, and operational controls.
  • No ranking, accuracy, savings, recovery, prevention, customer, or revenue result is claimed.

From evaluation to first value

A short, explicit path

  1. Run the keyless demo.

    Confirm that the input and output shape match the job you need done.

  2. Create and verify a sandbox account.

    The email claim flow creates a product-scoped API key. No card is required for the free tier.

  3. Call the authenticated primary-value operation.

    A successful authenticated POST /v1/checks that returns evidence drift, control impact, and risk output.

Create a sandbox key Read the API reference