OOBE / INFRASTRUCTURE

The systems
beneath the systems.

Agent identity. Tool access. Blockchain data. Payment and execution. Distinct layers, connected through clear interfaces.

01 / SYSTEM ARCHITECTURE

From application
to settlement.

EXPLORE THE LAYERS

The hosted interface exposes tools to compatible agents. Local signing remains a separate authorization boundary.

Conceptual relationships. Agents may also access protocol and RPC interfaces directly.

02 / THE FOUNDATIONS

Agent identity and coordination primitives, exposed through the Synapse Agent Protocol and its developer interfaces.

A hosted tool gateway for compatible agent runtimes. Protocol access and payment-aware tools share a standard interface.

Solana data access and RPC infrastructure for applications and agent workflows.

User-owned signing and payment authorization remain separate from the hosted gateway.

03 / CAPABILITIES & AVAILABILITY

Availability is described per product. Public access to an endpoint does not mean every tool or execution path is enabled without configuration.

Current product surfaces and capability boundaries
SURFACE	AVAILABILITY	BOUNDARY
SAP MCP	Hosted gateway	Discovery & toolsPaid and write calls require appropriate local authorization.
Protocol SDK	Public source	Integration dependentConsult the repository and program documentation for supported APIs.
Synapse Studio	Desktop product	Release dependentDownloads and platform support are listed on the official product site.
Steve Capital OS	Product development	Product directionAdvanced orchestration and policy features require release-specific verification.