Skip to content

Add x402#3804

Open
sriakula1 wants to merge 2 commits intosindresorhus:mainfrom
xpaysh:add-x402
Open

Add x402#3804
sriakula1 wants to merge 2 commits intosindresorhus:mainfrom
xpaysh:add-x402

Conversation

@sriakula1
Copy link

@sriakula1 sriakula1 commented Dec 8, 2025

https://github.com/xpaysh/awesome-x402#readme

Why it should be included: x402 is the HTTP 402 Payment Required protocol - a web standard for internet-native payments. It enables AI agents to autonomously pay for API access and services. The protocol is backed by Coinbase and Cloudflare, with 500K+ weekly transactions.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

  • Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
  • Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
  • You have to review at least 2 other open pull requests.
  • You have read and understood the instructions for creating a list.
  • This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
  • Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot.
  • Your entry should be added at the bottom of the appropriate category.
  • The title of your entry should be title-cased and the URL to your list should end in #readme.
  • No blockchain-related lists.
  • The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

  • Has been around for at least 30 days. First commit: 2025-11-02 (36+ days)
  • Run awesome-lint on your list and fix the reported issues.
  • The default branch should be named main, not master.
  • Includes a succinct description of the project/theme at the top of the readme.
  • It's the result of hard work and the best I could possibly produce.
  • The repo name of your list should be in lowercase slug format: awesome-x402.
  • The heading title of your list should be in title case format: # Awesome X402.
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have awesome-list & awesome as GitHub topics.
  • Not a duplicate. Please search for existing submissions.
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs.
  • Includes a project logo/illustration whenever possible.
  • Entries have a description, unless the title is descriptive enough by itself.
  • Includes the Awesome badge.
  • Has a Table of Contents section.
  • Has an appropriate license: CC0-1.0.
  • Has contribution guidelines.
  • All non-important but necessary content grouped in a Footnotes section at the bottom of the readme.
  • Has consistent formatting and proper spelling/grammar.
  • Does not use hard-wrapping.
  • Does not include a CI badge.
  • Does not include an Inspired by awesome-foo or Inspired by the Awesome project link at the top of the readme.

unicorn

@sriakula1
Copy link
Author

PRs Reviewed

As required, I reviewed 2 open pull requests with substantive feedback:

  1. Add Parquet #3781 (Add Parquet) - Found inconsistent punctuation in entry descriptions. Several entries missing terminal periods.

  2. Add PDF #3737 (Add PDF) - PR description describes the list contents rather than the topic itself. Suggested improvement to follow guidelines. Also noted a grammar issue ("ensure" → "ensuring").


unicorn

Copy link
Contributor

@Mo-way Mo-way left a comment

Choose a reason for hiding this comment

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

Sorry to say this:
In my opinion, you didn't do an actual review of other PRs. Your "reviews" are AI generated and basically a long "lgtme", but in form that takes 30s instead of 1s to parse mentally.

Copy link

@MalloryWittwer MalloryWittwer left a comment

Choose a reason for hiding this comment

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

