megaloop — Terms of Service

Effective date: 2026-08-10 Last updated: 2026-08-10

These terms are an agreement between you and AI PWRD Inc., a Delaware corporation ("megaloop", "we", "us"), covering your use of the megaloop service at megaloop.dev, its dashboard, its API, and its MCP server.

By creating an account or sending a request through megaloop, you agree to these terms. If you do not agree, do not use the service.

Two other documents go with this one and form part of the agreement:

• Acceptable Use Policy (/acceptable-use) — what you may and may not do with the service.
• Privacy Policy (/privacy) — what we store, what we send to third parties, and what you can delete. The technical disclosure page at /trust says the same things with the source files named beside each claim.

1. What megaloop does

You already pay a flat monthly fee for one or more AI subscriptions. megaloop lets you link those subscriptions and use them as a single API endpoint, with requests spread across the accounts you linked.

Concretely, the service:

• holds the credentials for the provider accounts you link, encrypted;
• gives you one base URL and one API key;
• picks one of your linked accounts for each request and forwards the request to that provider;
• moves to another of your accounts when one hits its rate limit;
• shows you which of your accounts served what, and which are running out of headroom.

That is the whole of it. megaloop is a router that uses your accounts. It is not an AI model, not an inference provider, and not a reseller of anyone's capacity.

Forwarding is not byte-for-byte. Headers are added and replaced on the way out, and on one provider's path a fixed line is prepended to your system prompt — your own prompt kept in full after it, nothing you wrote removed. The Privacy Policy sets out every one of those changes and is the authoritative list; the Acceptable Use Policy states them again under rule 3, because they are done on your account and you agree to that rule. Read them before you link a subscription.

2. Who runs this, and what stage it is at

megaloop is early software run by a very small operation — at the time of writing, one person.

Being direct about what that means for you:

• There is no support team and no on-call rotation. Messages get answered when a human is awake.
• There is no uptime commitment (section 10) and no third-party security audit of anything here.
• Features change, break, and occasionally get removed. Interfaces are not frozen.
• Access is currently closed. If you have an account, it is because we gave you one.

If you need a vendor with an SLA, a support contract, and a compliance package, megaloop is not that vendor today. Buy accordingly.

3. The condition this whole service rests on: you must own the accounts you link

This is the most important clause in this document, and it is the one most likely to cost you something if you ignore it. It is not buried in a schedule for that reason.

You may only link provider accounts that you own and are entitled to use. Not an employer's account you happen to have credentials for, not a friend's, not a shared account, not one you bought access to from someone else.

You are responsible for complying with each provider's own terms. When you link an account, you are pointing megaloop at a relationship between you and that provider. That relationship is governed by their agreement with you, not by ours.

You should understand and accept the following before you link anything:

• Provider terms vary, and some restrict what megaloop does. Routing a subscription plan through third-party software, using a subscription as an API, sharing account access, and automated use are all things a provider may limit or prohibit. Some do. Read the terms of every account you link, and re-read them when they change.
• We do not control those terms and cannot interpret them for you. We are not your lawyer and nothing on our site, in our docs, or in a support reply is advice about whether your use is permitted by your provider.
• The risk of a provider suspending, rate-limiting, or terminating your account is yours. A linked account is worth real money to you and can be lost. We take custody and token handling seriously, but we cannot promise a provider will not act against your account, and we are not liable if one does (section 16).
• We are not affiliated with, endorsed by, or sponsored by any provider. Provider names appear in our product only to tell you which of your own accounts is which.
• If a provider tells us to stop serving your traffic, we will. See section 13.

If you cannot honestly say the accounts you are about to link are yours to use this way, stop here.

4. Your megaloop account

• You must be at least 18 and able to enter a contract. Eighteen is the minimum age for a megaloop account, it is the same floor the Privacy Policy states, and there is no younger tier — we do not knowingly keep an account for anyone under it. If you are signing up for a company, you must have authority to bind it, and "you" means that company.
• Sign-in is a code emailed to the address you registered. There is no password. Keep access to that mailbox secure — anyone who can read it can sign in as you.
• You are responsible for everything done with your API keys. Treat a megaloop key like the provider credentials it fronts. If a key leaks, revoke it in the dashboard. Revoking blocks the key from the management API at once, but the inference gateway authenticates against a short-lived in-memory cache, so a revoked key can still be accepted for inference for up to 60 seconds after you revoke it. Section 14 says the same thing; it is a real window and we would rather you plan around it than discover it.
• Tell us promptly at support@megaloop.dev if you think someone else has access to your account.
• One account per person or organisation. Do not create accounts to work around plan limits.

