> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ryvo.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Ryvo Protocol

> A non-custodial clearing and settlement protocol for machine payments on Solana.

Ryvo is a non-custodial clearing and settlement protocol for machine payments on Solana. It is designed for repeated, high-frequency relationships, agents paying APIs, services paying services, and operators routing payments between both, where settling every interaction as its own on-chain transfer is too expensive.

Ryvo decouples **payment execution** from **settlement**. Participants exchange signed cumulative commitments off-chain, then settle only the latest valid state on-chain. The same protocol supports direct settlement for one channel, bundled settlement for one payee, and cooperative clearing rounds across many participants and channels.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/getting-started/quickstart">
    Run your first payment flow against the live devnet deployment in minutes.
  </Card>

  <Card title="Protocol overview" icon="diagram-project" href="/getting-started/protocol-overview">
    Understand the on-chain objects, signed messages, and settlement paths.
  </Card>

  <Card title="TypeScript SDK" icon="code" href="/sdk">
    Integrate Ryvo with [`@ryvonetwork/sdk`](https://www.npmjs.com/package/@ryvonetwork/sdk), typed client, PDA helpers, and message builders.
  </Card>

  <Card title="Live benchmarks" icon="chart-line" href="/benchmarks/live-devnet">
    See compression ratios, transaction sizes, and explorer links from devnet runs.
  </Card>

  <Card title="Reference" icon="book" href="/reference/deployment">
    Deployment info, instructions, message formats, account layouts, events, and errors.
  </Card>

  <Card title="Agentic tools" icon="robot" href="/reference/agentic-tools">
    Skills, CLI, MCP, and LLM text for agents integrating Ryvo.
  </Card>
</CardGroup>

## What Ryvo provides

* **Permanent participant identities.** Every wallet registers once and keeps a stable `participant_id` for the life of the deployment.
* **Persistent payment lanes.** Each participant pair and token maps into a deterministic lane in channel buckets.
* **Signed cumulative commitments.** `ryvo-cmt-v5` is the unilateral message. The payer signs the new cumulative target and the payee settles the delta later.
* **Three settlement modes.** Direct settlement, bundle settlement, and cooperative clearing rounds, all settling into the same shared vault.
* **Non-custodial by construction.** Balances live in program-owned accounts. Operators and facilitators can help submit settlements without holding funds.

Ryvo compression works in two layers:

* **Micropayments are compressed by payment channels.**
* **Settlement is compressed by cooperative clearing rounds.**

## Who Ryvo is for

Ryvo is a good fit when the same parties interact repeatedly and per-payment settlement cost matters:

* agent-driven API and tool consumption
* metered service relationships (inference, RPC, data feeds, compute)
* operator hubs routing payments between users and providers
* payment networks among a known set of counterparties

It is not intended to replace Solana's native transfer for one-off, high-value payments.

## Where to go next

<CardGroup cols={2}>
  <Card title="Why cooperative scaling" icon="lightbulb" href="/thesis/motivation">
    Why machine payments benefit from a clearing layer, not more transactions.
  </Card>

  <Card title="Your first payment" icon="play" href="/getting-started/first-payment">
    The smallest useful integration, register, deposit, open a channel, sign, settle.
  </Card>

  <Card title="Settlement modes" icon="layer-group" href="/settlement-modes/overview">
    Choose between direct, bundle, and cooperative clearing paths.
  </Card>

  <Card title="Security model" icon="shield-halved" href="/security/trust-model">
    What Ryvo guarantees on-chain, and what stays a relationship-level choice.
  </Card>
</CardGroup>