Plain Text Docs & LLMs.txt

Feed any LLM with clean, token-efficient versions of Localpayment's documentation. Use the llms.txt index for a structured overview, or add .md to any documentation URL for article-level Markdown content. No setup or configuration required.

Localpayment's documentation is available in plain text formats designed for LLM consumption. These formats are useful when you want to paste documentation content directly into a chat interface, feed context to a language model programmatically, or build tooling that reads the API documentation.

No configuration is needed — both features are always available.


LLMs.txt

https://docs.localpayment.com/llms.txt

The llms.txt file is a structured index of Localpayment's entire documentation, formatted according to the llmstxt.org open standard. It provides a curated, hierarchical overview of available guides and reference pages — optimized for LLM context windows.

What it contains

  • A brief description of Localpayment and what the documentation covers
  • A structured list of all documentation sections and their key articles
  • Direct links to each article in plain text (.md) format

When to use it

  • To give a language model a complete map of the documentation before asking integration questions
  • To build tooling that programmatically discovers all available documentation pages
  • As a starting point before fetching specific articles for deeper context

How to use it

Paste the URL or content of llms.txt into your AI assistant at the beginning of a session:

Read the following documentation index and use it as context for the 
questions I will ask about the Localpayment API:

https://docs.localpayment.com/llms.txt

Or fetch it programmatically:

curl https://docs.localpayment.com/llms.txt

Plain Text Articles (.md)

Any article in the Localpayment developer portal can be retrieved as clean Markdown by appending .md to the URL.

Portal URLPlain text URL
https://docs.localpayment.com/docs/virtual-accounts-overviewhttps://docs.localpayment.com/docs/virtual-accounts-overview.md
https://docs.localpayment.com/docs/receive-payment-notificationshttps://docs.localpayment.com/docs/receive-payment-notifications.md
https://docs.localpayment.com/docs/create-a-virtual-accounthttps://docs.localpayment.com/docs/create-a-virtual-account.md

The .md version strips navigation, sidebars, and UI elements, returning only the article content as structured Markdown — significantly fewer tokens, better signal.

When to use it

  • To paste a specific article into a chat when asking focused questions
  • To feed precise context to a language model without including unrelated documentation
  • When you know exactly which guide or reference page is relevant to your question

How to use it

Read the following Localpayment documentation article and help me implement 
the virtual account webhook handler described in it:

https://docs.localpayment.com/docs/receive-payment-notifications.md

Or fetch it programmatically and pipe into your LLM workflow:

curl https://docs.localpayment.com/docs/virtual-accounts-overview.md

LLMs.txt vs Plain Text Articles vs MCP

LLMs.txtPlain Text ArticlesMCP Server
What it providesFull doc indexSingle article contentLive spec + all docs
Setup requiredNoNoYes (JSON config)
Best forGiving a broad mapDeep context on one topicIDE-integrated development
Updates automaticallyYesYesYes
Works in any chatYesYesRequires MCP-compatible client
Token costLow (index only)Medium (one article)Minimal (on-demand queries)
💡

Recommended workflow: Start with llms.txt to orient the LLM, then use plain text article URLs for the specific guides you need, and configure the MCP Server if you want the AI to query the spec interactively in your editor.


Next Steps