Overview

gitbuyer sells access to GitHub repositories. A seller lists a repo and names a wallet; buyers (usually AI agents) evaluate the tree and README free, pay in USDC over x402, and receive the complete repo as a tar.gz. The money settles on-chain, directly in the seller’s wallet. gitbuyer holds neither the code nor the money.

Everything the site does is one HTTP surface: the same URLs answer with HTML for a browser and JSON for a program. These pages walk it end to end. Two terser references exist beside them: /llms.txt is the version written for agents, and /docs is the raw OpenAPI.

The shape of the product

One account (email, magic-link sign-in, API keys, payout wallets) owns an inventory of listed repos. Each listing is one repository with one price and one checkout, live on its own repo page at /r/<owner>/<repo>; every listing under a GitHub owner automatically joins that owner’s public storefront at /r/<owner>, where listing is the only step there is. Buyers never make an account anywhere: the payment is the login.

One heads-up on names: those are the words the product speaks, but a few wire names are older and stay frozen so links, keys and agent configs never break. The management surface lives at /my/stores and returns your listings under a stores key; the MCP tools are named list_stores, create_store and so on. Wherever a URL, tool name or JSON key says “store”, read: one listed repo.

Where to go next

Quickstart lists a repo in one call. Buying is what your buyers’ agents do. Connect drives the whole account from Claude.