Skip to main content
Integrate Byzantine faster with your coding agent. Pick what you need; they work well together.

Docs MCP

Your agent searches these docs. Read-only.

Agent skills

Step-by-step playbooks and helpers, checked against the API.

Plain-text docs

Any page as markdown, for pasting into a chat.

​
Quick start

1

Install the skills

2

Add the docs MCP server

3

Ask your agent

“Integrate Byzantine in my app. Start with the sandbox: create an individual account, then a deposit.”
Your agent follows the Integration guide and the skills.

​
Docs MCP server

https://docs.byzantine.fi/mcp lets your agent search these docs. It can look things up; it cannot create accounts or move funds.

​
Agent skills

The Byzantine agent skills teach Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI, Windsurf and other agents how Byzantine works and how to integrate it.

Onboarding

Individual KYC, company KYB, associated persons, passkeys.

Request signing

The signing contract, a request helper and a 401 diagnostic.

Money movement

Passkey-approved deposits and withdrawals, statuses.

Webhooks

Signature verification, events, replay.

​
Plain-text docs

Append .md to any page URL to get it as markdown. The full index is at /llms.txt.

​
Safe defaults

Sandbox first

Build in the sandbox. The bundled scripts only call the sandbox, never production.

Keep keys out of chats

If a private key was pasted into a conversation, revoke it in the integrator dashboard (Settings → API keys) and create a new one.

Read-only keys for reporting

Use a read_only key for dashboards, reporting and support tools.

Funds stay under user control

Your agent cannot move funds on its own: every deposit and withdrawal needs the user’s passkey. See the Integration guide.