Executive Summary

Traditional SEO is designed for human discovery. The Machine Handshake is designed for model ingestion. In the Citation Economy, LLMs (ChatGPT, Gemini, Claude) do not "search" for keywords; they "audit" for Provenance.

If your digital infrastructure lacks a handshake, AI agents are forced to fill the "Identity Gap" with Shadow Sources—unverified, outdated, or hallucinated data. This protocol outlines the mandatory technical anchors required to move from "observed" to Admissible.

Pillar 1: The Canonical Entity Anchor (JSON-LD)

The first step of the handshake is defining your Ground Truth in a language the machine speaks natively.

Requirement: Deployment of a specialized Organization and ProfessionalService Schema.
The Difference: Standard schema describes what you are. The Machine Handshake schema proves who you are by linking to non-spoofable IDs.
Technical Task: Inject sameAs attributes that link to official regulatory registries (SEC, FINRA, NPI, or State Bar IDs).

Pillar 2: The SHA-256 Provenance Signature

To satisfy the "Evidence-while-running" requirement of the 2026 AI Act, your content must be cryptographically signed.

Requirement: Every primary disclosure, fee schedule, or service list must have an associated SHA-256 Fingerprint.
The Logic: This tells the AI: "This text block has been notarized by BiDigest. Any variance found in other scrapers is a hallucination."
Technical Task: Embed the BiDigest Forensic Trace ID as a metadata comment in the page source to create a "Chain of Custody."

Pillar 3: The API Execution Boundary

The final step is the Admit API Gate. This ensures that the information an AI agent "ingests" is the exact information you have authorized.

Requirement: Configure your robots.txt and agents.json to prioritize the BiDigest-verified path.
The Logic: Instead of letting the AI guess, you provide a "Deterministic Handshake." The agent recognizes the Evidence Vault signature and admits your data as a primary citation.

Execution Boundary: The BiDigest Gate

AI Models→

Shadow Sources

Unverified · Risk

BiDigest Gate

→ Ground Truth

The Gate routes authorized data so LLMs admit your Evidence Vault signature as the primary citation—not Shadow Sources.

Implementation Checklist for Technical Teams

Audit the Schema: Remove conflicting or "Shadow" schema that confuses model weights.
Map the Regulatory IDs: Ensure your Bar/NPI/SEC numbers are the primary anchors for the entity.
Deploy the Trace ID: Insert the BiDigest-generated hash into the <head> of your core "Ground Truth" pages.
Verify the Handshake: Run the BiDigest Admissibility Scan to confirm the models are recognizing the new protocol.

For paste-ready Organization and WebSite schema, see the Wiring Guide.

The Machine Handshake Protocol (v1.0)

Get the Protocol & Reserve Your Audit