SYNTHETIC PROOF WALKTHROUGH

Hold a vendor mapping when the supplied domain is not approved

A synthetic entity-resolution packet comparing supplied vendor evidence with a customer-controlled domain baseline.

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 submitted vendor domain is absent from the customer-provided approved-domain list.

  1. 01

    Provide customer-owned identity evidence

    The caller supplies names, aliases, addresses, domains, and any expected customer baseline.

  2. 02

    Normalize and compare

    The control compares normalized values without consulting or claiming an official identity registry.

  3. 03

    Hold the mismatched mapping

    An unapproved domain returns named evidence for a trusted out-of-band review.

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_name": "Northstar Supply",
  "aliases": [
    "Northstar"
  ],
  "expected_name": "Northstar Supply",
  "email_domain": "northstar-payments.com",
  "approved_domains": [
    "northstarsupply.com"
  ]
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "REVIEW_REQUIRED",
  "exceptions": [
    {
      "code": "VENDOR_DOMAIN_UNAPPROVED",
      "severity": "HIGH",
      "message": "The supplied vendor email domain is absent from the customer-provided approved domains.",
      "evidence": {
        "submitted_domain": "northstar-payments.com"
      }
    }
  ],
  "evidence": {
    "canonical_name": "Northstar Supply",
    "aliases_checked": 1,
    "domain_checked": true
  },
  "next_action": "Verify the vendor through a trusted customer-controlled channel."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

This result compares customer-supplied evidence. It is not KYB, sanctions screening, domain-ownership proof, or legal-entity verification.

Decision
REVIEW_REQUIRED
Named exception
VENDOR_DOMAIN_UNAPPROVED
Evidence
submitted domainnorthstar-payments.com
Next action
Verify the vendor through a trusted customer-controlled 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 →