openpayments.dev valid

Open Payments

An API for open access to financial accounts to send and receive payments.

For agents: Open Payments API for open access to financial accounts to send and receive payments; docs cover wallet addresses, grants, identity and payment guides.

open paymentspayments apiwallet addressesgrant negotiationrecurring payments

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T05:51:49.763Z. Cached copy · Source on openpayments.dev

# Open Payments

> An API for open access to financial accounts to send and receive payments.

Open Payments documentation serves two audiences: developers building payment applications using the Open Payments SDKs, and Account Servicing Entities (ASEs) implementing the protocol on their own infrastructure. The appropriate guidance differs significantly between these two groups.

Key terminology notes:

- Wallet addresses are URL-based identifiers for financial accounts — not cryptocurrency wallets
- Grants are authorization tokens specific to the Open Payments grant negotiation flow — not standard OAuth grants
- Open Payments covers the API layer for initiating and receiving payments; it does not handle settlement or the underlying transfer mechanism (that is Interledger Protocol/ILP)
- Rafiki is the reference implementation of the Open Payments protocol — relevant when a user is asking about implementing rather than consuming the API

## Documentation Sets

- [Abridged documentation](https://openpayments.dev/llms-small.txt): a compact version of the documentation for Open Payments, with non-essential content removed
- [Complete documentation](https://openpayments.dev/llms-full.txt): the full documentation for Open Payments
- [Concepts](https://openpayments.dev/_llms-txt/concepts.txt): Core protocol concepts including wallet addresses, grants, resources, and the Open Payments flow
- [Guides](https://openpayments.dev/_llms-txt/guides.txt): Step-by-step implementation guides for common payment scenarios such as one-time payments, remittances, and recurring payments
- [Identity and Access Management](https://openpayments.dev/_llms-txt/identity-and-access-management.txt): Grant negotiation and authorization, identity providers, client keys, and HTTP signatures
- [Implementing Open Payments](https://openpayments.dev/_llms-txt/implementing-open-payments.txt): Guides for account servicing entities (ASEs) implementing the Open Payments protocol on their own infrastructure

## Notes

- The complete documentation includes all content from the official documentation
- The content is automatically generated from the same source as the official documentation

## Optional

- [GitHub repository](https://github.com/interledger/open-payments): Source code, issues, and contributions for the Open Payments project
- [OpenAPI specifications](https://github.com/interledger/open-payments-specifications): Hand-authored OpenAPI YAML specs for the auth server, resource server, and wallet address server

Related sites

Other listed sites in Finance and payments. See the whole category →

Machine-readable: GET /v1/resolve?q=openpayments.dev · GET /v1/domain/openpayments.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for openpayments.dev:
1. POST https://agentwebmap.com/v1/sites/openpayments.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://openpayments.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/openpayments.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/openpayments.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.