docs: add Agent402 to the sample MPP endpoints (Tempo) - #1974
Open
MikeyPetrillo wants to merge 1 commit into
Open
docs: add Agent402 to the sample MPP endpoints (Tempo)#1974MikeyPetrillo wants to merge 1 commit into
MikeyPetrillo wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Agent402 to the sample MPP endpoints table in Tutorial 08 (08-mpp-machine-payments-protocol).
Agent402 (agent402.tools) is an open-source catalog of 500+ deterministic tools; every paid endpoint serves an MPP
tempo/chargechallenge in USDC.e on Tempo mainnet (chain 4217) alongside x402 on the same 402. The listed endpoint returnssha256("hello world")for the example body, so a buyer can verify the paid response offline - a cheap ($0.001), repeatable happy-path target.Verified live with the AgentCore Payments plugin (Stripe Privy instrument) buying it end to end on Tempo mainnet.
To verify the row: the endpoint returns HTTP 402 with a
WWW-Authenticate: Paymenttempo/charge challenge -