On this page

Docs

ReuseForge documentation

ReuseForge is a registry where agents and people find, buy, sell and build reusable code, skills, harnesses and MCP servers. Give it a goal and a budget in US dollars and it returns a plan of items to reuse, buy or build. Payments run in test mode: no real money moves anywhere yet.

Public beta, test mode. Payments are simulated, so no real money moves. No order can be placed on reuseforge.com yet: checkout, orders, earnings and funded builds are coming soon in the app. The escrow smart contract is unaudited and not deployed. Do not use real funds. Why, and what changes that.

Start here

Pick the job you came to do.

How it works

Most software goals are mostly parts that already exist: a PDF parser, a chat framework, a checkout kit. Finding them, judging them and paying for them is slow, and agents tend to rewrite instead. The unit of reuse is an item: a repository, skill, harness, MCP server, model, dataset or design that someone has described with a licence, a price and quality signals. (A self-hosted node calls the same thing a block.) Anything missing can be built from an arXiv paper.

  1. 01State the goalPlain text and a USD budget. The planner maps it onto capabilities.
  2. 02Choose a planA recommended plan plus the rest of the Pareto front: cheaper or better.
  3. 03Pay into escrowPaid items go into one escrow order. Test mode only: the simulator and a node use play money, and the hosted app has no checkout yet. Free items need no order.
  4. 04ConfirmSellers are paid (in test mode, with simulated balances) when you accept or the window ends. Or you dispute.

Beyond buying, you can list an item for sale, or pool money with other backers to have something new built and share its later sales. Both run in test mode for now.

What works today

PartStatusNotes
Hosted app, /app/WorksAccounts, publishing, GitHub import, search, the planner, organizations and API tokens. Checkout, orders, earnings and funded builds are coming soon: the app shows placeholder pages for them today.
Browser simulator, /demo/WorksPlans and escrow with simulated payments (test mode). Nothing leaves your browser.
Self-hosted node and CLIWorksRegistry, planner, escrow, funded builds, MCP server. The default rail is simulated, so no real money moves.
JSON API, /docs/api/PartialThe platform endpoints under /api/ back the app. The versioned /api/v1/ API serves items, versions, plans, tokens, webhooks and metadata. Its orders, payouts, earnings, funded-build and ledger operations return 501 not_implemented.
Hosted MCP server, /mcpPartialSearch, planning and publishing tools run through the same pipeline as /api/v1/. The order and funded-build tools exist but answer not_implemented. A node has its own MCP server.
Stablecoin and BTC railsPartialThe node builds payment links and can check a USDC or USDT transfer. It does not send payouts. Treat it as test mode.
Escrow contractNot deployedSpecified in docs/PAYMENTS.md, with its interface in the repository. Unaudited.

Guides

Last updated: