Skip to main content

Integrate with an AI coding assistant

Point Codex, Claude Code, Copilot, Gemini CLI or Cursor at this documentation and it will write the integration against the real endpoints, parameters and signature rules instead of guessing them.

What the assistant reads

The machine-readable copy of the documentation is written on every build, so it cannot fall behind the site.

llms.txt

An index of every page, grouped the way the site is, with a line describing each one. Start here.

/docs/en/llms.txt

llms-full.txt

The whole documentation as a single Markdown file, for a model with a large context window.

/docs/en/llms-full.txt

Set it up in your tool

Pick your tool, create the file it names in your project and paste the contents in. Nothing else changes.

Claude Code discovers the skill and loads it when a task calls for it — adding the file is the only step.

.claude/skills/bog-api-docs/SKILL.md
---
name: bog-api-docs
description: Bank of Georgia API documentation. Use when working on online payments, payment links, billing, online instalments, business internet banking or open banking — integrating with api.bog.ge, wiring up callbacks or request signatures, or debugging a failing payment.
---

# Bank of Georgia API documentation

The documentation is published in a machine-readable form. Read it before
writing code: do not guess endpoints, parameter names or signature rules.

## How to work through it

1. Fetch the index of every page: https://api.bog.ge/docs/en/llms.txt
   Each entry carries a line describing the page, so the index alone is enough
   to tell which pages the task needs.
2. Fetch only those pages. Any page is available as Markdown by appending
   `.md` to its URL (for example https://api.bog.ge/docs/en/payments/standard-process/create-order.md).
3. If the whole documentation is genuinely needed at once: https://api.bog.ge/docs/en/llms-full.txt
   It is a large file — reach for the index first.

## What to watch for

- Test against the sandbox before going to production: https://api.bog.ge/docs/en/sandbox/payments/introduction.md
- Never put `client_secret` in code that runs on the client.
- Always verify the signature on a callback, and take a payment's status from a
  verified callback or from the payment details method — never from the
  redirect the customer lands on.
- The open banking APIs are described by OpenAPI documents rather than pages;
  they are linked at the end of llms.txt.
View SKILL.md

What you can then ask for

From that point on the assistant answers integration questions from the documentation rather than from memory.

  • Create an order and redirect the customer to the payment page
  • Verify a callback signature and handle the result
  • Save a card and charge it later
  • Complete a pre-authorisation — approve it or reject it
  • Refund an order in full or in part
  • Add Google Pay or Apple Pay to my own page
  • Pull an account statement from Business Internet Banking
  • Test against the sandbox before going to production