🖐️Welcome

I'm Brian 🤖

Brian enables users and AI Agents to interact with Web3 by providing textual prompts to execute various Web3-related actions, such as:

• Transactions: "Can you swap 10 usdc for eth on Ethereum ?"

• Protocol info: "How Uniswap v4 hooks work?"

• Protocol data: "Give me the pools with the highest TVL on Uniswap"

• Smart contract: "Generate an ERC20 with name BrianAI and a supply of 1000 tokens"

The Brian API and Brian TS SDK allow developers to integrate the Brian AI capabilities in their applications to build intent-based apps that could be custodial, non-custodial, or support smart accounts.

The LangChain<>Brian SDK allows devs to launch LangChain AI Agents capable of transacting and deploying tokens on-chain.

The Brian App, built on top of Brian APIs, offers users an interface for performing transactions in a non-custodial way, researching web3 info, and deploying smart contracts by prompt.

If you have any questions or doubts, join our Dev community!

How Brian API works

Brian API is an Intent Recognition and Execution Engine capable of understanding the user intent for Web3 interactions, providing accurate textual answers and data, building transactions, or generating smart contracts.

This is the end-to-end flow of the Brian API.

Anyone can try it on our non-custodial Brian App or API swagger. 1) Prompt/Intent

Users and Agents can prompt their intent for a web3 interaction: ‣"I want to bridge 1 eth to Base and send them to vitalik.eth" ‣"Tell me how Uniswap v4 works" ‣"Deploy an ERC20 with name BrianAl and a supply of 1000 tokens" ‣"What are the top trending tokens today?" 2) Intent Recognition Engine*

Brian Al extracts your intent into parameters and passes them to the execution engine. * Brian mission is to provide the best web3 intent recognition.

3) Intent Execution Engine

The output of the API is built using a series of existing off-chain tools and, for TXs, on-chain aggregators in the market (like Enso Finance or Bungee Exchange).

4) Output

The API output could be:

‣ A TX to sign and execute (by Agents or Users) ‣ Text answer ‣ Code to deploy ‣ Market data