Credit only

Capacity contribution agreement — credit only

1. Parties

This agreement is between {{ownerName}} (the "Owner") and {{contributorName}} (the "Contributor"), covering one project: {{projectTitle}}. It takes effect on {{effectiveDate}}.

2. What is being contributed

The Contributor commits {{ccuCommitted}} CCU of Claude Code capacity to the project. One CCU equals one percent of a Claude Pro weekly Claude Code allowance, so the number describes a slice of usage capacity, not a dollar figure or a promised outcome. Alongside that capacity comes the Contributor's actual time and labour: writing code, running sessions, reviewing output, and doing whatever the work requires. What counts as delivered is what the platform's ledger records as spent against this project, not whether any particular feature ships or works.

3. Ownership of the work produced

The Owner keeps everything the Contributor produces using the committed capacity — all code, designs, documentation, and other output. The Contributor gets no equity, no royalty, and no ownership stake in {{projectTitle}}. What the Contributor gets instead is a real, binding credit obligation, spelled out in clause 5, that the Owner has to honour for as long as the project stays public. That's the trade this template describes: full ownership to the Owner, in exchange for credit the Owner can't quietly drop.

4. Intellectual property

The Contributor assigns the Owner all right, title, and interest in anything they create for {{projectTitle}} using the committed capacity — code, prompts, configuration, documentation, and any AI-generated output produced during their sessions. This is a present assignment, effective as work is produced, not a promise to assign later. Where local law won't let moral rights be assigned, the Contributor waives them to the extent waiver is legally possible. If the assignment doesn't take effect in some jurisdiction, the Contributor instead grants the Owner an exclusive, worldwide, perpetual, royalty-free licence to use, modify, and distribute the work, with the right to sublicense it.

Each side keeps ownership of whatever they already had before this agreement. Bringing pre-existing material into the project gives the Owner a licence to use it as part of {{projectTitle}}, but doesn't transfer ownership of it.

5. Credit and attribution

The Owner must list {{creditName}} in {{creditPlaces}} for as long as {{projectTitle}} remains public. This isn't a courtesy the Owner can revisit later — it's a term of this agreement. Credit can be removed only if the Contributor asks for it, or if the Owner has a serious, stated reason: the Contributor's work has been entirely removed from the project, or conduct that would justify removing anyone from any project. Either way, the Owner must give written notice first.

The Contributor may use the work in a portfolio, a talk, a resume, or a case study, including screenshots and a description of the publicly visible parts, and may describe what they built. That right doesn't override clause 6 — anything still confidential stays confidential even in a portfolio piece.

If the Owner sells or transfers {{projectTitle}}, this credit obligation travels with it. The Owner must make continued credit a condition of that sale, not something the new owner can quietly drop.

6. Confidentiality

Both sides may see things that aren't public: private repository contents, credentials, unreleased plans, or internal discussion about the project. Neither side may share that outside the working relationship, except for material that's already public or that they already knew independently before this agreement. The Contributor may describe their own contribution under clause 5, but may not disclose project details still covered by this clause.

7. No warranty

Everything here is provided as-is. Claude Code output can be wrong, incomplete, or insecure, and neither party guarantees that anything produced works correctly, is fit for any purpose, or doesn't infringe someone else's rights. Neither party is liable to the other for indirect, incidental, or consequential losses arising from this agreement or the work done under it.

8. Not a partnership, not employment

The Owner and Contributor are independent parties. Nothing here creates a partnership, joint venture, agency, or employment relationship between them, and neither can bind the other to anything. Each is responsible for their own taxes on anything they receive or earn. UseMyTokens is the platform that hosted this agreement; it is not a party to it and has no obligation to enforce it.

9. Termination

Either party can end this agreement with seven days' written notice, or immediately if both agree. Capacity already spent is not refundable. The assignment in clause 4 and the credit obligation in clause 5 both survive termination. Clauses 4, 5, 6, 7, and 8 survive termination.

10. Governing law

This agreement is governed by the laws of {{governingLaw}}. Before either side takes a dispute anywhere else, they agree to try to resolve it directly between themselves first.

11. Signing

Both parties sign electronically through UseMyTokens by typing their full legal name. The platform stores a SHA-256 hash of this exact agreement text alongside each signature, so either party can later prove exactly what they agreed to.

---

Not legal advice. UseMyTokens produced this document from a template. It is a starting point written to be read, not a substitute for a lawyer. Nobody here has reviewed it against your situation, your jurisdiction or your project. If real money, employment, an existing NDA or someone else's intellectual property is involved, get it looked at before you sign.