Enterprise Terms Addendum

1. Scope and order of precedence

This Addendum supplements StockUp's Terms of Service, Privacy Policy, and API Acceptable Use Policy. A signed Enterprise agreement or order form controls if it conflicts with this Addendum. Marketing pages, plan previews, and demo materials do not create a contractual Enterprise commitment by themselves.

2. Organizations, administrators, and authorized users

The organization named in the Enterprise account is responsible for choosing administrators, managing users and seats, assigning quotas, protecting credentials, and removing access when a person or application is no longer authorized.

Every active Enterprise member must accept the current Enterprise Terms before using the Enterprise Dashboard or Playground. Individual acceptance covers the user's platform and acceptable-use responsibilities. An organization administrator remains responsible for the organization's commercial commitments under its Enterprise agreement.

3. Enterprise API access

Enterprise access may include organization-owned API keys, Enterprise model aliases (including a Quan 3.5 alias), organization resources, and per-user attribution. Requests may require a valid Enterprise API key, an approved Enterprise model, an organization identifier, and an X-Enterprise-User-Id header.

Standard self-serve Developer API keys cannot access Enterprise-only model aliases or organization resources. Existing Enterprise API keys may continue to serve direct API requests even when a member has not accepted a newer Dashboard version.

4. Usage credit, plans, and billing

Enterprise usage is measured in dollars of monthly usage credit, not token pools. Unless the applicable Enterprise agreement or order form says otherwise:

• Each Enterprise plan includes a monthly amount of usage credit. Requests draw on it at StockUp's published Developer API list price for the model used, plus $0.007 for each executed live web search. More expensive models use credit faster than less expensive ones.
• Enterprise plans include access to the current public Quan models and their Enterprise aliases, including Quan 3.5. New models are added at their own published list price.
• Usage credit and included document credits reset each month and do not roll over. Document credits work as described in the Quan credits section of the Terms of Service.
• When usage credit runs out, the organization administrator chooses whether further requests stop until the next period or continue as overage at list price, billed at the end of the month.
• Seats, per-user limits, and usage policies are set by the organization administrator within the plan's limits.

Current starting plans are listed on the Enterprise page and may change:

• Pilot: $199, paid once, for 30 days, with $225 of usage credit, 1,500 document credits, and up to 10 seats. Unused Pilot credit expires at the end of the 30 days. If the organization subscribes to Team during the Pilot, the $199 is credited once toward the first Team month.
• Team: $499 a month, with $600 of monthly usage credit, 3,000 monthly document credits, and up to 50 seats.
• Business: $1,999 a month, with $2,500 of monthly usage credit, 15,000 monthly document credits, and up to 500 seats.
• Custom: from $10,000 a month, with usage credit, document credits, and seats set by contract.

Annual Enterprise contracts are invoiced in advance, payable within 30 days of the invoice date (net-30), and include two months at no charge. Changes to Developer API list prices apply to Enterprise usage under the notice terms in the Terms of Service.

When an organization, user, or application reaches an agreed limit, StockUp may stop further requests, require administrator action, apply agreed overage charges, or suspend access to the affected model or resource. Enterprise usage credit and limits are separate from Starter, Plus, and Pro allowances and from the public Developer API's free allowances and promotions.

5. Data handling and model providers

StockUp is committed to reducing provider training, retention, and secondary use of Enterprise prompts, responses, documents, and related data where controls are available. StockUp may configure provider settings, select applicable provider options, or seek contractual protections that limit training and retention.

Some model, search, hosting, storage, and infrastructure providers operate independently of StockUp. Their systems, policies, and technical controls may change. StockUp cannot guarantee zero retention or zero training use unless a signed Enterprise agreement expressly provides that commitment.

Unless a signed Enterprise agreement says otherwise, StockUp does not provide a blanket zero-retention guarantee, a blanket no-training guarantee, or a guarantee that every provider will exclude Enterprise data from secondary use.

6. Security, confidentiality, and compliance

Each party must protect confidential information received from the other party and use it only for the agreed business purpose. The organization must ensure that it has the right to submit prompts, documents, employee identifiers, and other data to StockUp.

Security questionnaires, data residency, encryption, incident notification, audit support, provider configuration, and other special requirements apply only when written into the applicable Enterprise agreement or order form.

7. Support and service levels

Enterprise onboarding, support response times, escalation procedures, uptime commitments, service credits, and dedicated assistance apply only when included in a signed Enterprise agreement or order form. An Enterprise plan preview does not create an SLA.

8. Acceptable use and audit

Enterprise users may not bypass quotas, share credentials outside the organization, attribute requests to an unauthorized user, reverse engineer protected systems, resell access without permission, or use StockUp for unlawful activity or market manipulation.

StockUp may record organization usage, quota events, key changes, member changes, and security events in Enterprise audit logs. Administrators may review organization-level usage and access records as permitted by the Enterprise configuration.

9. Suspension and offboarding

StockUp may suspend an Enterprise user, key, application, model, or organization for security risk, abuse, unpaid amounts, quota manipulation, a Terms violation, loss of authorization, or a legal requirement.

When Enterprise access ends, the organization must stop using Enterprise credentials and remove StockUp integrations from its systems. Data deletion and retention follow the Privacy Policy and any applicable written Enterprise agreement.

10. Related documents

See the StockUp Terms of Service, Privacy Policy, API Acceptable Use Policy, and Enterprise page. Questions about Enterprise terms can be sent to support@stockup.cc or to the contact listed in your Enterprise agreement.