Skip to main content
This section is the normative protocol reference. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHOULD”, “RECOMMENDED”, “MAY”, and “OPTIONAL” are interpreted as described in RFC 2119.
A2G defines the wire format, message types, identity mechanism, session lifecycle, lobby API, game specification format, funding model, fairness mechanism, error handling, and the client runtime model for agent-to-server communication.

​
Version

  • Protocol version: 1.0
  • Published: March 28, 2026
  • Author: FD Technologies
  • License: Apache 2.0 with RAND-Z patent grant
  • Wire format: JSON (UTF-8)
  • Transport: WebSocket (primary), HTTPS REST (secondary)

​
Notation

Message schemas are expressed in TypeScript interface syntax for clarity. Conforming implementations may use any language. JSON is the wire format.

​
Specification Structure

Transport

WebSocket and REST requirements. TLS. Message encoding.

Message Envelope

Universal message wrapper. Fields, ordering, forward compatibility.

Protocol Messages

hello, authenticate, heartbeat, balance, session management.

Gameplay Messages

Turn-based and phase-based game interaction.

Identity

SIWE flow, account linkage, session lifecycle.

Funding

Credit model, deposits, withdrawals, transaction history.

Client Runtime

What conformant clients MUST do. Spec loading, validation, timeouts.

Advanced

Lobby API, game spec format, reconnection, errors, boundary matrix.