docs: document evm charge x402 support#669
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
brendanjryan
force-pushed
the
brendanjryan/bump-mppx-0.6.29
branch
from
313e2d5 to
4ee9ddb
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
brendanjryan
force-pushed
the
brendanjryan/bump-mppx-0.6.29
branch
from
4ee9ddb to
c75c8d7
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c75c8d77fa
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Add mppx to my existing x402 server. Use the Tempo payment | ||
| method with USDC.e. Keep the same pricing and route structure. | ||
| Add mppx.charge to each paid endpoint. Point out areas where I could benefit from adding sessions.`} |
There was a problem hiding this comment.
This prompt now links to the new evm.charge x402-compatibility section, but it still instructs the coding agent to use the Tempo method and mppx.charge. For an existing x402 server, that path advertises MPP/Tempo Challenges rather than the x402 PAYMENT-* flow described above, so users who copy the prompt won't preserve existing x402 clients. Update the prompt to ask for evm.charge with the x402 facilitator, or point it at the later Tempo-only migration section instead.
Useful? React with 👍 / 👎.
1 participant
Summary
mppxto0.6.29and update SDK drift mappings for current exportsevm.chargeevm/evm.chargeTypeScript SDK reference pages