Agent Native | Binance Web3 API

Agent Native

Two complementary interfaces for AI tools, coding assistants, and autonomous agents. Discover, read, and interact with Binance Web3 API documentation programmatically.

Core Components

Choose the integration method that fits your use case. Each component serves a different purpose — use them individually or together.

Static files

llms.txt

A lightweight discovery protocol. AI tools fetch static files to understand what documentation is available and load full content.

Learn more

MCP Server

Native integration for AI IDEs via Model Context Protocol. Search docs, generate code, and test API calls directly.

Coming soon

Quick Start

Fetch documentation with llms.txt

Code
# Summary — document titles, descriptions, and links
curl -s https://web3.binance.com/en/dev-docs/llms.txt

# Full content — complete documentation in a single file
curl -s https://web3.binance.com/en/dev-docs/llms-full.txt

The MCP Server quick start will be published once the interface is available.

Who Is This For?

Whether you're building with AI IDEs or integrating documentation into agent pipelines, there's a tool for your workflow.

AI IDE Users

Using Claude Code, Cursor, or Windsurf? The MCP Server will give you native tool integration — search docs and generate code without leaving your editor.

LLM Application Builders

Use llms.txt to inject up-to-date Binance Web3 API documentation into your prompts and agent context.

Prompt Engineers

Use llms.txt to feed complete Binance Web3 API documentation into any LLM. Perfect for building prompts with up-to-date API context.

How They Work Together

AI Tool / Agent

llms.txt → Quick discovery: "What docs exist?"

MCP Server → Native integration: "Search docs, generate code, test API"

Last modified on June 17, 2026

llms.txt

Agent Native

Two complementary interfaces for AI tools, coding assistants, and autonomous agents. Discover, read, and interact with Binance Web3 API documentation programmatically.

Core Components

Choose the integration method that fits your use case. Each component serves a different purpose — use them individually or together.

Static files

llms.txt

A lightweight discovery protocol. AI tools fetch static files to understand what documentation is available and load full content.

Learn more

MCP Server

Native integration for AI IDEs via Model Context Protocol. Search docs, generate code, and test API calls directly.

Coming soon

Quick Start

Fetch documentation with llms.txt

Code
# Summary — document titles, descriptions, and links
curl -s https://web3.binance.com/en/dev-docs/llms.txt

# Full content — complete documentation in a single file
curl -s https://web3.binance.com/en/dev-docs/llms-full.txt

The MCP Server quick start will be published once the interface is available.

Who Is This For?

Whether you're building with AI IDEs or integrating documentation into agent pipelines, there's a tool for your workflow.

AI IDE Users

Using Claude Code, Cursor, or Windsurf? The MCP Server will give you native tool integration — search docs and generate code without leaving your editor.

LLM Application Builders

Use llms.txt to inject up-to-date Binance Web3 API documentation into your prompts and agent context.

Prompt Engineers

Use llms.txt to feed complete Binance Web3 API documentation into any LLM. Perfect for building prompts with up-to-date API context.

How They Work Together

AI Tool / Agent

llms.txt → Quick discovery: "What docs exist?"

MCP Server → Native integration: "Search docs, generate code, test API"

Last modified on June 17, 2026

llms.txt