Quan API Enterprise: Admin and Developer Setup Guide

Who This Guide Is For

This guide is for two groups inside an Enterprise account: admins who manage company access and developers who integrate Quan into internal apps, analyst tools, dashboards, copilots, workflow queues, or customer-facing financial products.

Enterprise Setup Flow

1. Create or sign in to a StockUp account on the Quan API Enterprise page.
2. Create the Enterprise organization for your company.
3. Request a plan from the dashboard. StockUp must approve or activate the plan before employee access and Enterprise models are fully unlocked.
4. Create an Enterprise API key from the dashboard.
5. Add employees in Manage Access and assign each one a monthly token quota.
6. Developers call POST /v1/query with the Enterprise API key, an Enterprise model alias, and the employee identifier header.

Enterprise Model Names

Use these aliases when a request should go through the Enterprise-only path. They map to the Enterprise prompt files and enforce Enterprise access checks.

Required Headers

Enterprise requests need the normal API authentication header plus a member attribution header. The member header lets StockUp apply the right per-user quota.

Quick cURL Example

curl -X POST https://stockup.cc/v1/query \
  -H "Authorization: Bearer sk_quan_ent_your_key" \
  -H "X-Enterprise-User-Id: employee_firebase_uid" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "quan-3-4-enterprise",
    "messages": [
      {
        "role": "user",
        "content": "Review AAPL, MSFT, and GOOGL for earnings risk, valuation sensitivity, and what our analyst team should watch next."
      }
    ],
    "stream": false,
    "googleSearch": true,
    "temperature": 0.2
  }'

JavaScript Backend Example

Keep Enterprise keys on the server. Do not expose sk_quan_ent_... keys in browser JavaScript, mobile app bundles, public repos, or client-side logs.

async function runEnterpriseQuan({ enterpriseUserId, prompt }) {
  const response = await fetch("https://stockup.cc/v1/query", {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${process.env.STOCKUP_ENTERPRISE_API_KEY}`,
      "X-Enterprise-User-Id": enterpriseUserId,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      model: "quan-3-4-enterprise",
      messages: [{ role: "user", content: prompt }],
      stream: false,
      googleSearch: true,
      temperature: 0.2
    })
  });

  const data = await response.json();
  if (!response.ok) {
    throw new Error(data.error || "Quan API Enterprise request failed");
  }
  return data?.candidates?.[0]?.content?.parts?.map(part => part.text || "").join("");
}

Python Example

import os
import requests

payload = {
    "model": "quan-3-4-deep-research-enterprise",
    "messages": [
        {
            "role": "user",
            "content": "Create a research brief for our semiconductor coverage list. Focus on SEC filing changes, earnings risk, margin pressure, and major catalysts."
        }
    ],
    "stream": False,
    "googleSearch": True,
    "temperature": 0.15
}

res = requests.post(
    "https://stockup.cc/v1/query",
    headers={
        "Authorization": f"Bearer {os.environ['STOCKUP_ENTERPRISE_API_KEY']}",
        "X-Enterprise-User-Id": os.environ["STOCKUP_ENTERPRISE_USER_ID"],
        "Content-Type": "application/json"
    },
    json=payload,
    timeout=120
)

res.raise_for_status()
print(res.json()["candidates"][0]["content"]["parts"][0]["text"])

How Per-User Quotas Work

Every Enterprise member has a monthly token quota. New users default to 200,000 tokens per month. Admins can increase or decrease that number in Manage Access.

• Quota period: usage is tracked by calendar month using a period key like 2026-07.
• Default user limit: 200,000 tokens per member per month.
• Usage source: successful Enterprise API responses increment member and organization token usage.
• Limit reached state: the user row shows a red ! indicator when usage reaches or exceeds the quota.
• Blocked requests: if overages are off and the member is projected to exceed quota, the request is blocked before the model call.

How Admins Change a User Limit

1. Open the Enterprise dashboard.
2. Go to Manage Access.
3. Find the employee row.
4. Use the quota input to set the monthly token limit. Example: 500000 for 500k tokens/month.
5. Optionally enable Overage for that user.
6. Click Update.

Enterprise Prices and Organization Token Pools

The organization also has a monthly token pool based on the selected Enterprise plan. Even if an individual user has quota remaining, Enterprise model calls can be blocked if the organization monthly pool is exhausted. These are preliminary starting prices and flexible planning baselines; StockUp can adjust pricing, token pools, seats, support structure, and rollout design when contacted for a real deployment. Final terms depend on usage, security review, model mix, grounding behavior, and contract structure.

Common Errors and Fixes

Admin Best Practices

• Start users at the default 200k monthly quota, then increase limits for production workflows or heavier analyst users.
• Give shared service accounts higher limits only when the downstream app also tracks the real user internally.
• Keep overages disabled for new teams until the cost model is reviewed.
• Rotate Enterprise API keys if they appear in logs, tickets, chat tools, or client code.
• Disable users who leave the company or no longer need API access.
• Use separate keys for development, staging, and production when possible.

Developer Best Practices

• Use Enterprise aliases only for Enterprise workloads. Keep public model names for normal developer API tests.
• Send a stable employee UID in X-Enterprise-User-Id on every Enterprise alias request.
• Store the Enterprise API key server-side and proxy client requests through your backend.
• Use stream: true for chat-like interfaces and stream: false for background jobs or workflow steps.
• Use quan-3-0-enterprise for routing/classification and quan-3-4-deep-research-enterprise for high-value research tasks.
• Handle 402 and 403 responses explicitly so your users understand whether the issue is quota, plan activation, or credentials.

Security and Data Handling Notes

Enterprise access is planned around stronger company controls, private Enterprise data-handling review, and no Quan prompt/response storage where supported by Enterprise configuration. Do not describe the public API as zero-retention. Final privacy, retention, provider, grounding, and contract terms should be confirmed during Enterprise onboarding.

Production Rollout Checklist

1. Confirm your Enterprise plan is active.
2. Create separate Enterprise API keys for dev, staging, and production.
3. Add all initial employees in Manage Access.
4. Set quotas for each employee or service-account user.
5. Decide whether overages are allowed for each user.
6. Update backend code to send X-Enterprise-User-Id.
7. Log request IDs and app-side user IDs, but avoid logging prompts or API keys in plaintext.
8. Monitor quota bars and red limit indicators during the first rollout week.
9. Move heavier workflows to Deep Research only where the added reasoning depth is worth the token usage.
10. Review data-handling and provider configuration before sending sensitive internal research at scale.

Enterprise Resources

Use these public resources when planning a company rollout, internal developer handoff, security review, or Enterprise procurement review.

• Quan API Enterprise landing page for plan requests, company positioning, organization access, and Enterprise dashboard entry.
• Enterprise Financial AI API page for company, team, fintech, bank, and financial-institution use cases.
• StockUp developer docs for the core API integration guide and developer portal.
• OpenAPI YAML and OpenAPI JSON for machine-readable API discovery.
• StockUp privacy policy and StockUp terms for legal, data-handling, and platform-use review.