Skip to content
gitbuyer logo

gitbuyer

Lets sellers list GitHub repositories so buyers can clone them after paying in USDC over x402.
At a glanceswept Oct 12, 2026

≈ 6visits/mo

Use not read yet · estimate, read Oct 13, 2026

For
Developers selling GitHub repo clone access, and buyers or agents evaluating code before purchase
Runs as
API
Used for
  • sell clone access to a private GitHub repo
  • preview a repo's tree and readme before buying
  • pay in USDC to clone a repository
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 20, 2026
  • MCP servercom.gitbuyer/mcpverified in the MCP registry
  • Stateanswers, 16 toolschecked 2026-10-20
  • Address to connectgitbuyer.com/mcp
  • OpenAPI spec68 pathsthe spec ↗
  • API docsgitbuyer.com/apithe vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Commerceby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare gitbuyer with

Pick up to two.

All 10 alternatives to gitbuyer →

All Commerce tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use gitbuyer for?

Sign in to leave a note
Questions this page answers
  • What is gitbuyer?

    Lets sellers list GitHub repositories so buyers can clone them after paying in USDC over x402. It is listed in the Atlas under Commerce.

  • Who is gitbuyer for?

    Developers selling GitHub repo clone access, and buyers or agents evaluating code before purchase

  • What are alternatives to gitbuyer?

    In Commerce, by use: 1stDibs, XP, Unstoppable, Whoppah, Printonic, Name.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk