Terms of Service

ReuseForge is a registry and marketplace for reusable code, skills, harnesses, MCP servers, models, datasets, prompts and templates. This site, the web app at /app/, the API, the MCP endpoint and the planner are together "the Service". "We" and "us" mean the operator of the Service.

The operator is the maintainer of the open-source project at github.com/Longfordjames/Claude-1. No company name or registered address is published yet. We will add the legal entity and its address to this page before paid features launch. You can always reach us as described in section 19.

By creating an account, calling the API or otherwise using the Service, you accept these terms. If you use the Service for an organisation, you confirm you may bind it. If you do not agree, do not use the Service.

The ReuseForge software itself is MIT licensed. These terms cover the hosted Service, not your right to copy and run the software.

The Service is in public beta. It can change, break, lose data or go offline without notice. Do not rely on it for anything you cannot afford to lose.

Test mode. Unless a listing or order says otherwise in plain words, payments are simulated. Once orders are switched on, a deposit, a payout and a refund will be recorded as they would be on a real rail, but no money, token or coin moves. Listings marked DEMO are examples and cannot be bought.

The USDC, USDT and Bitcoin rails are only partly built. The escrow contract (RepoEscrow) has not been independently audited and has not been deployed. Until real rails are switched on and announced on the Pricing and Security pages, do not send real funds to any address you find on or through the Service.

The sections on escrow, fees, refunds and crowdfunded builds describe how the system is designed to work once real money is in play. In test mode they describe a simulation, and nothing in them creates a right to real money.

What works today. Accounts, sign-in, listings with versions and files, reviews, discussions, stars, follows, collections, organisations, reporting and moderation work now. Ordering, escrow, payouts and crowdfunded builds are still being built in the hosted service: the order, checkout, earnings and funded-build screens in the app are placeholders, and paid items cannot be bought yet.

You must be at least 18 and able to enter a binding contract where you live. Individuals and organisations may use the Service. AI agents may use it through the API and MCP endpoint, but a person or organisation is always responsible for what its agent does.

You may not use the Service if the law applicable to you or to us forbids it, including sanctions and export controls, or if we have previously suspended or removed your account for breaking these terms.

Browsing, searching and planning do not need an account. Listing, buying, reviewing, starring and discussing do. You can sign up with an email and password or sign in with GitHub. Give accurate information and keep it current. A verified email is needed to list a paid item. Email delivery is not switched on yet, so we cannot send verification or password-reset links. Until it is, only accounts created with GitHub sign-in (we use the verified primary email that GitHub reports) can have a verified email, and a forgotten password cannot be reset by email. Keep your password and your two-factor recovery codes safe.

You are responsible for everything done with your account, session or API tokens. Keep passwords and tokens secret, turn on two-factor sign-in, and revoke a token you suspect is exposed. Tell us promptly if you think your account has been taken over. Tokens carry scopes such as read, write and orders; give a token only the scope it needs. A token cannot change your password, email or two-factor setting, end your sessions or delete your account.

One person should not run many accounts to get around a limit, a suspension or the review rules. Handles are first come, first served. Some handles are reserved, including any that start with reuseforge. We may reclaim a handle that impersonates someone or is used to deceive.

Organisation accounts have members with roles (owner, admin, write, read). The organisation is the seller of what it lists. Its owners are responsible for who they give access to.

Sellers keep ownership. You keep all rights in what you list. We do not acquire ownership of your code, text or data.

The listing's licence governs use. Every listing states a licence, either an SPDX identifier such as MIT or Apache-2.0, or a stated commercial or proprietary licence. Buying a listing gives the buyer exactly the rights that licence gives and nothing more. A price does not by itself transfer ownership or lift the licence. Buyers must read the licence before using the code. If a listing says UNKNOWN, assume you have no right to use it until the seller says otherwise.

What you promise as a seller. You own what you list or have the right to license it on the terms you state. You have the right to sell it for the price shown. It is described honestly, including what it does, what it does not do, and any known security problem. You will deliver what the listing describes.

Imported listings. If you import a repository from GitHub or another source, you confirm that you are its owner or authorised to list it. Metadata such as stars, licence and description is copied from the source and may be out of date. Do not list someone else's open-source project as a paid product unless its licence lets you.

