Account, plans, and billing

Workspace access

Your analyses, projects, and API keys belong to a workspace. Use the workspace switcher when you collaborate across organizations, and confirm the active workspace before creating or deleting work.

Workspace membership determines which projects and settings you can see. If an expected project is missing, confirm the active workspace before creating a duplicate or assuming data was removed.

Roles and safe collaboration

Use the least access required for each collaborator. Before sharing an exported result, check that it does not expose confidential creative, internal strategy, or client information beyond the intended audience.

Signing out on a shared device ends the authenticated session, but you should also avoid saving API keys or confidential exports in shared browser storage or download folders.

Usage limits

Limits depend on the current plan and the type of action. The workspace shows the applicable allowance before a gated action. For current prices and plan descriptions, use the pricing page rather than relying on copied documentation.

If an action is unavailable, check the displayed plan and allowance first. Limits can differ by workflow, so an available Market view does not imply the same allowance for RoastIQ, BuyerLens, or API analysis.

Billing controls

Open Settings inside the workspace to review subscription state and available billing actions. Only use the checkout and customer-portal links generated for your signed-in account.

Use the billing portal for supported subscription management actions. Do not send payment-card details through chat, support messages, or project fields. If billing state appears out of date after checkout, refresh the workspace and check the account used for payment before attempting a second purchase.

API keys

API keys are shown once when created and stored as hashes. If a key is lost, revoke it and create another. Never place a live key in client-side code, browser storage, screenshots, or a public repository.

Recommended key hygiene:

• Create separate keys for separate environments or integrations.
• Store keys in a server-side secret manager.
• Rotate a key when a collaborator leaves or exposure is suspected.
• Revoke unused keys instead of keeping them for convenience.
• Use test keys when validating an integration without invoking the live pipeline.

Account and billing troubleshooting

When contacting support about access or billing, include the workspace name, approximate time, and a non-sensitive description of the action. Never include passwords, complete payment details, session cookies, or a full API key.

For integration access, continue to the API reference. For current plan descriptions, use Pricing.