# Ezys Documentation

> A public permissioned solver network for institutional-grade FX transactions

Every page below is also available as Markdown at the same path with a `.md` extension; the HTML page is at the same path with `.html` (the home page is `https://docs.ezys.io/`).
The Partner API v0.9.10 is also published as an OpenAPI document (YAML): https://docs.ezys.io/openapi/ezys-partner-api.v1.yaml
All pages in one file: https://docs.ezys.io/llms-full.txt
Agent skill (how to use this documentation): https://docs.ezys.io/SKILL.md
Read-only MCP server (Streamable HTTP; tools search, list_pages, read_page, get_api_operation): https://docs.ezys.io/mcp

## Introduction

- [Ezys](https://docs.ezys.io/index.md): Exchange token and fiat assets through one partner API, with quotes, signed intents and settlement tracking.
- [Architecture](https://docs.ezys.io/architecture.md): Ezys turns exchange requests into executions across token transfers and fiat payout rails. The public integration consists of quote and intent submission, execution status, receipts and webhooks.

## For Fintech Service Providers

- [Overview](https://docs.ezys.io/for-fsps/overview.md): Ezys enables Fintech Service Providers to access competitive FX execution without building or managing direct relationships with multiple liquidity providers.
- [Intent](https://docs.ezys.io/for-fsps/intent.md): How to lock a rate with a firm quote and execute it by submitting an Intent.
- [Execution Strategy](https://docs.ezys.io/for-fsps/strategy.md): Choose whether to lock a quote, which amount to fix, and whether to process the intent immediately or through batch collection.
- [Settlement](https://docs.ezys.io/for-fsps/settlement.md): What happens after your Intent is accepted — how and when funds are transferred.

## For FX Trading Institutions

- [Overview](https://docs.ezys.io/for-institutions/overview.md): Institutions can integrate liquidity and execution capabilities with Ezys through an onboarded connection. Supported corridors, funding and settlement arrangements are agreed before traffic is enabled.
- [Liquidity Provider](https://docs.ezys.io/for-institutions/liquidity-provider.md): Provide pricing and settlement capacity for the corridors enabled in your Ezys integration.
- [Solver Participation](https://docs.ezys.io/for-institutions/validator.md): A registered solver can propose solutions for batches of intents on corridors it supports. This role is distinct from validating blocks on a blockchain.

## Core Concepts

- [Solver Network](https://docs.ezys.io/core-concepts/solver-network.md): Ezys selects execution paths from configured liquidity sources. An intent can be processed immediately or collected into a batch for registered solvers to propose solutions.
- [Execution & Settlement](https://docs.ezys.io/core-concepts/execution-settlement.md): An accepted intent starts an execution. Settlement moves the assets, while status, receipts and on-chain anchors report different parts of the result.

## API Reference

- [Overview](https://docs.ezys.io/api-reference/overview.md): Complete reference for the Ezys REST API. All endpoints communicate over HTTP using JSON.
- [OpenAPI Specification](https://docs.ezys.io/api-reference/openapi.md): The Ezys Partner API is also published as an OpenAPI 3.0 document:
- [Authentication](https://docs.ezys.io/api-reference/authentication.md): How to authenticate with the EZYS API.
- [Idempotency](https://docs.ezys.io/api-reference/idempotency.md): X-Idempotency-Key provides request deduplication and replay for partner-facing POST requests. A matching completed request replays its original 2xx response during the 24-hour retention window.
- [Quote API](https://docs.ezys.io/api-reference/quote-api.md): Request a quote — the pair, amount, and side you want — from the Solver Network. The solver searches its liquidity sources, scores the results, and returns either a ranked list of indicative candidates or a firm quote…
- [Intent API](https://docs.ezys.io/api-reference/intent-api.md): Submit an Intent — what you want to exchange and the constraints you accept — to the Solver Network. The solver computes an execution path and either accepts it (reserving liquidity and starting settlement) or rejects…
- [Status API](https://docs.ezys.io/api-reference/status-api.md): Query the current state and recorded phase history of a single execution — one end-to-end fill spanning up to three phases: intent (acceptance), offramp (input locking and payout confirmation), and payout (fiat delivery…
- [Receipts API](https://docs.ezys.io/api-reference/receipts-api.md): GET /v1/executions/{reference}/receipt returns a stored receipt after eligible payout execution completes and receipt issuance succeeds.
- [Webhooks](https://docs.ezys.io/api-reference/webhooks.md): Ezys sends an HTTPS POST to your registered endpoints when an execution changes state. Each request carries one event.
- [Error Handling & Retries](https://docs.ezys.io/api-reference/errors.md): Choose recovery from the endpoint, HTTP status, and error code together. A 5xx does not prove that an operation failed before acceptance, and a 422 does not always require a different intent.
- [Money & Amounts](https://docs.ezys.io/api-reference/money-and-amounts.md): How monetary values are represented across the Ezys API. This convention applies to every amount-bearing field in requests, responses, webhooks, and reconciliation data.

## For agents

- [Using Ezys with AI](https://docs.ezys.io/using-ezys-with-ai.md): AI coding agents can read this documentation and the Partner API contract directly. Connect your agent through one of the options below so it answers from these pages instead of from memory.

## OpenAPI

- [Ezys Partner API v0.9.10 (OpenAPI, YAML)](https://docs.ezys.io/openapi/ezys-partner-api.v1.yaml): machine-readable description of the endpoints and schemas