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

Live protocol defaults

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

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:
Protocol MCP:
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

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.