Draft — pending legal review
This is a first draft, grounded directly in how the Bagged API and website work today rather than generic template language. It has not been reviewed by a lawyer, and it should not be treated as final or relied upon for anything customer-facing — especially once any paid tier collects real payment — until it has been. Bracketed items like [COMPANY LEGAL NAME] and [JURISDICTION] are deliberate placeholders, not oversights; they need real business/legal input, not a guess.
1. Who this agreement is between
These Terms of Service (“Terms”) govern access to and use of the Bagged API and the bagged.life website (together, the “Service”), operated by [COMPANY LEGAL NAME], a company organized under the laws of [JURISDICTION] (“Bagged,” “we,” “us,” or “our”). By joining the waitlist, receiving or using an API key, or otherwise using the Service, you (“you” or “Customer”) agree to these Terms.
2. What the Service is (and isn’t)
Bagged is a PnL and analytics API for on-chain memecoin trading activity: bonding-curve cost basis, wash-trade filtering, and rug resolution, computed from public on-chain data by a dedicated PnL engine. Coverage varies by chain and changes as we build it out — the status page and docs describe, honestly and without inflating it, which endpoints are backed by live on-chain indexing versus placeholder data at any given time. Check them before building anything that assumes every chain listed on the site is live.
The Service is a data and analytics tool. It is not financial, investment, tax, or legal advice, and nothing it returns is a recommendation to buy, sell, or hold any asset. You are solely responsible for any trading or investment decisions you make.
3. Accuracy — best-effort, not guaranteed
PnL figures returned by the Service are best-effort approximations, not audited financial records.
- Solana wallet history is fetched from our on-chain data provider up to a fixed cap of the 500 most-recent transactions per wallet. A wallet with more history than that will have realized PnL computed only from the transactions inside that window — older activity is not included, which can understate a very active wallet’s true realized PnL.
- Bonding-curve cost basis, wash-trade filtering, and rug resolution are heuristics built to handle memecoin-specific edge cases as accurately as we can, but they are not infallible, and the underlying on-chain data providers can themselves have gaps, delays, or errors.
To the maximum extent permitted by law, we disclaim any warranty of accuracy, completeness, or fitness for a particular purpose regarding PnL data, and disclaim liability for decisions made in reliance on it.
4. Accounts, waitlist signups, and API keys
Using the API requires an API key. Signing up with your email through the waitlist form on bagged.life does not issue one automatically — keys are currently provisioned by hand. Because only a one-way hash of a key is ever stored, we cannot retrieve or redisplay a lost one. Once you have a key, the same rules below apply to it.
You are responsible for keeping your API key confidential and for all activity that occurs under it. If you believe a key has been compromised or you’ve lost it, contact us and we’ll help you get a new one issued — there is no self-serve key recovery today.
5. Acceptable use
You agree not to, and not to permit anyone else to:
- Circumvent, or attempt to circumvent, your tier’s rate limits or usage caps.
- Reverse engineer, resell, or sublicense raw access to the Service without our written permission.
- Send traffic patterns intended to overwhelm, scrape beyond intended use, or otherwise abuse the Service — including its public, unauthenticated endpoints.
- Use the Service for any unlawful purpose, or in a way that violates our on-chain data providers’ own terms of use.
Usage tiers (Free, Builder, Growth, Enterprise) and their current call allowances are described on the pricing page. Rate limits are enforced automatically at the API layer based on your key’s tier.
6. Enforcement
If we determine, in our reasonable judgment, that your use of the Service violates these Terms — including abusive traffic, attempts to bypass rate limits, or fraudulent signups — we may revoke your API key without prior notice. That’s the same mechanism we use for routine key rotation, applied as our enforcement tool. We’ll try to give notice and a chance to fix things first for good-faith mistakes, but we reserve the right to revoke immediately for clear abuse.
7. Fees
Pricing tiers and their current call allowances are described on the pricing page and are subject to change. If and when you subscribe to a paid tier, the applicable fees, billing cycle, and payment method will be as presented to you at signup or in a separate order form. Enterprise pricing is negotiated individually — contact us for that.
8. Service availability
The Service is provided on a best-effort basis. We do not currently offer a formal SLA for the Free, Builder, or Growth tiers; Enterprise customers may negotiate one directly with us. We don’t publish fabricated uptime or latency numbers — the status page gives a plain account of what’s actually running. We may modify, suspend, or discontinue any part of the Service at any time.
9. Intellectual property
We retain all rights in the Service, including its software, APIs, and branding. You retain rights in the data you submit to us (for example, wallet addresses you look up). We grant you a limited, non-exclusive, non-transferable license to access and use the Service in accordance with these Terms and your tier’s usage limits.
10. Termination
You may stop using the Service at any time. We may suspend or terminate your access — including by revoking your API key — for breach of these Terms, non-payment on a paid tier, or if we discontinue the Service. Sections that by their nature should survive termination (accuracy disclaimers, limitation of liability, governing law) will survive.
11. Limitation of liability
To the maximum extent permitted by law, the Service is provided “as is” and “as available,” without warranties of any kind, express or implied. We are not liable for any indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, data, or trading gains, arising from your use of or inability to use the Service, even if advised of the possibility of such damages. Our total liability arising from these Terms or the Service will not exceed the greater of (a) the amount you paid us in the twelve months before the claim, or (b) [LIABILITY CAP].
12. Indemnification
You agree to indemnify and hold us harmless from claims, damages, and expenses arising out of your misuse of the Service or violation of these Terms.
13. Governing law
These Terms are governed by the laws of [JURISDICTION], without regard to conflict-of-law principles. Any dispute will be resolved in the courts located in [JURISDICTION].
14. Changes to these Terms
We may update these Terms as the product changes. If we make material changes, we’ll update the date below and, where practical, notify active API key holders by email. Continued use of the Service after changes take effect means you accept them.
15. Contact
Questions about these Terms? Email business@bagged.life.
Last updated: September 2, 2026 — initial draft, pending legal review.