5. Acceptable use

The Acceptable Use Policy (/acceptable-use) is part of these terms and governs what you may do with the service. In summary, and without limiting what that document says: link only accounts you own, do not resell or share access to megaloop or to the accounts behind it, do not use megaloop to do anything a provider's terms forbid, and do not use it for anything illegal.

Breaking the AUP is grounds for suspension or termination under section 13.

6. We resell no inference and hold no credits

Every request you send runs on capacity you already pay for. megaloop holds no API credits of its own and never substitutes another source of inference for yours. This is a structural fact about how the service is built, not a marketing position, and it has consequences you should hold us to and plan around:

• What you pay us buys the software, not tokens. The subscription fee in section 7 is for access to megaloop. It is not a payment for inference and it does not include any.
• What you pay your providers is separate. We do not bill it, collect it, refund it, or have any visibility into it beyond what your linked accounts report back to us.
• When your own capacity runs out, requests fail. If every linked account is rate-limited, suspended, or out of quota, megaloop returns an error. It will never quietly serve you from some other pool, because there is no other pool.

7. Plans, prices, and the trial

Trial. Every new account starts on a 14-day full-feature trial. No card is required. During the trial you can link an unlimited number of accounts. The trial starts when your account is created and ends 14 days later. When it ends you need a paid plan to keep using the service — that is the term you agree to here.

Stated plainly because it is true today and we are not going to imply otherwise: the gateway does not currently refuse a request from an account whose trial has ended. Entitlement enforcement on the inference path is behind a configuration switch that is off in this deployment, and an expired account can still link up to 5 provider accounts. If you keep using the service after your trial ends without subscribing, you are in breach of this section, and our not having cut you off automatically is not a waiver of it or permission to continue. We may turn enforcement on at any time.

Plans. Two, both monthly:

Both plans are otherwise identical — the difference is the cap on linked accounts, nothing else.

The amount you are actually charged is the one shown on the payment provider's checkout page for the plan you pick, and that is the amount that binds. The figures above describe those prices; they are not themselves the mechanism. They have been checked against the configured prices and agree: $39.00 and $99.00 US, both monthly, both active.

Monthly only. There is no annual term, no prepayment, and no discount. This is deliberate and built into the product rather than being a policy we could quietly bend.

Prices are in US dollars and exclusive of tax. Any VAT, GST, or sales tax owed where you are is yours to bear on top of the price shown. We do not calculate it, add it to your invoice, or collect it on anyone's behalf: automatic tax calculation is not switched on at our payment provider, so the amount charged is the plan price and nothing else. If your own tax authority expects you to account for the tax yourself, that is on you.

Payment. Card details never reach us. Checkout, card updates, plan changes, and cancellation all happen on our payment provider's own hosted pages. We store the customer and subscription identifiers they give us, your plan tier, status, and renewal date — see the Privacy Policy.

Renewal. Subscriptions renew automatically each month at the then-current price until you cancel. Section 17 covers what happens if we change a price.

Changing plan. You can switch between Starter and Pro at any time in the billing portal. The change takes effect immediately and the difference is prorated: you are credited for the unused part of the month on the old plan and charged for the rest of it on the new one. Neither adjustment is billed on the spot — both appear as lines on your next invoice.

Downgrading with more accounts than the plan allows. If you drop from Pro to Starter while holding more than 5 linked accounts, we do not unlink anything. Your existing accounts keep working; you simply cannot link another until you are back under 5.

Failed payments. If a payment fails, your access continues while the payment provider retries. That grace period is not indefinite — if the subscription ends up cancelled, access ends with it.

8. Cancellation

Cancel any time, yourself, in the billing portal. No email, no retention call, no notice period.

Cancelling stops the next renewal. You keep access for the rest of the month you have already paid for, and the subscription ends at the end of that period. The billing portal is configured to cancel at the end of the paid period rather than immediately, and nothing is prorated back to you on the way out. Section 9 covers refunds.

