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

# API reference

> Endpoint-by-endpoint reference for discovery, signed partner, and merchant portal APIs.

Set `AGENTBANK_BASE_URL` using [Environments](./environments). All endpoint
paths are relative to that host; credentials and resources are isolated by environment.

## Use the workflow first

Begin with the [Quickstart](./quickstart) for the complete integration sequence,
then use these endpoint pages for request and response details.

## Endpoint groups

Every endpoint has its own page with authentication, path/query parameters,
example request, and example response.

| Group | Use it for |
| - | - |
| [Discovery](./reference/discovery/currencies) | Active currencies, live fiat instruments, recipient schemas, and curated bank names. These routes are public and work for both personal and partner clients. |
| [Signed Partner API](./reference/partner/create-end-user) | KYC, recipient previews, payment estimates, payment lifecycle reads, and cancellation. Every request is Ed25519-signed. |
| [Merchant Portal API](./reference/portal/login) | Portal login, payment-history reads, and webhook endpoint management. |

## Content conventions

* Use `Content-Type: application/json` for bodies.
* Send and sign the exact UTF-8 JSON bytes.
* Timestamps returned by the B2B objects may be strings containing Unix
  milliseconds; payment `created_at` and `updated_at` are ISO timestamps.
* Preserve all opaque IDs (`mp_`, `mpk_`, `peu_`, `pay_`, `mwe_`) as strings.
* Treat fields documented as provider-generated, especially `payment_instruction`
  and `timeline`, as read-only.