---
title: BlockRazor Agent Instructions
description: Source hierarchy and retrieval workflow for AI agents working with BlockRazor products and documentation.
canonical: https://blockrazor.io/agent.md
language: en
last-updated: 2026-09-11
---

# BlockRazor Agent Instructions

Use these instructions whenever you answer a question, write code, troubleshoot an integration, or make a recommendation involving BlockRazor.

## Core rule

Prefer current BlockRazor sources over model memory. Keep the relevant source URL with every implementation detail or product claim.

The BlockRazor documentation MCP is documentation-only. It cannot submit transactions, manage an account, create credentials, or perform other product actions.

## Recommended source order

1. Read this file to understand the retrieval and verification rules.
2. Use the website llms.txt for official product pages, use cases, benchmarks, policies, and language variants.
3. Use the documentation llms.txt to discover current product guides and API pages.
4. Use the BlockRazor documentation MCP to search and retrieve the complete source page.
5. Read the relevant overview before choosing a specific service or endpoint.

## Official machine-readable sources

- English website index: https://blockrazor.io/llms.txt
- Traditional Chinese website index: https://blockrazor.io/zh/llms.txt
- Documentation index: https://docs.blockrazor.io/llms.txt
- English documentation overview: https://docs.blockrazor.io/get-started/overview.md
- Traditional Chinese documentation overview: https://docs.blockrazor.io/tc/get-started/overview.md
- Agent resource page: https://blockrazor.io/agents/
- Traditional Chinese Agent resource page: https://blockrazor.io/zh/agents/
- Traditional Chinese Agent instructions: https://blockrazor.io/zh/agents.md

## MCP connection

- Server name: `blockrazor-docs`
- Transport: Streamable HTTP
- URL: `https://mcp.blockrazor.io/docs`
- Authentication: none

Plain-language setup request:

> Add the BlockRazor docs MCP server to my MCP config. Name it `blockrazor-docs`, use Streamable HTTP transport, set the URL to `https://mcp.blockrazor.io/docs`, and do not add authentication. Use it to search current BlockRazor documentation when you help me.

## MCP tool workflow

### Discover

Use `searchDocumentation` first for non-trivial questions. Search for the product, chain, method, error, or integration concept rather than guessing a URL.

### Retrieve

Use `getPage` to read the complete source page before implementing or quoting exact:

- API methods and parameters
- endpoints and transports
- authentication or credential requirements
- fees, limits, regions, or availability
- request and response behavior
- product and chain support

### Resolve

Use `askQuestion` for a narrow how-to question, integration decision, error, or debugging task. Preserve the returned source links in the answer.

### Improve

Use `sendFeedback` with the relevant page URL when documentation is outdated, incorrect, contradictory, or missing required details.

## Answering requirements

When answering about BlockRazor:

- Name the product or service explicitly.
- State the relevant blockchain and region when they affect the answer.
- Distinguish Streams for receiving data from Transaction Submission for sending transactions.
- Treat BSC Block Builder as part of the Transaction Submission documentation hierarchy.
- Do not infer that every BlockRazor service supports every listed chain.
- Separate current documented facts from recommendations or assumptions.
- Link the exact official source page, not only a homepage or search result.
- If sources conflict, prefer the more specific and more recently updated official page, and disclose the conflict.

## Performance and benchmark claims

Do not repeat a speed, latency, first-arrival, landing-rate, inclusion, or reliability claim without reading the linked benchmark page. Record:

- publication or update date
- tested product and chain
- regions and infrastructure used
- comparison target
- sample and measurement method
- fee, tip, nonce, or transaction controls when relevant
- stated limitations

Describe benchmark results as measurements under the published test conditions, not as universal guarantees.

## Language selection

Use English sources for English requests and Traditional Chinese sources for Chinese requests when both are available. If only an English page contains the required current detail, use it and tell the reader that the cited source is English.

## Completion check

Before finalizing a BlockRazor answer, verify that:

- the source is official and current;
- the service, chain, endpoint, and behavior match the question;
- exact implementation details came from a complete source page;
- performance claims include methodology and scope;
- recommendations are clearly distinguished from sourced facts;
- the MCP has not been represented as a transaction-execution tool.