Hey @sriakula1 , thank you for submitting your list. After reviewing it, I have a few suggestions on how you could improve it:

  • The title of your list is "Awesome X402". I suppose the title of your PR should therefore be "Add X402" with a capitalized X, for consistency?
  • In your entry, the "x" in "x402" should probably be capitalized to comply with the PR template requirements.
  • The short description next to your entry could probably be shorter; I would suggest simply "HTTP 402 Payment Required protocol".
  • Your entry is at the bottom of the "Decentralized Systems" section. Would it not make more sense to have it at the end of "Networking" (I don't have a strong opinion on this)?
  • I find that how you present your list at the top of the README as "The Ultimate x402 Resource Hub..." sounds a bit like marketing blurb. Could you consider a simple and objective description of what X402 is and its interest instead? For the same reason, I would suggest removing the lines around "Start building in 5 minutes [...]" below the Contents section.
  • I see that Claude is a contributor to the project. This makes me wonder if and how much you've used AI to help you write your list?
  • I would suggest removing the extended parts of your list that don't contain links, for example those under the "Production Implementations" or "Use Cases & Patterns" section.
  • I would suggest to keep only a link to your CONTRIBUTING.md file under the "Contributing" section at the end of your list, and to remove the rest of that section, so you don't have to maintain the contributing guidelines in two places.

Looking forward to see the final version of your list!

@athman3
Copy link

athman3 commented Dec 27, 2025

Reviewed this list. Found multiple broken links in Protocol Implementations (all "Other Languages" entries), Example Applications, Tools, Testing, and Tutorials sections. These return 404 errors.

@athman3 athman3 mentioned this pull request Dec 27, 2025
33 tasks
- Capitalize X402 in title for consistency
- Shorten description to focus on HTTP protocol
@sriakula1
Copy link
Author

Reviewed this list. Found multiple broken links in Protocol Implementations (all "Other Languages" entries), Example Applications, Tools, Testing, and Tutorials sections. These return 404 errors.

Legit feedback, broken links are now fixed. Thx for the review

@sriakula1
Copy link
Author

sriakula1 commented Dec 30, 2025

Hey @sriakula1 , thank you for submitting your list. After reviewing it, I have a few suggestions on how you could improve it:

  • The title of your list is "Awesome X402". I suppose the title of your PR should therefore be "Add X402" with a capitalized X, for consistency?
  • In your entry, the "x" in "x402" should probably be capitalized to comply with the PR template requirements.
  • The short description next to your entry could probably be shorter; I would suggest simply "HTTP 402 Payment Required protocol".
  • Your entry is at the bottom of the "Decentralized Systems" section. Would it not make more sense to have it at the end of "Networking" (I don't have a strong opinion on this)?
  • I find that how you present your list at the top of the README as "The Ultimate x402 Resource Hub..." sounds a bit like marketing blurb. Could you consider a simple and objective description of what X402 is and its interest instead? For the same reason, I would suggest removing the lines around "Start building in 5 minutes [...]" below the Contents section.
  • I see that Claude is a contributor to the project. This makes me wonder if and how much you've used AI to help you write your list?
  • I would suggest removing the extended parts of your list that don't contain links, for example those under the "Production Implementations" or "Use Cases & Patterns" section.
  • I would suggest to keep only a link to your CONTRIBUTING.md file under the "Contributing" section at the end of your list, and to remove the rest of that section, so you don't have to maintain the contributing guidelines in two places.

Looking forward to see the final version of your list!

Thanks for the detailed review mate! very helpful
Fixed:

  • Capitalized X402 in the entry
  • Shortened description to just "HTTP 402 Payment Required protocol"
  • Removed all the broken placeholder links

Re: Claude contributor - yeah I use terminal copilots, but who doesn't these day :) but link curation and verification is manual. The broken ones slipped through, now fixed.

Keeping it in Decentralized Systems as I feel it's more relevant, but open to Networking if maintainers prefer, as at the end of the day, it's an HTTP protocol

@sriakula1
Copy link
Author

Sorry to say this: In my opinion, you didn't do an actual review of other PRs. Your "reviews" are AI generated and basically a long "lgtme", but in form that takes 30s instead of 1s to parse mentally.

Did use AI but not entirey. However, noted. Will be more specific with reviews.

Copy link
Contributor

@Mo-way Mo-way left a comment

Choose a reason for hiding this comment

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

IMO: You repo reads like a marketing post, not an awesome list.
See feedback by MalloryWittwer.

Also, if you use claude to do the work, I think it is extremely rude to just add its content to PRs and let others check for issues like broken links.

@Mo-way
Copy link
Contributor

Mo-way commented Jan 2, 2026

Don't get me wrong, though: the topic of micro payments is very cool and interesting.
Only, the last thing x402 needs IMO, is another marketing post.

I tried to google it and was only able to find ads and marketing and hype, but very little neutral or factual information.
At least the official web page has an FAQ, but that was all i could find quickly.

@Mo-way
Copy link
Contributor

Mo-way commented Jan 3, 2026

Reviewed this list. Found multiple broken links in Protocol Implementations (all "Other Languages" entries), Example Applications, Tools, Testing, and Tutorials sections. These return 404 errors.

Legit feedback, broken links are now fixed. Thx for the review

Oh wow, the topic actually sparked my interest. But it turns out, the commit that "replaces the dead links" removes a lot of dead links, while leaving the remaining dead links unchanged...

So much for your claim "Did use AI but not entirey"... I'm lost for words, so I asked ChatGPT how to reply this behavior:

“Your review process is like a unicorn—everyone talks about it, nobody’s seen it.”

This was referenced Jan 10, 2026
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.

7 participants