Skip to main content
Ryvo publishes agent-facing tools in the Ryvonetwork/ryvo-agentic repository. The repo contains gateway tools, protocol tools, Codex-style skills, and LLM-readable docs.

​
Repository layout

PathPublishesPurpose
cli/@ryvonetwork/gateway-cliDiscover gateway routes and call them from agent workflows.
mcp/@ryvonetwork/gateway-mcpMCP server for gateway route discovery and calls.
protocol-cli/@ryvonetwork/protocol-cliRead protocol state and prepare unsigned protocol actions.
protocol-mcp/@ryvonetwork/protocol-mcpMCP server for protocol read and prepare tools.
skills/ryvo-gateway/Codex-style skillGateway catalog, x402, and SIWX workflows.
skills/ryvo-protocol/Codex-style skillParticipants, balances, channels, settlement, withdrawals, and BLS caveats.
skills/ryvo-gateway-payment-channels/Codex-style skillChannel-backed gateway calls using signed cumulative commitments.

​
Live protocol defaults

FieldValue
Program ID3UyUFeNsUYPpM6hMRf7H8wg3MKEXQ82rqnsXhZrUwgSD
Clusterdevnet
Chain ID1
Message domaina58a109a38f14cc27ef174135176cab3
Gateway-channel tokenOfficial devnet USDC, mint 4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU
The official devnet USDC token_id is resolved from the protocol TokenRegistry or from RYVO_PROTOCOL_DEVNET_USDC_TOKEN_ID. Do not hardcode demo token IDs in agent integrations.

​
CLI packages

npx @ryvonetwork/gateway-cli health
npx @ryvonetwork/gateway-cli catalog
npx @ryvonetwork/protocol-cli config
npx @ryvonetwork/protocol-cli token show
npx @ryvonetwork/protocol-cli participant show --owner <owner>
npx @ryvonetwork/protocol-cli channel headroom --payer-id <payer-id> --payee-id <payee-id> --latest-accepted <amount>
The protocol CLI is read + prepare only. It can prepare transactions and gateway commitment payloads, but it does not store private keys, sign messages, or broadcast transactions.

​
MCP packages

Gateway MCP: 
{
  "mcpServers": {
    "ryvo-gateway": {
      "command": "npx",
      "args": ["-y", "@ryvonetwork/gateway-mcp"]
    }
  }
}
Protocol MCP: 
{
  "mcpServers": {
    "ryvo-protocol": {
      "command": "npx",
      "args": ["-y", "@ryvonetwork/protocol-mcp"],
      "env": {
        "SOLANA_DEVNET_RPC_URL": "https://api.devnet.solana.com"
      }
    }
  }
}
The protocol MCP exposes the resource ryvo://protocol/llm.txt. Like the protocol CLI, it is read + prepare only and never signs or submits transactions.

​
LLM text

FileScope
llm.txtGateway-focused short context for agent clients.
llms.txtGateway-focused expanded context for agent clients.
protocol-mcp/llm.txtProtocol-focused short context, also exposed through MCP as ryvo://protocol/llm.txt.
protocol-mcp/llms.txtProtocol-focused expanded context.

​
Payment-channel guardrails

Gateway channel payments use signed cumulative commitments against locked channel collateral. For /v1/ryvo-channel/... routes, agents should:
  1. Open a channel to the gateway merchant participant.
  2. Lock official devnet USDC into that channel.
  3. Sign one cumulative commitment per request.
  4. Send X-Ryvo-Request-Id and RYVO-COMMITMENT with the gateway call.
Tokens SIWX routes remain auth-only and free. They do not use payment channels.

​
Protocol caveats

  • Participant withdrawals are instant on the live devnet deployment.
  • Unilateral channel unlocks take 72 hours.
  • Cooperative channel unlocks are immediate when both parties agree.
  • Ryvo BLS is Ryvo-specific. It is not a generic IETF hash-to-curve BLS ciphersuite, so clients must use the shared Ryvo implementation and test vectors.
  • BLS key rotation does not exist yet. If a BLS key is lost or compromised, the participant should migrate to a new participant identity for future BLS clearing.