Reference the LLMs.txt

Overview

The Launchpay Developer Portal publishes an llms.txt file, a structured index of all documentation on the portal, including Guides, API Reference pages, and Changelog entries. AI tools can use this file to discover and retrieve documentation content, giving developers accurate, grounded answers about Infinicept's APIs and integration patterns.

The file contains a categorized list of every page on the portal with titles, descriptions, and direct links to the Markdown (.md) version of each page. When an AI tool reads this file, it gets a complete map of what documentation is available and where to find it.

URL: https://developer.launchpay.com/llms.txt

What It Covers

  • Guides: Integration walkthroughs, webhook setup, credential retrieval flows, and feature overviews
  • API Reference: Links to every published endpoint reference page
  • Changelog: Recent updates and changes to the platform and documentation

How to Use LLMs.txt with Your AI Tools

The process is the same across AI tools, Claude, ChatGPT, Gemini, Cursor, Windsurf, and others. At the start of each new conversation or session, include the llms.txt URL alongside your prompt. The AI tool will fetch the file, identify the relevant documentation pages, and use them to answer your question.

Provide the URL Directly

Many AI tools require a LLMs.txt URL to be explicitly provided in the conversation or prompt before the tool can fetch its contents due to security reasons. The full llms.txt URL must be included each session. It does not persist across conversations.

Example prompt:

Reference the Launchpay documentation index at:
https://developer.launchpay.com/llms.txt

How do I retrieve gateway credentials after a merchant is boarded for CNP processing?

If your AI tool cannot fetch URLs directly, you can visit https://developer.launchpay.com/llms.txt in your browser, copy the contents, and paste them into your conversation as context.

Support

Have a question? Contact us on the Customer Support Portal.

Learn about updates in our Changelog.






Did this page help you?