Cancelling does not unlink your provider accounts or delete your data. Section 14 covers what happens to your data, and how to have it deleted.

9. Refunds

Plainly: we do not refund the current month by default. You pay monthly, you can cancel any time, and cancelling ends the next charge rather than reversing the last one.

Two exceptions, which we will honour on request at support@megaloop.dev:

• We broke it. If megaloop was materially unusable for a significant part of a month because of something on our side, ask and we will refund that month. This is a judgement call made by a human, not an automated credit scheme, and it is not an SLA (section 10).
• You were charged after cancelling, or charged twice, or charged on an account you never used. We fix billing mistakes.

If the law where you live gives you a refund or cancellation right that you cannot sign away — a statutory withdrawal or cooling-off period, a consumer guarantee, a mandatory right to a remedy — you keep it in full, and it overrides everything in this section. Nothing here asks you to waive a right your own law does not let you waive. Tell us which right you are relying on and we will apply it.

10. Availability — there is no uptime guarantee

We do not commit to any level of uptime, and there are no service credits. Not a soft target, not an internal goal we would rather not print: there is no SLA at this stage. Anyone telling you otherwise, including any earlier draft of anything, is wrong.

What that means concretely, given how the service actually runs today:

• megaloop runs in a single cloud region, on one application server and one database server. There is no redundancy and no automatic failover. A failure of either takes the service down.
• Deployments restart the service. Maintenance can interrupt requests.
• Under heavy concurrent load we may queue a request briefly and then refuse it with a retry hint, to stop one customer's traffic from degrading another's.
• We depend on your providers. If a provider is down, slow, or has rate-limited your account, your requests fail or slow down, and there is nothing we can do about it.
• We monitor the service, but nobody is paged at 3am.

Use megaloop where an outage costs you time, not where it costs you something you cannot afford to lose. If your workload cannot tolerate the service being unavailable without warning, keep a direct path to your providers as a fallback.

11. Your prompts and the responses

You keep whatever rights you have in what you send through megaloop and what comes back. We claim no licence to any of it beyond what is technically necessary to route the request to your provider and return the response to you.

We do not store your prompts or the responses. We keep one row of metadata per request. The Privacy Policy lists every column of that row and is the authoritative list — this section deliberately does not repeat it, because a partial list here would be read as the whole one. The Privacy Policy also covers what is read out of a response to fill it, the retention position, and every third party in the path; the /trust page names the source file behind each claim.

Two things you should be clear-eyed about:

• The provider serving your request receives the full prompt and the full response. Their retention, their training practices, and their terms apply to that, and they are not ours to control or to promise anything about.
• Our infrastructure providers sit in the path. The Privacy Policy names them. Read it before sending anything through megaloop that you would not send through a hosted service.

You are responsible for having the right to send what you send, and for the consequences of what you do with what comes back.

12. Changes to the service

We will change megaloop. Features get added, reworked, and sometimes removed. We may change which providers are supported, including dropping support for one — usually because that provider changed something on their side.

Where a change would break how you use the service, we will give you as much notice as we practically can, by email. Where a change is forced on us by a provider or by law, we may have to make it immediately and tell you afterwards.

13. Suspension and termination

You can leave at any time. Cancel in the billing portal, unlink your accounts, and stop using the service.

We may suspend or terminate your account if:

• you break the Acceptable Use Policy or section 3 of these terms;
• your payment fails and the subscription is not restored;
• a provider requires us to stop serving your traffic, or terminates the accounts you linked;
• the law requires it;
• your use is causing damage to the service or to other customers.

Where we can, we will tell you first and give you a chance to fix it. Where a provider or the law forces our hand, we may act first and explain afterwards.

We may also shut the service down. This is a very small operation and that is a real possibility, so it is written down rather than left to be discovered. If we wind megaloop down we will give you 30 days' notice by email, stop charging you, and give you that time to unlink your accounts. We will not sell your credentials or your data to anyone as part of any such wind-down.

14. Your data when the agreement ends

Ending your subscription does not by itself delete anything. What you can do, and what is honestly true today:

