AI Tooling

How AI tools can consume Bkper docs, API references, discovery endpoints, and agent context.

Every page on bkper.com is available as clean Markdown. Navigation chrome — sidebar, header, footer — is stripped, reducing token usage for AI tools.

Formats

Three ways to get docs into your AI. Pick the one that matches your workflow.

`llms.txt` — explore

A structured index of every article with descriptions. Start here when you want your AI to browse and pick what to read.

/llms.txt — all site content
/docs/llms.txt — all docs
/docs/ai/llms.txt — AI docs
/docs/guides/llms.txt — user-facing guides
/docs/build/llms.txt — developer docs
/docs/api/llms.txt — API libraries at a glance

`llms-full.txt` — deep dive

The complete text of every article in a scope. No links to chase, no extra requests. Use this when you need comprehensive context on a specific topic.

/llms-full.txt — all site content
/docs/llms-full.txt — all docs
/docs/ai/llms-full.txt — all AI docs
/docs/build/apps/llms-full.txt — all app docs
/docs/build/scripts/llms-full.txt — all script docs

`.md` — single page

Any individual page as Markdown. Use this when you already know the exact page you need.

Append .md to the URL:

https://bkper.com/about.md
https://bkper.com/docs/core-concepts.md
https://bkper.com/docs/ai/cli-vs-mcp.md

curl https://bkper.com/docs/core-concepts.md

Or request it via the Accept header — no URL modification needed:

curl https://bkper.com/docs/core-concepts \
  -H "Accept: text/markdown"

The response includes an x-markdown-tokens header with the estimated token count, which agents can use to plan context window usage:

HTTP/2 200
content-type: text/markdown; charset=utf-8
vary: Accept
x-markdown-tokens: 1850

Every documentation page also has a Page Options dropdown in the right sidebar:

Page Options dropdown showing copy, view, and AI actions

Copy the page as Markdown, open it directly in Claude or ChatGPT, or grab a ready-made prompt for your AI tool of choice.

API references

API reference endpoints compile the library overview and full spec into a single compact document optimized for agent workflows:

/docs/api/rest.md — endpoints, parameters, and data models
/docs/api/bkper-js.md — bkper-js README + TypeScript definitions
/docs/api/bkper-gs.md — bkper-gs README + TypeScript definitions
/docs/api/bkper-api-types.md — shared TypeScript type definitions
/docs/api/bkper-web-auth.md — OAuth browser SDK

Compiled Markdown vs raw source:

Library	Raw tokens	`.md` tokens	Reduction
REST API	~38K	~9K	4×
bkper-js	~32K	~18K	1.8×
bkper-gs	~22K	~12K	1.9×
bkper-api-types	~12K	~5K	2.4×
bkper-web-auth	~2K	~2K	~1×

Agent skills and plugins

For coding agents that support the Agent Skills standard and can run local shell commands, install the Bkper CLI skill:

npx skills add bkper/bkper-cli --skill bkper-cli

The skill is a portable companion for external agents such as Claude Code, Codex, OpenCode, OpenClaw, Hermes Agent, Cursor, and similar tools. It is generated from the Bkper CLI agent configuration and gives other harnesses Bkper’s from-to accounting model, CLI references, SDK pointers, and safety guardrails for operating the local bkper CLI.

Install and authenticate the CLI first when the agent needs live Bkper access:

npm i -g bkper
bkper auth login

For the built-in terminal agent, see Bkper CLI Agent. For hosted connector access without local tools, see Bkper MCP Server. For coding workflows, see Coding Agents.

Source on GitHub.