Licence to us. You give us a worldwide, non-exclusive, royalty-free licence to host, store, copy, display, index and transmit what you submit (listings, files, reviews, discussions, profile) to run the Service, show it to the people you chose to show it to, make backups, and let agents and users retrieve it through the API. The licence ends when you delete the content, except for copies in backups, copies other people already received, and the records described in section 8.5. Deleting a listing marks it removed and hides it from everyone except our administrators; its files and version history stay in our database. Public listings, reviews and profiles can be read by anyone.

Reviews. Reviews must reflect your own experience. You may not review your own listing, trade with yourself to raise ratings, or pay for or offer rewards for reviews. Once orders are live, a review marked verified purchase means the reviewer's order for that item was released.

You may not list, upload, send or promote any of the following:

• Malware and traps. Code that is designed to damage, spy on, extort or take over a system, hidden telemetry, backdoors, or undisclosed network calls. This includes prompts, skills and harnesses that instruct an agent to exfiltrate data, bypass its user's permissions or hide what it does.
• Secrets and personal data. Credentials, API keys, private keys, seed phrases, or other people's personal data without a lawful basis.
• Code you have no right to sell. Infringing or unlicensed code, code taken in breach of its licence (for example removing a required notice or relicensing copyleft code as proprietary), leaked or stolen source, or code under a confidentiality duty.
• Illegal goods and services. Anything unlawful where you or the buyer are, tools whose main purpose is crime, content that sexually exploits children, or content that incites violence.
• Scams. Fake listings, fake reviews, impersonation, misleading claims about quality, test results or what a project will earn.

You also may not: take payment for a listed item outside escrow after meeting the buyer on the Service; attack, probe or overload the Service or other users' accounts; scrape in a way that harms availability; evade rate limits; use the Service to build a competing copy of its private data; or help someone else do any of this.

Security research is welcome and is covered by the policy on the Security page, not by this section.

We are the venue, not the seller. Contracts for the sale of code are between the buyer and the seller. We provide the registry, the planner and, once they are switched on, the order and escrow system and the dispute process. We do not own, inspect or guarantee the listings, and we are not a party to the licence between buyer and seller.

No warranty on third-party code. Listings, quality scores, test pass rates, attestations, fit estimates, risk scores and Pareto plans are signals made from data that sellers, other users and heuristics provide. They help you decide. They do not prove the code is correct, safe, original or fit for your purpose. Run third-party code in a sandbox, read it first and check its licence (see the buyer advice on the Security page).

We do not review listings before they appear. We may remove or hide a listing, block a download or suspend an account at any time under section 13, but we have no duty to monitor, and not removing something does not mean we approve it.

The planner may suggest building a block from an arXiv paper or other public blueprint. Such a build step is an estimate of effort, not an offer from us or from the authors, and the authors are not affiliated with ReuseForge.

The Verified badge. Our staff set a Verified badge on an account by hand. It says something about the account. It is not an audit of any code, it does not mean we have reviewed or endorse any listing, and a verified account can still publish buggy or harmful code.

When a plan or basket includes paid items, the buyer creates an order. The order records the items, their prices, the payment rail, the network fee rate, the arbiter and two deadlines. Those terms are fixed when the order is created.

The buyer deposits the total to the escrow address for the chosen rail. The escrow agent confirms the deposit and the order becomes funded. Money in escrow is not paid to the seller until the order is released.

Each seller marks their own item delivered, with access to it and the content hash of what was delivered. When every item is delivered, the acceptance window starts. The default is 7 days. The delivery deadline, also 7 days by default, starts when the order is funded.

The order is then released or refunded:

• The buyer accepts: the order is released and sellers are paid.
• The buyer says nothing: the order is released when the acceptance window ends. Check what you received within the window. After it closes a dispute is too late.
• An item is still undelivered when the delivery deadline passes: the whole order is refunded to the buyer, with no fee.
• The buyer disputes: see section 10.

The open-source ReuseForge protocol records listings, orders, deliveries and votes as signed events in an append-only log that nodes copy to each other, so that the history is tamper-evident. If you sign events with the ReuseForge command-line tool or run a node, an event that has been copied to another node cannot be edited or erased by any one party, including us. The hosted service at reuseforge.com keeps accounts, listings, reviews and discussions in its own database today and does not publish them to that log. See Trust and verification and What is public in the Privacy Policy.

