> For the complete documentation index, see [llms.txt](https://browsr-documentation.gitbook.io/browsr-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://browsr-documentation.gitbook.io/browsr-documentation/introducing-browsr..md).
# Introducing Browsr.
**Browsr** is a multimodal, agentic LLM interface architected for frictionless interaction with structured and unstructured blockchain data across EVM chains and L1s. \
\
Leveraging NLP, Semantic Search, and Machine Code Parsing (MCP), it enables autonomous access to on-chain state, ABI surfaces, runtime traces, and exfiltrated off-chain signals (e.g., breached credentials, CVEs).
Watch autonomous agents work their magic using Browsr.
The protocol leverages real-time ML inference and smart contract introspection to offer a unified search substrate—capable of converting smart contract metadata, event logs, and low-level hex traces into semantically-relevant, query able representations for trading, security, and monitoring.\
\
**Website:** browsr.ai/
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://browsr-documentation.gitbook.io/browsr-documentation/introducing-browsr..md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.