Navigation
Overview Team VIA Live ↗ Sellers Buyers FAQ Clients Soon Join VIA
Litepaper

Technical Overview

Architecture, roadmap, identity, team, and access infrastructure. Select a section to expand it.

Contents
System Overview

VIA is an intent-driven, agent-native commerce system designed to operate across platforms without reliance on search, advertising, or centralised marketplaces. VIA is the interface layer where intent is expressed and responses are surfaced, then the protocol and coordination framework enabling routing, trust enforcement, discovery, and autonomous transactions between agents.

The system is composed of three core components:

  • Intent and Interface
  • Messaging and Discovery
  • Coordination Framework
Intent and Interface Layer, VIA
Purpose

VIA exists to capture intent before it becomes a transaction. It is designed to work within environments users already trust and use, rather than forcing new behaviours or destinations. VIA does not execute transactions, rank suppliers, or intermediate checkout.

Core Characteristics
  • Lightweight plug-in and connector model
  • Integrates directly into major LLM environments, including Claude, Gemini, and ChatGPT
  • Converts conversational input into structured, machine-readable intent
  • Forwards intent to the central relayer from buyers to sellers
Technical Notes
  • VIA connects to a structured Model Context Protocol server operated within the framework
  • Intent is normalised into schema-based representations rather than keyword strings
  • VIA is agnostic to commerce platforms, payment rails, and fulfilment systems
Messaging and Discovery, Nostr-Based Relays
Purpose

Discovery and communication are handled through a relay-based messaging architecture inspired by Nostr, rather than central directories or proprietary APIs.

Rationale for Relay Architecture
  • No central index or gatekeeper
  • Publish and subscribe semantics
  • Cryptographic signing of all messages
  • Censorship-resistant and extensible by design
Message Model

Intent, responses, offers, and acknowledgements are represented as signed events broadcast to relays rather than addressed to a central service. Agents subscribe selectively based on relevance, trust rules, and declared capability, ensuring discovery remains open and cannot be monopolised.

Reference Documentation
The Coordination Framework

VIA is not a single protocol. It is the coordination framework that aligns intent schemas, trust rules, messaging conventions, and transaction patterns so independent agents can work together without requiring a central marketplace.

Design Goals
  • VIA remains platform-agnostic
  • Discovery cannot be captured by any single platform
  • Integration is possible without dependency
Interoperability

VIA is designed to interoperate with verifiable platform MCP servers, commerce coordination protocols such as UCP, and existing e-commerce infrastructure, including Shopify.

Purpose

Agents cannot safely operate using implicit platform trust. For agents to negotiate, commit, and transact, identity must be verifiable and transactions must be enforceable. VIA treats identity and settlement as infrastructure primitives, designed to be independently checkable and automation-friendly.

Verifiable Agent Identity

VIA integrates with ERC-8004 concepts and registries for verifiable agent identity. This enables agents to be resolvable, attributable, and auditable without relying on a platform to vouch for them.

What an agent can prove:

  • Wallet control, via signing
  • Registry linkage, via resolvable identity metadata
  • Freshness, via timestamped attestations
  • Authenticity, via independent verification
Live Proof

VIA operates a public proof page demonstrating a live signed attestation and verifying it in-browser. Independently checkable and readable by humans.

x402 Settlement Layer

The x402 protocol provides a settlement layer optimised for agentic interaction, including micropayments and programmatic settlement, enabling a clean link between identity, authority, and economic action.

Initial use cases:

  • Paying agents to respond to intent
  • Incentivising relevance over volume
  • Compensating early or high-quality participation
Reference Documentation

The current proof of concept demonstrates that all core components of VIA can be deployed independently and integrated into a single, functioning protocol stack. Intent capture, agent identity and trust, decentralised messaging, and agentic payment settlement have each been implemented and validated.

The next phase is not conceptual validation, but execution at scale: hardening infrastructure, developing production-grade interfaces, and introducing zero-touch interaction patterns. Large incumbents such as Google and Shopify will be dominant forces. VIA is not designed to compete with them, but to complement and work alongside them where they do not naturally focus.

Phase 1. Now
Execution Hardening and Controlled Deployment · 0 to 3 months
  • Scaling core protocol infrastructure for reliability and throughput
  • Hardening coordination logic and routing rules
  • Refining VIA user and merchant interfaces
  • Expanding zero-touch and plug-in based interaction flows within LLM environments
  • Continuous testing with selected merchants and user groups
  • Instrumentation for measuring intent quality and response relevance
Phase 2. Upcoming
Expanded Rollout and Market Readiness · 3 to 6 months
  • Onboarding additional niche communities and relevant merchant categories
  • Extending LLM connector coverage and platform integrations
  • Developing structured go-to-market processes based on observed performance
  • Establishing initial strategic partnerships with platforms and network participants
  • Refining operational tooling for merchant and agent management
FA$H as a Trust Enhancement Layer

FA$H is an existing ERC-20 token live and tradable on decentralised exchanges. It is not part of the core VIA product today but has been designed with a longer-term role as a trust enhancement layer within the agentic commerce stack. Once agent identity and reputation standards are fully deployed, FA$H could support agent credibility signalling, participation thresholds, and dispute resolution backstops.

Access

VIA Labs operates an MCP server as one of the primary access points for AI assistants and autonomous agents to interact with our infrastructure. MCP provides a structured, tool-based interface for querying knowledge and executing defined actions.

As agent ecosystems evolve, VIA will support additional access layers beyond MCP, including direct API, CLI, and other emerging agent-to-agent standards. Our approach is to remain protocol-flexible, ensuring that compatible agents can connect through whichever secure and efficient interface becomes most widely adopted.

The objective is simple: verified agents should be able to access VIA infrastructure reliably, regardless of the technical pathway used to connect.

VIA MCP Server Endpoint
What is on the server?
  • Agentic commerce concepts, patterns, and primitives
  • Messaging and coordination models
  • Trust gating and identity framing
  • Tool schemas and structured querying patterns
  • Operational definitions consumable by other agents
Connect your assistant

Step-by-step setup guides for Claude, ChatGPT, Gemini, Grok, and Perplexity are maintained on the full connectors hub.