Escrow protects payment. It does not look inside a delivery, it does not stop a buyer from copying delivered code, and it does not guarantee that code works. Who holds the funds depends on the rail: the escrow contract for USDC and USDT once it is deployed, and the escrow agent (initially us) for Bitcoin, which cannot hold a conditional payment on its own. We will say which applies on the order itself before you pay.

Payment in cryptocurrency is irreversible on the network. You are responsible for sending the right amount, on the right network, to the right address. Network (gas) costs are charged by the network, not by us. We are not liable for funds sent to a wrong address or on a wrong network.

Browsing, searching, planning and listing are free. There is no subscription. A released paid order pays a network fee, by default 1% of each item's price, taken from the seller's payout. The buyer pays the sum of the listed prices and no markup. Each seller's net is rounded down to the cent and the fee is the remainder. Refunds carry no fee. The Pricing page has the table and a worked example.

The fee rate is written into each order and does not change for that order. We may change the default rate for new orders. We will update the Pricing page and this section's effective date before a change takes effect.

Prices are in US dollars. Sellers are responsible for their own taxes on what they earn, and buyers for any tax due on what they buy. In test mode no real sale takes place. We will document how sales tax and VAT are handled before real payments start.

A buyer who finds that a delivery is not as listed can dispute the order while it is funded or delivered and before the acceptance window ends. State what you ran, what you expected and what failed, in up to 2,000 characters. The order freezes.

The arbiter reads the dispute and decides whether to release the payment to the sellers or refund it to the buyer. Unless an order names another arbiter, the operator of the Service is the arbiter. In the current system a decision is all or nothing for the whole order. Where the payment rail supports it, we may offer a split decision; the order will say so.

The arbiter decides in good faith on the evidence in front of them: the listing, the delivery, the content hash, the dispute text and any reply. Decisions are final within the Service. They do not remove rights you have against the other party under the law or the licence. There is no appeal or deadline for the arbiter yet; this is a known gap and we will describe any process we add here.

Outside an order dispute, refunds are a matter between buyer and seller. Free items and build steps never enter escrow, so there is nothing to refund.

Please try to settle things with the other party first, using the discussion thread on the listing. We may close a dispute that is abusive or repeated without basis.

A proposer can open a project: a goal, deliverables, named developers and milestones. Backers pledge toward the goal. A pledge counts after the escrow agent confirms the deposit. If the goal is reached before the deadline, the project is funded, developers deliver milestones with evidence, and backers vote on whether to release each one. If the goal is missed, backers are refunded.

Backers and developers receive revenue units. Developers may hold at most 50% of the units. When the finished block is later sold, the network fee comes off first and the rest is split across current unit holders in proportion to their units. Units can be transferred between identities where the Service allows it.

This is not investment advice. We do not recommend any project, promise any return or promise that a project will be finished or will sell. You can lose everything you pledge. Revenue units that people can trade may be regulated as securities or similar instruments where you or the proposer live. Proposers and backers are each responsible for following the law that applies to them. Do not promote a project to the public as an investment. We may refuse, hide or stop a project, and we make no representation that the feature is lawful in any particular country.

Crowdfunded builds run only on the simulated rail today. Nothing in this section applies to real funds until we announce that real funds are supported. KYC and AML checks are not performed in the beta.

Anyone with an account can report a listing, account, review, discussion or comment in the app. The reasons you can choose are spam, malware, licence, scam, abuse and other. An administrator can dismiss the report, remove the listing or suspend the account. We tell the reporter what was decided, with a short note, and we tell the owner of a removed listing, with a reason.

Copyright and licence notices. If you believe a listing infringes your copyright or breaks the licence of your code, send us a notice that includes: (a) your name and contact details; (b) a description of the work; (c) the URL of the material on the Service; (d) a statement that you have a good-faith belief the use is not authorised by the owner, its agent or the law; (e) a statement that the notice is accurate and, under penalty of perjury, that you are the owner or authorised to act for the owner; and (f) your physical or electronic signature. Send it as described in section 19, using a private channel.

We will review a complete notice promptly. We may remove or disable the material and tell the seller. A seller who believes the removal was a mistake can send a counter-notice with their contact details, the URL of the removed material, a statement under penalty of perjury that they believe it was removed by mistake, and consent to the jurisdiction needed to resolve the dispute. Where the law provides for it, we restore the material after a reasonable period unless the complainant tells us they have started legal action. We may share a notice and counter-notice with the other party.

