# Payrail Agent Index

Payrail Agent is payment infrastructure for personal AI agents. It combines Payrail Agent Card, built-in browser, Payrail Agent Search, Payrail Agent Memory, Payment Bridge, and omnichannel approvals so user-authorized agents can complete purchases without asking users to paste card data, passwords, identity fields, OTPs, or final payment confirmations into chat.

## Canonical Machine Routes
- LLM index: https://agent.payrail.one/llms.txt
- Full docs text: https://agent.payrail.one/llms-full.txt
- Agent skill installer: https://agent.payrail.one/skill.md
- Agent JSON index: https://agent.payrail.one/agent-index.json
- OpenAPI JSON: https://agent.payrail.one/docs/openapi.json
- Support: security@payrail.one

## Required Agent Rules
- Use Payrail Agent Search to find provider-method URLs, official docs, and guidance; execute with your own capabilities.
- Use built-in browser for ordinary commerce navigation.
- Use Payrail Agent requests for protected data, choices, approvals, and payments.
- Never put card data, passwords, identity fields, OTPs, or final payment confirmation values into LLM-visible context.
- Stop at every protected step and wait for Payrail Agent before continuing.

## Overview
Understand Payrail Agent as payment infrastructure for personal AI agents before choosing a component or guide.
- Payrail Agent Docs: https://agent.payrail.one/docs | Markdown: https://agent.payrail.one/docs/index.md | Payrail Agent gives personal AI agents one user-authorized payment stack: Payrail Agent Card, Memory requests, and routing across browser, API, and agentic payment rails.

## Components
Learn the modules behind agent payments and protected checkout execution.
- Payrail Agent Components: https://agent.payrail.one/docs/components | Markdown: https://agent.payrail.one/docs/components.md | Payrail Agent is modular payment infrastructure for personal AI agents. Each component can stand alone, but together they form an end-to-end purchase flow where agents act for humans without owning sensitive data.
- Payrail Agent Card: https://agent.payrail.one/docs/payrailAgentCard | Markdown: https://agent.payrail.one/docs/payrailAgentCard.md | Payrail Agent Card turns agentic payments, crypto, APIs, browser checkout, and new payment protocols into one simple top-up balance.
- Payrail Agent Fill: https://agent.payrail.one/docs/components/payrailAgentFill | Markdown: https://agent.payrail.one/docs/components/payrailAgentFill.md | The host built-in browser analyzes the page; Payrail Agent Fill only materializes and applies exact protected values and one exact final click.
- Payrail Agent Search: https://agent.payrail.one/docs/components/payrailAgentSearch | Markdown: https://agent.payrail.one/docs/components/payrailAgentSearch.md | Payrail Agent Search answers natural-language discovery questions with provider and method names, useful URLs, official documentation, and concise operating guidance. The agent performs the work.
- Payrail Agent Memory: https://agent.payrail.one/docs/components/memory | Markdown: https://agent.payrail.one/docs/components/memory.md | Payrail Agent Memory stores user-owned items and protected fields so agents can request the right data during a workflow without seeing raw values.
- Payrail Agent Memory fill: https://agent.payrail.one/docs/components/memory-fill | Markdown: https://agent.payrail.one/docs/components/memory-fill.md | Payrail Agent Memory fill is the step where approved values are written into a target — such as a browser checkout field for card, login, identity, or confirmation — without ever entering the LLM context.
- Payment Bridge: https://agent.payrail.one/docs/components/payment-bridge | Markdown: https://agent.payrail.one/docs/components/payment-bridge.md | Payment Bridge is the backend connectivity layer that gives agents a simple Payrail Agent interface while payment operations run through provider-backed infrastructure.
- Omnichannel UI: https://agent.payrail.one/docs/components/omnichannel-ui | Markdown: https://agent.payrail.one/docs/components/omnichannel-ui.md | Payrail Agent supports a growing set of user-facing apps so agents can request approval, ask for missing data, and show progress without exposing protected values in chat.

