AI agent access
Use these endpoints and tools to give AI coding assistants and LLMs access to Payabli documentation at lower token cost than fetching full web pages.
Quick start
- AI coding agents (Claude Code, Cursor, Copilot, and more): Install the Payabli Agent Skills to guide your agent as it writes Payabli code. Add the Payabli MCP server so it can search the docs. They work best together — install both.
- Context7: Pull Payabli docs into any Context7-compatible AI tool for up-to-date, version-aware context. See Context7.
- Chat interfaces (ChatGPT, Claude.ai): Append
.mdto any docs page URL and paste it into your conversation. You get clean markdown instead of a full web page. - Project rules and custom instructions: Add a section-level
llms.txtURL to your AI tool’s rules file to give it an index of relevant Payabli pages. - API-aware coding: Download the OpenAPI spec and add it to your AI tool’s context so it understands the full API surface when writing integration code.
MCP server
The Payabli MCP server gives AI agents and coding assistants direct access to Payabli documentation and SDK references through the Model Context Protocol. Use it to integrate Payabli knowledge into tools like Claude, Cursor, and other MCP-compatible clients.
Agent Skills
Payabli Agent Skills ship Payabli-specific procedural knowledge into your coding agent, so it follows the right order of operations when writing Payabli code. The MCP server answers questions; skills sequence the work. Use them together.
Context7
Context7 indexes the full docs.payabli.com site and serves it to AI coding assistants as up-to-date, version-aware context. Use it when you want your assistant to reference current Payabli documentation without you pasting URLs or markdown into the conversation.
Point any Context7-compatible tool at the Payabli library:
Most Context7 clients accept the library ID websites/payabli directly. See the Context7 MCP setup guide for client-specific instructions.
Per-page markdown
Append .md to any page URL to get a lightweight markdown version. This returns clean markdown without HTML, navigation, or scripts, and uses fewer tokens than fetching the full page.
For example, to get the markdown version of the Pay In overview page, use:
Site-wide endpoints
These endpoints follow the llms.txt standard and offer documentation content in markdown format.
Section-level endpoints
Use these for more targeted access. The llms.txt variant provides a page index with descriptions. The llms-full.txt variant provides full page content.
Guides
Step-by-step integration guides, conceptual explanations, and platform documentation for Pay In, Pay Out, and Pay Ops.
Developer tools
API references, SDK documentation, embedded component references, and developer-focused tooling.
Query parameters
The developer tools endpoints support query parameters to reduce response size. SDK code examples are part of the API specification, so excludeSpec removes them. Use lang instead if you want the spec but only need examples in one language.
Changelogs
Release notes and change history for the API, embedded components, and SDKs.
Cookbooks
Short, focused API recipes for common tasks.
OpenAPI specification
Download the full Payabli OpenAPI specification (~1.9 MB) for use with AI coding tools, API clients, or code generators.