Skip to content

Conversation

@neekolas
Copy link
Contributor

@neekolas neekolas commented Oct 22, 2025

Add XMTP agent configuration guide to document how to configure an agent to pay for messages in configure-agent.mdx

Add a new documentation page that outlines XMTP agent setup for message payments, including signer and payer requirements, RPC configuration, and a TypeScript example using Agent.create.

  • Add configuration steps and constraints for signer (EOA only) and messagePayer
  • Specify XMTP Chain RPC URL requirements and environment options
  • Provide TypeScript example for Agent.create with signer, rpcUrls.xmtp, dbEncryptionKey, env, and messagePayer in configure-agent.mdx

📍Where to Start

Start with the new documentation content in configure-agent.mdx, focusing on the Agent.create example and the signer and messagePayer requirements section.


📊 Macroscope summarized a2e048f. 0 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

<!-- MACROSCOPE_FOOTER_END -->\<!-- Macroscope's pull request summary ends here -->

@vercel
Copy link

vercel bot commented Oct 22, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs-xmtp-org Ready Ready Preview Comment Oct 23, 2025 6:14pm

Copy link
Contributor Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@neekolas neekolas mentioned this pull request Oct 22, 2025
@neekolas neekolas force-pushed the 10-22-add_agent_configuration_guide branch from 2137234 to 4549720 Compare October 22, 2025 21:34
@neekolas neekolas force-pushed the 10-22-add_agent_configuration_guide branch from 4549720 to 4e9d3df Compare October 22, 2025 21:46
@neekolas neekolas changed the base branch from 10-16-gateway_config_updates to graphite-base/451 October 23, 2025 18:08
@neekolas neekolas force-pushed the 10-22-add_agent_configuration_guide branch from 4e9d3df to 9a8eb0f Compare October 23, 2025 18:11
@graphite-app graphite-app bot changed the base branch from graphite-base/451 to main October 23, 2025 18:11
1. An agent built using our Node or Agent SDK
2. A payer wallet that has been [funded through the XMTP Funding Portal](./fund-your-app.mdx)

## Setup your Signer
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Setup your Signer
## Setup your Payer Wallet


## Setup your Signer

When you create a client, you already specify a `Signer` that is used to link your XMTP identity to a wallet. You can choose to use the same `Signer` to pay for messages, or create a new one purely for this purpose.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When you create a client, you already specify a `Signer` that is used to link your XMTP identity to a wallet. You can choose to use the same `Signer` to pay for messages, or create a new one purely for this purpose.
When you create a client, you already specify a `Signer` that is used to link your XMTP identity to a wallet. You can choose to use the same `Signer` as your payer wallet, or create a new one purely for this purpose. In either case, it must be the same wallet you [funded through the XMTP Funding Portal](./fund-your-app.mdx)


When you create a client, you already specify a `Signer` that is used to link your XMTP identity to a wallet. You can choose to use the same `Signer` to pay for messages, or create a new one purely for this purpose.

This Signer must be of type `eoa`. The `messagePayer` may not be a smart contract wallet, since the signatures need to be able to be verified offchain.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This Signer must be of type `eoa`. The `messagePayer` may not be a smart contract wallet, since the signatures need to be able to be verified offchain.
This Signer must be of type `eoa`. The `messagePayer` may not be a smart contract wallet, since the signatures need to be able to be verified offchain.
:::info
You can fund your payer wallet from a smart contract wallet [using the XMTP Funding Portal](./fund-your-app.mdx).
:::

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants