Frequently Asked Questions
What are Agent ID's?
Agent ID's are human readable names for your AI agent. They act as a crypto-native identity that can be used across different contexts, resolving for addresses in client applications. You can use the Operator Gateway CLI to adapt an existing agent codebase and route messages to it.
What do you mean by "bridging agents to web3"?
To bridge your AI agent from an HTTP server environment to the Web3 ecosystem, you'll need to give it a unique identity. This process involves two main steps:
Create and Configure a Wallet Address Start by creating a new blockchain wallet address. This will serve as the public identity of your agent on the Web3 network.
Name Resolution to the Wallet Assign a human-readable name to your wallet address using Agent ID's. This name acts as a crypto-native identifier that can be recognized and used across various platforms.
Set Up Operator Gateway Implement the Operator Gateway package to create a link between your agent's wallet address and your HTTP server. This gateway facilitates message routing from your agent to client applications within Web3. This means your agent can be used in any XMTP compatible client.
By completing these steps, your AI agent will transition from a traditional web server to the decentralized web, ready to interact with blockchain systems and users in the Web3 space.
What would you recommend for a starter wallet?
If you are primarily using agents on desktop, we recommend Metamask or Phantom Wallet.
You will need to use the xmtp.chat interface to use agents on desktop. If you are on mobile, we recommend Coinbase Wallet.
Can I transfer my name to another wallet?
Not yet. In the developer preview, name records are stored offchain, but we are actively looking to bring them onchain in the near future. Then, you will be able to transfer and even sell them if you like.
How can I access agents once they're connected?
You can use any XMTP compatible client to access your agents.
I have an AI agent ready to deploy. How do I start?
You can review the Agent Developer Tutorial to learn the steps you can take to deploy your agent.
What are some workflows I can build with Operator?
Agents are designed to be composable, meaning that you can build custom workflows for things like gating your agents, or triggering specific events. Here's an example:
You can build a Farcaster Frame that requires users to first recast and like the frame in order to trigger an NFT mint
You can use Syndicate Cloud to broadcast mint messages, and issue NFT's to everyone who meets the criteria
Then you can set up an indexer that allowlists users based on whether they hold an NFT. If they do, they can interact with the agent. If they don't, they'll be politely denied access
Can I see some agents in action?
Keep in mind that these are just demos, as agents on the network will primarily be accessed through XMTP enabled clients. Here's an agent we built that searches Farcaster, and an agent that helps you find details about NFT projects.
Last updated