Creator Agreement
The agreement for publishing packs on Modpack: what you own, the license you give us, your price and share, how you get paid, and the rules that keep people safe.
The short version
- You own your packs. Modpack hosts and runs them for the people you share them with, under a royalty license.
- You set the price, $0 to $5 a run that works, and keep 80% of it (90% for founding creators, for 24 months).
- Earnings are pending for 30 days, then paid monthly on the 15th from $25. They’re never forfeited.
- You never see the people who run your pack or their inputs and results; only totals across 5 or more people.
- No income claims in listings, and no charging people outside Modpack.
- You handle your income taxes; Modpack handles sales tax and sends you a 1099-MISC.
About this agreement
This agreement is between you and Modpack, Inc. (“Modpack”, “we”, “us”) and covers publishing packs on Modpack. It adds to the Terms, which apply to creators too. Where the two differ on a creator topic, such as price, earnings or licenses, this agreement wins.
Its key terms, exactly as shown on the creator setup page:
Creator Agreement v1: you own your packs; Modpack hosts and runs them for the people you share them with, under a royalty license. You set the price, $0 to $5 a run that works, and keep 80% (founding creators 90% for 24 months). Earnings are pending for 30 days, paid monthly on the 15th from $25, and never forfeited. Stripe checks your identity and tax ID once, before the first payout. No income claims in listings and no charging people outside Modpack. You handle your income taxes; Modpack handles sales tax.
You accept it once, on the creator setup page, with this sentence under the button:
By continuing you confirm you’re 18 or older and live in the US, and agree to the Creator Agreement, Terms and Privacy Policy.
That click records your acceptance of Creator Agreement v1 as its own versioned record. Only you can accept it: Claude Code opens the page, but it can’t sign you in or accept an agreement for you.
Who can be a creator
US residents, 18 or older
Creators must live in the United States and be 18 or older, like everyone on Modpack. We screen creators against US sanctions lists before paying anyone.
One creator account per person
Your creator account is your handle, such as modpack.md/yourname. You can change the handle once in the first 30 days. Handles can’t impersonate a person, brand or Modpack, and some names are reserved.
Your sign-in
Keep your sign-in secure. Some steps need your passkey or a fresh sign-in, because they change what other people get: sharing a pack for the first time, or changing its license, visibility or update authority.
Your packs, and the license you give Modpack
You own your packs
You keep ownership of your packs: their code, instructions, checks, examples and listing. Nothing here transfers ownership to Modpack.
The royalty license
You give Modpack a non-exclusive, royalty-bearing license to host, store, copy, build, run, test, check, display and distribute your packs, and to sell runs of them, to the people you share them with. The royalty is your share of your price (section 08). The license covers each version while it’s available on Modpack.
Modpack sells every run
People buy runs from Modpack, not from you, and Modpack pays you a royalty. You aren’t a seller on a marketplace, and Modpack doesn’t hold money for you as an agent.
An open license for shared packs
A pack you share uses an allowed open license: Apache-2.0 by default, or MIT, BSD-2-Clause, BSD-3-Clause, ISC, 0BSD or CC0, and CC BY 4.0 for text-only packs. Copyleft, non-commercial, no-derivatives and source-available licenses (such as GPL, AGPL, LGPL, MPL, CC BY-SA, BSL and SSPL) aren’t accepted.
People who add your pack
People who add your pack can export the version they use, under its license, and keep their results. A version already released can’t be recalled from people who have it.
Your promises about content
You have the rights to everything in your pack, its declared license is accurate, and it keeps third-party notices. It contains no secrets, no one else’s confidential material, and nothing a client or employer hasn’t allowed you to share.
Our listing and discovery
We can show your pack’s name, description, price, evidence and your handle on Modpack, in search, in the Markdown and llms.txt pages AI assistants read, and when we tell people about Modpack.
Network improvements and update authority
When your pack fails or struggles in real runs, the Modpack network can repair it: it proposes a change, tests it against the same checks as your versions, and releases it as a labeled network version. Your update authority decides which of those changes go out without asking you.
Choosing it
You choose update authority when you first share a pack, and can change it later with your passkey. “Creator only” makes every network change wait for you.
Network Revisions License
You give Modpack a perpetual, sublicensable license to make, release and distribute network versions of your pack. Every network version keeps your notices and credit, is labeled “modified by the Modpack network”, and comes with a changelog. As far as the law allows, you waive moral rights that would block these changes.
Your new versions
When you publish a new version, it goes out first, and network fixes are re-applied on top of it only after they pass the checks again.
Who is responsible
Modpack is responsible for the changes its network makes. You’re responsible for your own content.
Your price applies
Your price and share apply to every version of your pack, including network versions.
Publishing, automated checks and listing rules
Your agent does the work
Your agent, such as Claude Code, can package your setup, draft the listing, publish new versions under unchanged terms and set your price. Only you can accept this agreement, confirm a pack’s first share, change its license, visibility or update authority, retire it, set up payouts or sign a counter-notice.
Automated checks on every version
Every version goes through nine automated checks before anyone else can run it: clean rebuild and replay, secrets, malware and dependencies, size and structure, where it connects, resource use, instruction safety, a trial run by a test agent, and license. Most versions pass in about 2 minutes. Modpack pays for the checks.
Pass, hold or block
A blocked version doesn’t go out, and your agent gets the exact file, line or destination with a suggested fix. A held version keeps working privately for you: a second automated review runs, your agent can fix or declare the behavior, and if it’s still unresolved a person decides, usually within 24 hours.
Declared actions
If your pack asks the person’s agent to do something, such as run the project’s own tests, you declare it. Declared actions are shown on the pack page and checked against the declaration.
An accurate listing
Describe what the pack does, what it’s for and not for, and its limits, accurately. Evidence labels and success rates are computed by Modpack from real runs; you can’t edit them.
Pack text
Pack text can give the person tips, never orders to their AI: no instructions to visit sites and obey what they say, run commands, call other tools or connectors, or ignore earlier instructions; no hidden or encoded text; no promotion aimed at the AI.
Packs that visit sites
Use an honest user agent, respect robots.txt, keep to rate limits, and stop on a login wall, 401, 403, 429 or CAPTCHA. No CAPTCHA solving and no proxies to get around blocks. A full crawl needs the person to verify the domain. Reports never claim that a site complies with a law or standard.
Your own costs
New creators get a one-time $25 promotional authoring credit for builds and test runs. After that, builds, test runs and your own runs of your packs are charged at the rate card, with no creator price and no royalty on your own runs.
Trust levels
Instead of caps, signals pause new adds of a version: a report, a failed re-check, a spike in failures, or unusual network use or spending. Popular packs are re-checked at 100, 1,000 and 10,000 people, and people review a random sample of new versions.
The people who run your packs
You never see their data
You never see the identity, inputs, results or files of the people who run your pack, through diagnostics or any other way.
What you do see
Totals across 5 or more people: runs, how often runs worked, and failure types, with dates rounded to the week. Below 5 people you see “not enough data yet”. Questions asked on your pack page, without names. You never learn who reported your pack.
Don’t try
Don’t try to identify people, re-identify anyone from de-identified data, collect their data through your pack, or contact them outside Modpack about their runs. Packs reach only the hosts they declare, and every connection is logged.
No charging outside Modpack
Don’t ask people to pay you outside Modpack for runs of your pack, and don’t move them off Modpack to avoid its price.
Your price and your share
Your price
$0 to $5 per run that worked, per pack or per entrypoint, set by you in the Studio or by your agent. $0 means free. People pay usage at the rate card plus your price, and see both before a run starts; your price is its own line on every receipt.
Charged only when it works
Your price is charged only on runs that worked. A run that doesn’t work, or that the person stops, isn’t charged your price and earns you nothing.
Changing it
Decreases apply right away. Increases apply 14 days after notice, at most once every 30 days. Runs already set aside keep their price, and people with auto top-up are told before a new price applies.
Your share
You keep 80% of your price. Founding creators keep 90% for 24 months from when they set up their creator account, then 80%. Modpack keeps the rest of your price, and the usage margin, to run the service.
An example
At a price of $0.50, the person pays usage plus $0.50. You earn $0.40, or $0.45 as a founding creator. Modpack keeps $0.10, or $0.05.
Earnings and payouts
Pending, then available
Each run that worked adds your share to pending earnings. They become available after 30 days, which covers refunds and fraud checks.
Runs paid with free credit
Runs paid with starter or other promotional credit still earn, but those earnings become available only once that person’s paid credit has cleared: 60 days after a paid top-up with no refund or chargeback, and never more than the cleared amount.
Payouts
Monthly on the 15th, when $25 or more is available, plus a December payout from $5. Paid to your bank through Stripe Connect Express. Stripe’s payout fees, today $2 for each month you’re paid plus 0.25% + $0.25 per payout, come out of the payout.
Identity and tax ID first
Stripe checks your identity and tax ID once, before the first payout. Until then, earnings keep adding up.
Refunds and chargebacks
Refunds and chargebacks on runs you earned from come out of your future earnings for 180 days. Your balance never goes negative, and we never chase you for a debt.
Never forfeited
Earnings are never forfeited and carry no fees for being unpaid. If we can’t pay you, we contact you, and after the dormancy period the law sets (5 years in Florida) we report them as unclaimed property.
Statements
The Studio shows pending, available and paid earnings, each payout, and any refund taken from earnings.
Projections
An earnings projection answers “if I set this price, what would I earn at this many runs?”. It starts empty, uses only the numbers you enter, and is net of payout fees and before income tax. It’s labeled “Hypothetical, based on the numbers you entered. Not a prediction or a promise.” Typical results appear only after 90 days and 20 or more priced packs, as medians.
Taxes
Income tax is yours
You handle your own income taxes on what you earn.
1099-MISC
We report royalties of $10 or more in a year on Form 1099-MISC (box 2), filed and delivered electronically through Stripe. Corporations are generally exempt.
Sales tax is ours
Modpack collects and pays sales tax where it applies. Your price is part of Modpack’s sale, so you don’t register or collect sales tax for runs of your pack.
Promotion, earnings claims and disclosures
No income claims
Don’t make claims about what anyone can earn from Modpack in listings, pack pages or outreach, and don’t invent example creators or results. Modpack doesn’t make earnings claims either.
Disclose what you get
When you post about Modpack or your pack, say so in the post itself if you get anything from us: credit, a better share, early access, featuring or referral rewards. With a referral link, say “I earn Modpack credits if you join via my link”.
Reviews and questions
Never buy, reward or fake reviews, questions or reports, and never tie a perk to someone saying something positive.
If a post needs fixing
We may ask you to fix a post that breaks these rules. Perks we give never depend on positive things you say about Modpack.
Reports, takedowns and appeals
When a version is paused
One report pauses new adds of that version while it’s re-checked. Two independent reports or a failed re-check pause it for everyone and move people back to the last good version, which keeps running and earning as usual. Your agent gets the exact line to fix, and the fixed version goes out after checks.
Appeals
Appeal a pause, hold, takedown or trust change from the Studio. A person who didn’t make the first decision reviews it, usually within 24 hours. Your fix can go out meanwhile.
Copyright notices
We act on valid copyright notices within 48 hours by disabling the material, and send you the notice. People who added the pack keep their past results; new runs pause. The fastest way back is usually to remove the material and republish.
Counter-notices
If you wrote it, you can send a counter-notice from the Studio. It’s a sworn statement, so only you can sign it. We forward it the same day, and the pack comes back in 10 to 14 business days unless the sender tells us they’ve gone to court.
Repeat infringers and removed slugs
We close the creator accounts of repeat infringers, by default after three upheld notices within 12 months. A pack’s address stays reserved after a takedown, so nobody else can take it.
Claiming a “Built by Modpack” pack
Some packs are built by Modpack from open-source projects and labeled “Built by Modpack on {project} ({license})”. A maintainer of one of those projects can claim the pack. Claiming it means accepting this agreement.
Who can claim
An admin of an upstream repository the pack is built on. You prove it by signing in with GitHub (write access isn’t enough; we don’t keep the token) or by committing a .modpack/claim file to the default branch.
What you get
The pack’s dashboards, as totals across people; a veto on its listing, meaning you can edit its title, description and limits or ask us to remove it, and we act within 7 days; and the creator share of any price you set.
What stays the same
Your repository, its license and its notices don’t change. Modpack keeps the pack working, carries upstream notices, credits the project on the page and on every receipt, and sends fixes upstream.
Disputes
If another admin already claimed it, ask them to add you. If a claim is wrong, a person reviews it within 7 days.
Retiring packs, leaving, and what people keep
Delist
Delisting takes a pack out of Browse and search. People who added it keep it.
Retire
Retiring a pack gives the people who added it 30 days’ notice, and then it stops running. You can point them to a replacement and undo it until the date. Their results, files and exports stay with them.
Leaving
You can close your creator account anytime. Your packs are retired the same way, with 30 days’ notice to the people who use them. Pending earnings become available on schedule, and we pay what’s available at the next payout, even under $25.
When Modpack ends it
We can suspend sharing, remove packs or close a creator account that breaks this agreement or the Terms, or puts people at risk, with a reason and a way to appeal. Earnings from fraudulent or invalid runs aren’t earned. Everything else you earned is still paid. For any other reason, we give 30 days’ notice.
What continues
The open license and the Network Revisions License for versions already released, people’s rights to what they already have, and our duty to pay your earnings all outlast the agreement.
Warranties, indemnity and liability
Your warranties
[Draft] You promise that you have the rights described in section 03, your pack and listing are accurate, your pack contains no malware or hidden instructions, and you follow the law and this agreement.
Your indemnity
[Draft] You’ll cover claims against Modpack that come from your pack’s content, your listing, or your breach of this agreement, except where the claim comes from a change the Modpack network made.
As is
[Draft] Modpack provides the service, checks, projections and payouts “as is”. Checks reduce risk but don’t guarantee a pack is safe or useful, and we don’t promise any level of runs or earnings.
Limit of liability
[Draft] As far as the law allows, neither side is liable for indirect or consequential damages or lost profits. Our total liability is limited to the greater of what we paid you in the 12 months before the claim, or $100. This never limits our duty to pay earnings you’ve earned.
Changes, law and general terms
Changes
We tell you at least 30 days before a material change, by email and in the Studio, and it applies once you accept it. A change to your share or payout terms never applies to earnings you’ve already made.
Independent
You’re an independent creator, not Modpack’s employee, agent or partner. You don’t pay anything to earn: no paid plan is needed.
Governing law
[Placeholder] Florida law and applicable US federal law, with disputes handled as the Terms set out.
The rest
This agreement and the Terms are the whole agreement about publishing on Modpack. If one part can’t be enforced, the rest still applies. You can’t transfer it; we can transfer it to a company that takes over Modpack, and we’ll tell you.
Contact
Creator questions and legal notices
Privacy
Security issues
Postal address
Modpack, Inc., [postal address to be added]