Skip to main content

SPID Protocol Overview

As artificial intelligence becomes increasingly embedded in communication, commerce, and daily life, a new form of digital identity is required. Existing models based on email addresses, phone numbers, or static credentials are not sufficient for consent-driven, AI-mediated interactions.

The Smart Packet Identity Protocol (SPID) is designed to solve this gap.

SPID establishes a machine-readable, consent-aware identity layer that allows individuals to govern how AI systems interact with them across platforms, services, and networks.

The Problem SPID Solves​

AI systems currently lack a universal, trusted way to:

  • Verify who initiated an interaction
  • Confirm whether consent was granted
  • Determine which permissions are active
  • Log interaction terms in a standardized, portable format
  • Respect individual boundaries across decentralized networks

Without these capabilities, AI risks becoming intrusive, manipulative, or unaccountable at scale.

SPID provides a structured solution.

What SPID Is​

SPID is not a centralized platform, credential authority, or third-party gatekeeper.

It is an open protocol specification that allows:

  • Any individual to issue their own AI-readable identity marker (SPID)
  • Consent logs to be attached directly to AI interactions
  • Smart Packets (structured voice or data messages) to carry embedded permissions
  • Systems to verify consent status before initiating or continuing AI processes

SPID operates at the protocol layer, independent of application providers, ensuring broad interoperability and long-term resilience.

Core Components of SPID​

SPID Record
A compact, portable identity packet containing identity attributes, consent rules, and interaction parameters.

Consent Log
A machine-readable record of when, how, and for what purpose consent was granted or revoked.

Interaction Scope
Defines the specific boundaries of any AI interaction: topic, duration, data access, delegation rights, and authority limits.

Verification Layer
Allows any system to authenticate SPID records and confirm permission status in real-time.

Revocation Mechanism
Ensures that individuals can withdraw consent at any time, immediately terminating unauthorized AI actions.

Use Case Examples​

  • Asynchronous voice messaging (Smart Packets) with embedded consent markers
  • AI-powered assistants that verify consent before engagement
  • Regulatory-compliant AI services that require verifiable permission logs
  • AI-to-AI transactions governed by pre-authorized SPID interaction scopes
  • Voiceprint-verified identity layers tied to PulseID and Clean Voice standards

Why SPID Matters​

SPID transforms identity from a static credential into an active consent framework.

  • Individuals remain in control of their digital presence.
  • AI systems operate with transparent boundaries.
  • Organizations can confidently deploy AI without violating privacy or regulatory expectations.
  • Consent is no longer implied or assumed — it is explicit, verifiable, and auditable.

The Human Channel Commitment​

The Human Channel is actively developing and advancing SPID as a core part of the broader Consent-First AI framework. We believe SPID represents the foundation for building AI systems that scale responsibly, respect human agency, and protect long-term trust across all digital ecosystems.