• Unlink an account in the dashboard. That is a real delete: the row and its encrypted credentials are removed. Revoking megaloop's access at the provider itself is a separate step you take on the provider's site, and you should take it.
• Revoke your API keys in the dashboard. A revoked key stops working on the management API at once. On the inference gateway it can still be accepted for up to 60 seconds afterwards, because the gateway authenticates against a short-lived in-memory cache rather than reading the database on every request. The row stays so an audit can account for every key that existed. Only a hash and the visible prefix were ever stored.
• Ask us to delete everything. Email support@megaloop.dev and a human will do it, within 30 days of your request. There is no self-serve delete-everything button today, and we are not going to pretend otherwise.
• What a full deletion does not currently remove, stated because a policy that overclaims is worse than no policy: some security records — the audit log, and the records of sign-in codes that were issued — contain your email address and are not removed by that deletion today. The Privacy Policy says the same thing in more detail. We consider this a gap, not a design.
• Request metadata is not deleted on a schedule. Nothing prunes it automatically.
• Backups keep a copy for a while longer. A deletion removes the live row immediately, but encrypted database backups taken before it can still contain that row until they age out, which takes up to 14 days. We do not reach into a backup to edit it. The Privacy Policy describes the backup arrangement in full.

15. Disclaimers

The service is provided "as is" and "as available", without warranties of any kind, to the fullest extent the law allows. We do not warrant that megaloop will be uninterrupted, error-free, secure, or fit for any particular purpose.

We specifically do not warrant:

• that any provider will permit, tolerate, or continue to permit your use of megaloop;
• that your provider accounts will not be rate-limited, suspended, or terminated;
• that any given request will be served, or served by any particular account;
• that the outputs you get from a provider are accurate, lawful, or fit for anything.

16. Limitation of liability

To the fullest extent the law allows:

• We are not liable for indirect or consequential loss. That includes lost profits, lost business, lost or corrupted data, wasted engineering time, the cost of a stalled or failed automated run, and the cost of buying inference elsewhere to replace what you could not get through megaloop.
• We are not liable for what a provider does to your account. Including suspension, termination, rate-limiting, credential revocation, and any money you lose as a result. This is the risk you accept in section 3.
• Our total liability is capped at the total amount you paid us in the 12 months before the event that gave rise to the claim. For most customers that is a few hundred dollars. Given the price of this service, that cap is the honest measure of what we can stand behind.

None of that applies to the things that cannot lawfully be excluded. Nothing in these terms excludes or limits our liability for death or personal injury caused by our negligence, for fraud or fraudulent misrepresentation, or for any other liability that the law where you are does not permit us to exclude or limit. Where a limit above runs into one of those, the limit gives way and the rest of this section stands.

17. Changes to these terms

We may update these terms. When we do, we will change the "last updated" date and, for anything that materially affects you, email you before it takes effect.

For a price increase on your plan, we will give you notice before the renewal it applies to, so you can cancel first. A price increase never applies to a month you have already paid for.

Continuing to use the service after a change takes effect means you accept the updated terms. If you do not accept them, cancel.

18. Communications

While you have an account we will email you about the service: sign-in codes, billing, security, and changes to these terms. You cannot opt out of those while your account exists — they are how the service works.

Usage alerts, such as an account approaching its limit, are optional and you can turn them off in the dashboard.

19. General

• Governing law. These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict-of-laws rules. Disputes go to the state and federal courts located in Delaware, and we both submit to their jurisdiction. If you are a consumer, this does not take away any right your local law gives you to bring proceedings in the courts where you live, or to rely on the protections of your own law.
• Indemnity. If a provider or another third party brings a claim against us because of the accounts you linked to megaloop, or because of the way you used it, you will cover our reasonable costs in dealing with that claim. This is limited to that: it does not cover a claim arising from our own breach of these terms, our negligence, or our wilful misconduct, and it does not make you responsible for anything we did.
• Assignment. You may not transfer this agreement without our consent. We may transfer it as part of a sale or reorganisation of the business, on notice to you.
• Severability. If a clause is unenforceable, the rest still stands.
• Entire agreement. These terms, the AUP, and the Privacy Policy are the whole agreement between us about the service, and they replace anything said earlier.
• No waiver. Not enforcing something once does not mean we have given it up.

20. Contact

megaloop is operated by AI PWRD Inc., a Delaware corporation.

Write to support@megaloop.dev for support, refunds, deletion requests, security reports, and any notice you have to give us under these terms. One address is deliberate at this size: more of them would mean some went unread.