LLM Integration
Inyo's developer documentation is optimized for consumption by Large Language Models (LLMs). Whether you're building AI-powered integrations, using coding assistants, or training models on payment processing workflows, we provide machine-readable endpoints following the llms.txt specification.
Available Endpoints
| Endpoint | Description | Use Case |
|---|---|---|
/llms.txt | Documentation index with links to all pages as .md | Discovery — let your LLM find the right page |
/llms-full.txt | All documentation concatenated into a single file | Full context — load everything into one prompt |
/{path}.md | Raw markdown for any individual documentation page | Targeted retrieval — fetch only what you need |
How to Use
With Coding Assistants (Cursor, Copilot, Claude)
Add the llms.txt URL to your project's context or rules file:
# .cursorrules or similar
Documentation: https://dev.inyoglobal.com/llms.txt
Full docs: https://dev.inyoglobal.com/llms-full.txtRAG / Retrieval-Augmented Generation
Fetch the index, then selectively load individual pages:
# 1. Get the index
curl https://dev.inyoglobal.com/llms.txt
# 2. Fetch a specific page
curl https://dev.inyoglobal.com/api-references/payments-gateway/getting-started.md
# 3. Or get everything at once
curl https://dev.inyoglobal.com/llms-full.txtCustom AI Agents / MCP Tools
Build tools that fetch Inyo documentation on demand:
import requests
def get_inyo_docs(page: str = None) -> str:
"""Fetch Inyo developer documentation for LLM consumption."""
if page:
url = f"https://dev.inyoglobal.com/{page}.md"
else:
url = "https://dev.inyoglobal.com/llms-full.txt"
return requests.get(url).text
# Examples:
get_inyo_docs() # Full documentation
get_inyo_docs("api-references/payments-gateway/getting-started")
get_inyo_docs("api-references/payments-gateway/apis/tokenizing-cards")
get_inyo_docs("api-references/remittances/quotes-fx")File Format
/llms.txt
Follows the llms.txt specification. Markdown file with a title, description, and a list of links to individual doc pages with short descriptions. Each link points to the .md version of the page.
/llms-full.txt
All documentation pages concatenated into a single text file, wrapped in XML-style<doc> tags with title and path attributes for easy parsing:
<doc title="Getting Started" path="api-references/payments-gateway/getting-started">
# Getting Started
...full page content...
</doc>
<doc title="Authentication Methods" path="api-references/payments-gateway/authentication-methods">
# Authentication Methods
...full page content...
</doc>Individual .md Pages
Every documentation page is available as raw markdown by appending .md to the URL. The content is identical to the source markdown used to render the HTML page.
Available Documentation
Payment Gateway
- Getting started, authentication, environments
- Card tokenization with inyo.js (PCI-compliant)
- Pull funds: card authorization → 3DS → capture → refund/void
- Pull funds: ACH bank account collection
- Push transactions: domestic & international payouts
- Combined pull+push in one API call
- Webhooks, response codes, payment statuses
- AVS/CVC handling, fraud mitigation
- Test data and sandbox simulation
Remittances
- Sender KYC and trust levels
- FX quotes and rate locking
- Recipient and account management
- Transaction creation and tracking
- Country/bank data population
- Document upload and webhooks