## Guide
Task-oriented walkthroughs for setup, purchase flows, Memory, and subscriptions.
- Getting Started: https://agent.payrail.one/docs/getting-started | Markdown: https://agent.payrail.one/docs/getting-started.md | Install the Payrail Agent skill, connect the runtime to the remote MCP, then top up Payrail Agent Card before the first low-risk payment session.
- Set Up Your Account: https://agent.payrail.one/docs/guides/account-setup | Markdown: https://agent.payrail.one/docs/guides/account-setup.md | Follow this guide when you are preparing a user account for the first real payment session.
- Connect An Agent: https://agent.payrail.one/docs/guides/connect-agent | Markdown: https://agent.payrail.one/docs/guides/connect-agent.md | Use this guide to install the native Payrail Agent plugin, authenticate its remote MCP, verify capabilities, and run the first Memory-managed workflow.
- E2E Purchase Flow: https://agent.payrail.one/docs/guides/e2e-purchase | Markdown: https://agent.payrail.one/docs/guides/e2e-purchase.md | The built-in agent clarifies intent, searches providers, selects a channel, uses built-in browser or an agentic protocol, and raises user requests during the session.
- SDK Purchase Flow: https://agent.payrail.one/docs/guides/sdk-purchase | Markdown: https://agent.payrail.one/docs/guides/sdk-purchase.md | Your own agent can search, browse, and reason independently, then call Payrail Agent SDK to resolve a protected value or run a protected payment action.
- Manage Memory: https://agent.payrail.one/docs/guides/manage-secrets | Markdown: https://agent.payrail.one/docs/guides/manage-secrets.md | Saved Memory items reduce repeated questions while protected values stay behind Payrail Agent requests.
- Manage Subscriptions: https://agent.payrail.one/docs/guides/subscriptions | Markdown: https://agent.payrail.one/docs/guides/subscriptions.md | Subscription purchases use a dedicated static card and store renewal and cancellation context so users can manage recurring payments in one place.
- Troubleshooting: https://agent.payrail.one/docs/guides/troubleshooting | Markdown: https://agent.payrail.one/docs/guides/troubleshooting.md | Use this page when a checkout, a Memory request, a value that will not resolve, or a payment action is stuck.
- Agent Operating Guide: https://agent.payrail.one/docs/agents | Markdown: https://agent.payrail.one/docs/agents.md | Agents should use this page as the compact source of truth for Payrail Agent routing, protected steps, and safe checkout behavior.
- Agent Skills: https://agent.payrail.one/docs/integrations/agent-skills | Markdown: https://agent.payrail.one/docs/integrations/agent-skills.md | Agent skills package the instructions, rules, and commands an AI runtime needs to use Payrail Agent safely.
- Payrail Agent SDK: https://agent.payrail.one/docs/integrations/sdk | Markdown: https://agent.payrail.one/docs/integrations/sdk.md | The SDK is the right entry point when you own the surrounding agent, browser, or backend runtime and need Payrail Agent as the Memory request layer.
- ChatGPT App: https://agent.payrail.one/docs/integrations/chatgpt | Markdown: https://agent.payrail.one/docs/integrations/chatgpt.md | The ChatGPT app gives users a familiar place to start sessions and review payment-related state while Payrail Agent keeps protected values outside model context.
- Claude App: https://agent.payrail.one/docs/integrations/claude | Markdown: https://agent.payrail.one/docs/integrations/claude.md | Claude can use Payrail Agent through the same built-in browser plus Payrail Agent skill model used by other supported agents.
- Telegram Miniapp: https://agent.payrail.one/docs/integrations/telegram | Markdown: https://agent.payrail.one/docs/integrations/telegram.md | The Telegram miniapp delivers requests, shows approvals, hands off KYC, and keeps session work out of the chat.

## API
HTTP API entry points, authentication, schema, and generated OpenAPI reference.
- API Reference: https://agent.payrail.one/docs/api | Markdown: https://agent.payrail.one/docs/api.md | Use this page when you need the HTTP API: integration rules and the generated OpenAPI contract in one place.
- Public Directory: https://agent.payrail.one/docs/api/directory | Markdown: https://agent.payrail.one/docs/api/directory.md | Use this page when an agent or a page needs to find sellers without an account: natural-language search, the filterable list, one provider method with its guidance, and the trust record behind a hostname.

## Reference
Stable lookup pages for entities, payment methods, trust rules, and terms.
- Entities: https://agent.payrail.one/docs/reference/entities | Markdown: https://agent.payrail.one/docs/reference/entities.md | Use this page when you need the stable nouns used across product, SDK, API, and agent flows.
- Payment Methods: https://agent.payrail.one/docs/reference/payment-methods | Markdown: https://agent.payrail.one/docs/reference/payment-methods.md | Payrail Agent hides payment method details from users while routing agent sessions through the best available rail.
- Trust System: https://agent.payrail.one/docs/reference/trust-system | Markdown: https://agent.payrail.one/docs/reference/trust-system.md | Agentic commerce needs trust signals across the open internet. Payrail Agent can store purchase outcomes, provider reputation, and flow hints after sessions.
- Glossary: https://agent.payrail.one/docs/glossary | Markdown: https://agent.payrail.one/docs/glossary.md | Use this page when a docs page mentions a term you do not recognize.