Documentation sections
Documentation/Recipes
AI and tooling
AI prompt, llms.txt, OpenAPI spec and SDK generation
Integrating with AI
If Cursor, Claude, ChatGPT, or another AI tool is writing your integration, don't make it crawl these pages: copy the ready-made prompt - it bundles the instructions and the full API documentation into a single text. Fill in your stack where marked and send it to the agent.
llms.txt
For tools that can read documentation on their own, the llms.txt standard applies:
- tabpay.org/llms.txt - a table of contents with links;
- tabpay.org/llms-full.txt - the entire documentation as a single Markdown file: contracts, webhook signature with code, statuses, errors, and an integration checklist.
OpenAPI specification
The machine-readable API contract is available at tabpay.org/openapi.json (OpenAPI 3.1, including the webhook and signature description). What you can do with it:
- import it into Postman or Insomnia to get a ready-made request collection;
- generate a typed client for your language;
- pass it to an AI agent along with llms-full.txt.
# Typed client from the OpenAPI specification (openapi-typescript)
npx openapi-typescript https://tabpay.org/openapi.json -o tabpay-schema.tsThere are no official SDKs yet, and that's deliberate: the API is compact, and a client generated from the specification always matches the live contract.