Skip to content

Conversation

@deathbyknowledge
Copy link
Contributor

Summary

Screenshots (optional)

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The documentation style guide has been adhered to.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

@github-actions github-actions bot added size/m product:agents Build and deploy AI-powered Agents on Cloudflare that can act autonomously. September 2025 labels Sep 22, 2025
onStart() {
// We instantiate a wallet from which the agent will pay
const pk = process.env.CLIENT_TEST_PK as `0x${string}`;
const agentAccount = privateKeyToAccount(pk);
Copy link
Contributor

Choose a reason for hiding this comment

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

should this be called "wallet"?

(Since that's how it is described in the sentence above the code snippet and is most specific)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not entirely sure on the difference on wallet vs account. Since the x402 types are Account I'll stick to that wording. I've updated the comments to make it more clear as well.

fetchWithPay!: ReturnType<typeof wrapFetchWithPayment>;

onStart() {
// We instantiate a wallet from which the agent will pay
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
// We instantiate a wallet from which the agent will pay
// Create a temporary wallet that the agent will use to pay

Copy link
Contributor

Choose a reason for hiding this comment

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

My understanding is this is a temporary wallet. Yes? No?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, privateKeyToAccount is deterministic and always derives the same wallet (I'm not sure of the naming either) from a given private key.
So what's expected is that you only need to load your private key into your Worker's secrets and your wallet will be ready to use.

const url = new URL(req.url);
console.log("Trying to fetch paid API");

// We use the x402 fetch to access our paid endpoint
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
// We use the x402 fetch to access our paid endpoint
// Use the x402 compatible fetch (fetchWithPay) to access the paid endpoint

// The first parameter becomes the confirmation callback.
// We can set it to `null` if we want the agent to pay automatically.
const res = await this.x402Client.callTool(this.onPaymentRequired, {
name: toolName,
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be an example tool? Otherwise I read this and wondered what this was referencing

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've added toolName and toolArgs as parameters to fix this

}

onPaymentRequired(paymentRequirements): Promise<boolean> {
// Your HIL confirmation flow...
Copy link
Contributor

Choose a reason for hiding this comment

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

What's HIL?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

"Human-in-the-loop", updated it to use that instead to make it more clear

}
```

We also include an MCP client that you can use from anywhere (not just your Agents!) to pay for these tools.
Copy link
Contributor

Choose a reason for hiding this comment

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

Where would someone use this outside of an agent? Example might help

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Any application that connects to MCP servers is using some version of an MCP client. The wrapper agents wraps the official MCP client to support paid tool calls (which are not officially part of the spec)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

e.g. Windsurf wants to support MCPs with paid tools, so they'll need an MCP client that can handle payments

const X402_CONFIG: X402Config = {
network: "base",
recipient: env.MCP_ADDRESS,
facilitator: { url: "https://x402.org/facilitator" }, // Payment facilitator URL
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this something that I need to set myself or do I just use this URL as the default?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

AFAIK this one is the official (?) supported payment facilitator that handles payment verifications/settling for servers, and should work for most networks. Some users might want to use different facilitators so they could update it.

In any case, I've added an inline comment to docs on facilitators (https://x402.gitbook.io/x402/core-concepts/facilitator)

Copy link
Contributor

@irvinebroque irvinebroque left a comment

Choose a reason for hiding this comment

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

Stamp so you have it, see comments

@threepointone
Copy link
Contributor

let's land this tomorrow right before the announcement

@threepointone threepointone merged commit a294db3 into cloudflare:production Sep 23, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:agents Build and deploy AI-powered Agents on Cloudflare that can act autonomously. September 2025 size/m

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants