The terms, in plain words.
These terms cover the open-source Carthagent harness, this website, and Carthagent Cloud, the optional hosted model service. By installing the harness, using the site, or creating a Cloud account you agree to them.
Parties.
Carthagent is operated by an individual developer (“we”, “us”). “You” are the person installing the harness or holding a Cloud account. Cloud accounts are for one person; team or shared accounts are not offered and you may not share your sign-in link, session, or devices with others. Contact for anything in these terms: [email protected].
You must be at least 16 and able to form a binding contract. If you use Cloud on behalf of an employer, you confirm you are allowed to send that employer's code to a third-party model provider.
The harness.
The Carthagent command-line tool is open source under the MIT License. That licence, not these terms, governs your use of the code. It is provided as is, with no warranty, and these terms do not narrow it.
The harness writes and runs checks and edits files in your project under your supervision. You are responsible for reviewing what it does, for the repositories and providers you connect it to, and for the costs charged by any provider you connect with your own API key. It is not a sandbox and does not guarantee the correctness or security of code it produces. “Verified” means the harness's own required checks passed at that moment; it is not a promise about the code.
Carthagent Cloud.
Cloud forwards model requests from the harness to upstream model providers and meters them against your plan. It is optional: connecting your own provider is always available and is not degraded to steer you towards Cloud.
You get a Cloud account by signing in with a one-time email link or with Google on api.carthagent.xyz. You are responsible for the security of that email account and for devices you authorise with a ctg login code; you can revoke any device from your account page. Tell us promptly if you believe your account has been used without your permission.
The model catalogue, the allowances, the request limits, and which upstream provider serves a model can change. We will not reduce a paid plan's allowance in the middle of a billing period you have already paid for.
Billing.
- Plans are monthly subscriptions billed in advance through Stripe. Current prices and allowances are on the Cloud page; the request counts shown there are estimates, not guarantees.
- $1 first month on Builder. New customers pay $1 for the first month of Builder, then $10 per month unless you cancel. Pro is $25 per month and Max is $50 per month from the first month. The Builder offer is available once per customer. It is not a credit, a free tier, or a refundable fee.
- Allowances. Each plan has a monthly usage allowance and a daily ceiling. When either is reached, hosted requests are declined until it resets; you can keep working by connecting your own provider. Unused allowance does not roll over. Existing paid card subscriptions at this policy’s rollout retain their full new-plan allowance on confirmed plan changes until a separately notified transition, with at least 14 days’ email notice. Your plan-change review identifies this grandfathered policy when it applies.
- Changing plans. Review and confirm Stripe’s prorated price before switching. Your renewal date stays the same, and the new monthly price applies at renewal. Any amount due is collected immediately. Existing usage and reservations carry forward. Only paid incremental usage is added, capped by the prorated allowance difference, the net amount actually paid at the new plan’s usage rate, and the new plan’s full allowance. Downgrades and zero-paid changes do not add usage. The confirmed plan’s daily ceiling applies. Pending payments keep the existing paid usage limits. Introductory discounts do not apply to Pro or Max.
- Cancellation is self-service through the Stripe customer portal on your account page and takes effect at the end of the paid period. We do not refund partial periods, except where the law requires it or where we failed to provide the service.
- Failed payments pause hosted requests until payment succeeds.
- Tax is added where we are required to collect it. Prices are in US dollars.
Voyages beta and coins.
Voyages is an optional beta using your Carthagent sign-in. No Cloud subscription is required. Each player receives a one-time grant of 50 starting coins. Coins are virtual customization units, separate from Cloud credit: they cannot be bought for money, transferred, cashed out, or used for hosted model requests. Trading is not part of this beta. Personal quests are your own work log, not verified coding evidence or a way to earn coins, XP, distance or badges. Account-anniversary badges record account age, not coding achievement.
A compatible terminal client can explicitly claim 25 coins, 100 XP and 1 km for an eligible required-check verified delivery, up to three per account per UTC day. This uses local harness attestation; the server does not rerun your repository or independently establish authorship or correctness. Blocked, advisory and stale handoffs are ineligible. A delivery or the same project snapshot cannot earn twice. Do not fabricate receipts or change identities to bypass these limits. Future reward policies may change; existing receipts preserve awarded amounts and duplicate protection. Daily-quest assessment alone remains unrewarded.
Separate daily-quest assessment is a default-off backend preparation dated October 26, 2026, not a claim of an available website or terminal flow. If enabled, three curated quests rotate each UTC day. You may explicitly consent to send selected evidence for a quest to the external JEV classifier. Submit only material you have the right to share, after reviewing and removing sensitive content; automatic secret redaction is not promised. This consent applies to that submission, not your whole project or future submissions.
Daily completion is classifier-assessed, not independently verified code, authorship, test execution or a guarantee of correctness. Rubric scores are not calibrated confidence or productivity ratings. Ambiguous evidence may need clarification, and provider failures may leave a submission failed rather than complete. Daily assessments grant no coins, XP, distance, equipment or badges. Do not fabricate evidence or change identifiers to bypass submission or duplicate-outcome limits. Selected evidence is retained briefly for processing and metadata for 90 days, subject to the backup and provider limits in the Privacy Policy.
Review the server-quoted coin price before confirming a purchase. A completed purchase grants an item to your account; ending a listing or discount does not expire an owned item. You can re-equip owned items without paying again. Contact support about incorrect balances or missing items; this beta has no self-service refund control. Coin prices and sale availability may change for future purchases. The beta is early software; report problems rather than trying to exploit retries or duplicate grants.
Crews share your character name, handle, ship name, appearance and role with their current members after you accept an invitation or create a crew. They do not share Cloud billing, model access or repository permissions. Owners and admins may manage invitations and remove members; only an owner may transfer ownership or delete a crew. Do not impersonate others, harass members or use invitations to spam. Blocking stops direct invitations, not existing shared membership. You can leave a crew; an owner must transfer ownership or delete it first. Contact support to report abuse. The Privacy Policy describes the records we keep.
Acceptable use.
Do not use Cloud or the website to:
- break the law, or help someone else to;
- try to get around rate limits, allowances, the one-time offer, or another person's account;
- probe, overload, or interfere with the service or the upstream providers;
- send content that you do not have the right to send, including other people's personal data or confidential code you are not authorised to share;
- resell Cloud access or wrap it as a service for others.
Upstream providers have their own usage policies, and requests that they refuse will fail. We may suspend an account that we reasonably believe is in breach, and will tell you why unless the law prevents it.
Your content.
You own your code, prompts, and the model output you receive through Cloud. We claim no rights in them. You give us only the permission needed to forward your requests to an upstream provider and return the result. The Cloud gateway does not store prompt or response bodies. Separately, a daily-quest submission gives us permission to hold and forward your selected evidence to the external classifier and retain its assessment metadata for the periods in the Privacy Policy; it does not transfer ownership of your evidence.
Model output can be wrong, insecure, or similar to someone else's work. You are responsible for checking it before you rely on it or publish it.
No warranty.
Cloud and the website are provided “as is” and “as available”. We do not promise that they will be uninterrupted, error-free, or fit for a particular purpose, that any model will remain available, or that output will be accurate. To the extent the law allows, we exclude all implied warranties. This is a small, early service run by one person; please weigh that when deciding what to depend on it for.
Liability.
To the extent the law allows, we are not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, data, or goodwill, arising from your use of the harness, the website, or Cloud. Our total liability for any claim relating to Cloud is limited to the amount you paid us in the three months before the claim arose. Nothing in these terms limits liability that cannot be limited by law, including for fraud, or your statutory rights as a consumer where you live.
Termination.
You can stop using the harness at any time and can ask us to delete your Cloud account by emailing [email protected]; cancel any subscription first so you are not billed again. We may suspend or close accounts for breach of these terms, for non-payment, or if we discontinue Cloud, in which case we will give paying customers at least 30 days' notice and refund any prepaid period we cannot deliver. Sections on your content, warranty, liability, and law survive termination.
Law and changes.
These terms are governed by the laws of the State of Delaware, USA, without regard to its conflict-of-laws rules, and disputes will be brought in the state or federal courts located in Delaware. If you are a consumer in a jurisdiction whose law gives you the right to sue at home or protections that cannot be waived, those rights are unaffected.
If a part of these terms is found unenforceable, the rest still applies. These terms, the MIT License for the harness, and the Privacy Policy are the whole agreement between us.
We may change these terms. We will update the date at the top and keep earlier versions in the public repository's history. For changes that materially affect paying customers we will email you at least 14 days before they take effect; continuing to use Cloud after that date means you accept them.
See also the Privacy Policy.
← Carthagent