SYNTHETIC PROOF WALKTHROUGH

Pause a vendor request arriving from a new, unapproved domain

A synthetic domain-baseline comparison that produces evidence for out-of-band verification.

See the three stepsRead the product contract →
NO KEY · NO UPLOAD · NO CUSTOMER DATAThis demonstration runs entirely in your browser using the visible synthetic fixture below.

THREE STEPS

Put the control before the consequential action.

The sender domain appears in neither the approved-domain list nor the supplied prior-sender baseline.

  1. 01

    Supply the sender and baselines

    The customer provides the observed sender plus its own approved and previously seen domains.

  2. 02

    Compare exact normalized domains

    The control reports whether the sender is invalid, unapproved, or new to the supplied baseline.

  3. 03

    Verify outside the request channel

    A new domain routes the workflow to a previously trusted vendor contact path.

VISIBLE SYNTHETIC CONTRACT

Inspect exactly what the workflow sees.

The input and output are representative of the named product contract. Copy them into an architecture note, test fixture, or internal review—never treat this browser-only demonstration as a live control result.

Customer-authorized input
{
  "vendor_reference": "northstar-1007",
  "sender_email": "payments@northstar-payments.com",
  "approved_domains": [
    "northstarsupply.com"
  ],
  "prior_sender_domains": [
    "northstarsupply.com"
  ]
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "REVIEW_REQUIRED",
  "exceptions": [
    {
      "code": "VENDOR_DOMAIN_UNAPPROVED",
      "severity": "HIGH",
      "message": "The sender domain is not in the customer-provided approved-domain list.",
      "evidence": {
        "sender_domain": "northstar-payments.com"
      }
    },
    {
      "code": "VENDOR_DOMAIN_NEW",
      "severity": "MEDIUM",
      "message": "The sender domain was not in the supplied prior-sender baseline.",
      "evidence": {}
    }
  ],
  "evidence": {
    "vendor_reference": "northstar-1007",
    "sender_domain": "northstar-payments.com",
    "approved_domains_checked": 1,
    "prior_domains_checked": 1
  },
  "next_action": "Verify the requested change through a trusted out-of-band channel."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

The control does not inspect email content, authenticate a domain, send a message, contact a vendor, or change a vendor record.

Decision
REVIEW_REQUIRED
Named exception
VENDOR_DOMAIN_UNAPPROVED
Evidence
sender domainnorthstar-payments.com
Next action
Verify the requested change through a trusted out-of-band channel.

KEEP BUILDING

Move from the synthetic fixture to the exact API contract.

Review the product inputs, outputs, errors, and safety boundary before using authorized data. The related implementation guide explains the design decisions behind the control.

Product contract →Implementation guide →Security posture →

Try the control through the supported buyer path.

RapidAPI provides the subscription, key, quota, and capped marketplace plan for this synchronous control.

Get an API key on RapidAPIExplore every synthetic demo →