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

# Payments

> How payments work in CoralOS v1.1.0, current limitations, and the x402 flow.

<Note>
  Remote providers and on‑chain payments are disabled in Coral Server v1.1.0. Use local providers only. This page explains the model and what is supported today.
</Note>

# Overview

Coral’s payments model is designed for pay‑per‑use agent execution using Solana settlement. The server can construct a payment session when a graph includes paid, remote agents. Funds are escrowed up to a maximum budget and claims are submitted as work is performed.

In v1.1.0:

* Only local providers are supported for execution. Remote execution and payouts are disabled.
* The server includes payment configuration types and helpers for future compatibility (`PaymentConfig.kt`, `JupiterService`, `BlankBlockchainService`).

# HTTP 402 and x402

The x402 flow standardizes how a server requests payment for a resource/action via HTTP 402.

* Package reference: `org.coralprotocol.coralserver.x402`
* Config reference: `PaymentConfig.kt`

See the dedicated page: [Payments: x402 Flow](/features/payments-x402)

# Payment Sessions (design)

When a session contains paid remote agents, the server would:

1. Compute the maximum budget based on agent export pricing (e.g., micro‑coral ranges).
2. Open and fund an escrow session on Solana.
3. Replace any `provider.type = remote_request` entries with resolved `remote` entries that include wallet routing and session IDs.
4. Aggregate claims during execution and settle at close.

See `LocalSessionManager.createPaymentSession(...)` for the reference implementation. If blockchain services are disabled, this throws to indicate payments are not available.

# Current status and recommendations

* Execute agents locally (`provider.type = "local"`) on your own server; do not rely on remote rental for v1.1.0.
* You can prepare your agents with export pricing and identities for future enablement.
* If you enable marketplace discovery, treat pricing as metadata only (no billing will be enforced by the server).

See also:

* [Marketplace](/concepts/marketplace)
* [Security](/configuration/security)
* [Writing Agents](/guides/writing-agents)