We have not yet registered a designated agent with the US Copyright Office. We will list it here when we do. Notices sent as described above are still handled. Sending a knowingly false notice can make you liable for damages. We end the accounts of repeat infringers.

You can stop using the Service at any time. Export your data first under Settings, Your data, then delete your account under Settings, Account. You cannot delete it while you are the only owner of an organisation. Deleting an account signs you out everywhere, revokes your API tokens, archives your listings, and erases your email address, password hash, two-factor data, profile text, avatar, linked GitHub sign-in, notifications, follows and organisation memberships. Your handle stays reserved so nobody can pose as you. Some things stay, for example the security log, your reviews, discussions and comments, and the files of archived listings: the Privacy Policy lists exactly what. Orders in progress still complete or refund under their terms once orders are live.

We may remove content, suspend or end an account, or limit API access if you break these terms, put users or the Service at risk, or if the law requires it. A suspension signs the account out, revokes its API tokens and hides its listings. A person who tries to sign in to a suspended account is told to contact us. We tell you why when we can do so safely. There is no formal appeals process yet. To ask us to look again, open an issue as described in section 19; we will read it, but we cannot promise a particular result or a reply time. We may act immediately on malware or fraud. Once orders are live, orders in escrow are not paid out to a suspended seller until we have looked at them.

We may stop providing the Service or a part of it. If we shut down, we will give notice where we reasonably can, finish or refund funded orders, and give you a way to export your data.

Sections that by their nature continue after the end of your use (ownership, licences already granted, disclaimers, liability, disputes, governing law) continue.

The Service is provided as is and as available. To the fullest extent the law allows, we give no warranty of any kind, express or implied, including merchantability, fitness for a purpose, non-infringement, uninterrupted service, accuracy of scores or plans, or that any listing is safe or lawful. We do not warrant that the escrow system, the payment rails or any smart contract is free of defects. They are in beta, and the contract is unaudited.

Nothing here is legal, tax, financial or investment advice. Some consumer laws give you rights that cannot be waived. These terms do not take those away.

To the fullest extent the law allows, we are not liable for indirect, incidental, special, consequential or exemplary damages, or for lost profits, revenue, data, goodwill or crypto-assets, arising from your use of the Service or from third-party code, sellers, buyers, other users, networks or wallets.

Our total liability for any claim relating to the Service is limited to the greater of (a) the fees we received from you in the 12 months before the claim and (b) US$100. In test mode we receive no fees, so the second figure applies.

Nothing limits liability that cannot be limited by law, such as liability for fraud, wilful misconduct, death or personal injury caused by negligence.

If a third party brings a claim against us because of what you listed or did on the Service, in breach of these terms or the law, you will cover our reasonable costs of dealing with it, to the extent the law allows. We will tell you about the claim and let you help respond to it.

We will change these terms as the product moves out of beta, especially when real payments start. We will change the effective date at the top and tell you where we can (in the app, on the site, or by email once email delivery is on). For a material change we will give at least 14 days' notice before it applies to you, except where a change is needed sooner for security or legal reasons. If you keep using the Service after the date, you accept the new terms. If you do not accept them, stop using the Service and delete your account. Orders already funded keep the terms they were made under.

To be specified before payments go live. The governing law and the forum for disputes between you and us have not been fixed during the beta. We will set the final jurisdiction clause here, and announce it as described in section 17, before any paid feature handles real money. Until then, nothing in these terms limits any mandatory consumer rights you have under the law where you live.

Before starting any formal proceeding, please contact us and give us 30 days to try to resolve the issue.

We are a small team and we use GitHub as our front door.

• General questions, bugs and terms feedback: open an issue in the project repository.
• Moderation decisions you want us to look at again: open an issue that says only "moderation review" and your handle, with no other details.
• Security vulnerabilities: report privately through a GitHub security advisory, as described on the Security page.
• Copyright notices and anything that includes personal details: do not post these in a public issue. Open an issue that says only "legal notice" or "privacy request" with no details, and we will move to a private channel with you. If you cannot use GitHub, a security advisory also reaches us privately; mark it "not a vulnerability".

A dedicated legal and privacy email address will be added here when it exists.