Version 2026-11-03 (supersedes all prior versions)
1. SCOPE & INCORPORATION
This Pricing Schedule forms part of, and is incorporated by reference into, the SimplyAsk.ai Terms of Service (the “TOS”). Capitalized terms not defined here have the meanings given in the TOS. This page sets out: (a) the Transaction types, Billing Units, Credits per Billing Unit (Credit Weights), Fair-Use Limits and counting rules that apply to every account; (b) the Credit Weights for AI models; (c) plan prices, Included Credits and Add-On terms for Symphona Explore Accounts; (d) the Trial; and (e) Activity retention periods.
For Partner‑Governed Accounts and Enterprise Agreement Accounts, this Pricing Schedule governs metering mechanics (Sections 2 to 5 and Sections 8 to 10); plan prices, Included Credits, per-Credit overage rates and Overage Spend Limits are as set out in the applicable signed order, agreement or Side Letter. For Partner‑Governed Accounts, it also governs our invoicing to the Authorized Resale Partner; it does not change the Partner‑End Customer commercial pricing, except for any regulatory adjustments permitted by the TOS.
All monetary amounts are denominated in United States Dollars (“US$”) and exclude taxes. These plans and rates apply to the Services in our shared SaaS environment; self-hosted (private cloud or on-premises) deployments are priced by signed agreement.
2. KEY CONCEPTS
- Credits: The unit of metered consumption of the Services.
- Transaction: An operation that consumes Credits (for example, Process Executions, Agent Sessions, AI Tokens and Service Tickets). Transactions may have sub‑types with different Billing Units and Credit Weights.
- Billing Unit: The unit in which a Transaction type or sub‑type is measured (for example, one Process Execution or 10,000 AI tokens).
- Credit Weights: The number of Credits consumed per Billing Unit for a given Transaction type or sub‑type.
- Fair-Use Limit: A usage limit for a Transaction type, beyond which further usage counts as additional Billing Units.
- Usage Period: The monthly metering period defined in the TOS.
3. TRANSACTION TYPES & CREDIT WEIGHTS
| Transaction | Billing Unit | Credits per Billing Unit | Fair-Use Limit |
|---|
| Process Execution | 1 Process Execution | 25 | Up to 1,000 executed steps per execution; each further 1,000 steps (or part) counts as one more Process Execution |
| Agent Session | 1 Agent Session | 15 | Up to 50 turns per session; each further 50 turns (or part) counts as one more Agent Session |
| AI Tokens | Per model (Section 4) | Per model (Section 4) | None |
| Sent Email | 1 email | 1 | None |
| Sent SMS | 1 SMS segment | 5 | None |
| Handled Call Minute | 1 minute | 42 | None |
| Web Search | 1 search query run by the model provider | 4 | None |
| Function Execution | 1 function run | 2 | Up to 60 seconds per execution; each further 60 seconds (or part) counts as one more Function Execution |
| Service Ticket | 1 Service Ticket created | 10 | None |
| File Storage | 1 GB-month | 25 | None |
| Knowledge Base Storage | 1 GB-month | 100 | None |
| Active Phone Number | 1 phone number per Usage Period | 500 | None |
4. AI MODEL CREDIT WEIGHTS
AI Tokens are metered per model and per provider tier. “Standard” is the provider’s standard tier; “Priority” is the provider’s priority tier (for claude-opus-5-5, Anthropic’s fast mode; for Baseten models, the Fast variants, which are listed as separate models); “Batch” is the provider’s batch processing. A blank cell means the provider does not charge for that token type; 0.00 means it is not currently charged.
4.1 Text models (Credits per 10,000 tokens)
| Provider | Model | Tier | Input | Output | Cache write | Cache read | Long-context threshold (tokens) | Long-context multiplier |
|---|
| OpenAI | gpt-6-astra | Standard | 20.00 | 100.00 | 25.00 | 2.00 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6-astra | Priority | 40.00 | 200.00 | 50.00 | 4.00 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6-astra | Batch | 10.00 | 50.00 | 12.50 | 1.00 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6.1-sol | Standard | 4.00 | 20.00 | 5.00 | 0.20 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6.1-sol | Priority | 8.00 | 40.00 | 10.00 | 0.40 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6.1-sol | Batch | 2.00 | 10.00 | 2.50 | 0.10 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6.1-terra | Standard | 2.00 | 10.00 | 2.50 | 0.10 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6.1-terra | Priority | 4.00 | 20.00 | 5.00 | 0.20 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6.1-terra | Batch | 1.00 | 5.00 | 1.25 | 0.05 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6-luna | Standard | 0.20 | 1.00 | 0.25 | 0.02 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6-luna | Priority | 0.40 | 2.00 | 0.50 | 0.04 | 272,000 | 2.0x in, 1.5x out |
| OpenAI | gpt-6-luna | Batch | 0.10 | 0.50 | 0.125 | 0.01 | 272,000 | 2.0x in, 1.5x out |
| Anthropic | claude-fable-5-1 | Standard | 20.00 | 100.00 | 25.00 | 0.50 | | |
| Anthropic | claude-fable-5-1 | Batch | 10.00 | 50.00 | 12.50 | 0.25 | | |
| Anthropic | claude-opus-5-5 | Standard | 8.00 | 40.00 | 10.00 | 0.40 | | |
| Anthropic | claude-opus-5-5 | Priority | 16.00 | 80.00 | 20.00 | 0.80 | | |
| Anthropic | claude-opus-5-5 | Batch | 4.00 | 20.00 | 5.00 | 0.20 | | |
| Anthropic | claude-sonnet-5-5 | Standard | 4.00 | 20.00 | 5.00 | 0.20 | | |
| Anthropic | claude-sonnet-5-5 | Batch | 2.00 | 10.00 | 2.50 | 0.10 | | |
| Anthropic | claude-haiku-5-5 | Standard | 0.20 | 1.00 | 0.25 | 0.02 | 100,000 | 5.0x |
| Anthropic | claude-haiku-5-5 | Batch | 0.10 | 0.50 | 0.125 | 0.01 | 100,000 | 5.0x |
| Google | gemini-4-argon | Standard | 8.00 | 40.00 | | 0.40 | | |
| Google | gemini-4-argon | Priority | 14.40 | 72.00 | | 0.72 | | |
| Google | gemini-4-argon | Batch | 4.00 | 20.00 | | 0.20 | | |
| Google | gemini-3.8-flash | Standard | 3.00 | 15.00 | | 0.30 | | |
| Google | gemini-3.8-flash | Priority | 5.40 | 27.00 | | 0.54 | | |
| Google | gemini-3.8-flash | Batch | 1.50 | 7.50 | | 0.15 | | |
| Google | gemini-3.5-flash-lite | Standard | 0.60 | 5.00 | | 0.06 | | |
| Google | gemini-3.5-flash-lite | Priority | 1.08 | 9.00 | | 0.10 | | |
| Google | gemini-3.5-flash-lite | Batch | 0.30 | 2.50 | | 0.04 | | |
| xAI | grok-4.7 | Standard | 4.00 | 12.00 | | 1.00 | 200,000 | 2.0x |
| xAI | grok-4.7 | Priority | 8.00 | 24.00 | | 2.00 | 200,000 | 2.0x |
| xAI | grok-4.7 | Batch | 3.20 | 9.60 | | 0.80 | 200,000 | 2.0x |
| Baseten | GLM-5.3 | Standard | 2.80 | 8.80 | | 0.28 | | |
| Baseten | GLM-5.3-Fast | Priority | 4.20 | 13.20 | | 0.42 | | |
| Baseten | GLM-5.3-Flash | Standard | 0.30 | 1.00 | | 0.06 | | |
| Baseten | Kimi-K3 | Standard | 6.00 | 30.00 | | 0.60 | | |
| Baseten | DeepSeek-V4-Pro-0813 | Standard | 2.64 | 7.92 | | 0.264 | | |
| Baseten | DeepSeek-V4.1-Flash | Standard | 0.60 | 2.40 | | 0.014 | | |
| Baseten | DeepSeek-V4.1-Flash-Fast | Priority | 1.20 | 4.80 | | 0.028 | | |
Long context: when a request (including cached tokens) exceeds a model’s long-context threshold (for xAI models, when it reaches or exceeds the threshold), the whole request is metered at the long-context multiplier. For OpenAI models the multiplier is 2.0x on input and cache tokens and 1.5x on output tokens. A blank threshold means the model has no long-context rate.
4.2 Image models: output
| Provider | Model | Credits | Billed per | Rate covers |
|---|
| OpenAI | gpt-image-2.5-sunburst | 60.00 | 10,000 output tokens | Any size |
| OpenAI | gpt-image-2.5-flare | 60.00 | 10,000 output tokens | Any size |
| Google | Nano Banana Pro (gemini-3-pro-image) | 48.00 | image | Up to 4K |
| Google | Nano Banana 2.1 (gemini-nano-banana-2.1) | 22.60 | image | Up to 4K |
| xAI | grok-imagine-image-2.0 | 16.00 | image | Up to 2K, medium quality |
| xAI | grok-imagine-image | 4.00 | image | 1K or 2K |
Models billed per image charge one rate, set at their largest size, whatever size is generated. Input sent to image models is metered separately under Section 4.3.
4.3 Image models: input (prompt text and input images)
| Provider | Model | Text input | Image input | Cached text input | Cached image input | Billed per |
|---|
| OpenAI | gpt-image-2.5-sunburst | 10.00 | 16.00 | 2.50 | 4.00 | 10,000 input tokens |
| OpenAI | gpt-image-2.5-flare | 10.00 | 16.00 | 2.50 | 4.00 | 10,000 input tokens |
| Google | Nano Banana Pro (gemini-3-pro-image) | 4.00 | 4.00 | | | 10,000 input tokens |
| Google | Nano Banana 2.1 (gemini-nano-banana-2.1) | 3.00 | 3.00 | | | 10,000 input tokens |
| xAI | grok-imagine-image-2.0 | | 2.00 | | | input image |
| xAI | grok-imagine-image | | 0.40 | | | input image |
Google charges one rate for text and image input, and a Nano Banana Pro input image counts as 560 tokens. OpenAI’s cached input rates apply only to images generated through the Responses API image tool.
4.4 Document AI models (Credits per page)
| Provider | Model | Credits per page | Used by |
|---|
| AWS Textract | Extract Text (Detect Document Text) | 0.30 | Extract Text step |
| AWS Textract | Extract Forms (Analyze Document Forms) | 10.00 | Extract Forms step |
| AWS Textract | Extract Tables (Analyze Document Tables) | 3.00 | Extract Tables step |
5. COUNTING RULES
- Process Executions: Counted once when a Process instance starts, whether it is started by API, schedule, webhook, event or form, including runs started from the editor for testing. A restart of the same Process counts as another Process Execution. A sub-Process called by a Process is part of its parent’s Process Execution. AI Tokens, emails, SMS, Function Executions and other Transactions used inside a Process Execution are metered separately.
- Agent Sessions: Counted once when a session is created. A session is one conversation (on any channel, including chat widgets and WhatsApp), one phone call, or one run of a Prompt AI Agent step in a Process; conversations are persistent and have no inactivity timeout. A Prompt AI Model step is not an Agent Session; its tokens are metered as AI Tokens. AI Tokens, Web Searches, Function Executions and call minutes used inside a session are metered separately.
- AI Tokens: For text models, Credits are calculated as tokens ÷ 10,000 × the model’s Credit Weight, separately for input, output, cache-write and cache-read tokens. Search results, fetched pages and tool output that enter the model’s context are metered as input tokens. Images sent to models hosted on Baseten are metered as input tokens at the model’s input rate, with no per-image charge. Image models are metered per image or per 10,000 output tokens as shown in Section 4.2, plus their input under Section 4.3. Document AI models are metered per page processed.
- Sent Emails: Counted after each successful send by a Process step, per message and not per recipient. Platform emails (such as invitations, password resets and usage notices) are not metered.
- Sent SMS: Counted per encoded segment of each outbound message (160 GSM-7 or 70 UCS-2 characters per segment). Inbound SMS is not metered.
- Handled Call Minutes: Call duration in seconds Ă· 60, rounded up per call. The same rate applies to minutes handled by an AI Agent and to transferred minutes.
- Web Searches: Each search query billed by the model provider counts as one Web Search, including page-browsing calls that are counted as searches for that provider (for xAI, browse_page and open_page calls). Search results that enter the model’s context are metered as AI Tokens, except where the provider does not charge for retrieved content.
- Function Executions: Each function invocation that starts counts, including failures, timeouts and runs started from the editor for testing; retries the platform makes on its own do not count. Code executed by an AI Agent in a model provider’s sandbox is metered as Function Executions, one per code-execution call plus one for each further 60-second block started. Where a model’s provider has no code-execution tool (as for models hosted on Baseten), code the AI Agent runs is executed as a temporary function in the Services and metered as a Function Execution in the same way.
- Service Tickets: Counted once when a Service Ticket is created, whether by a person, a Process or an AI Agent. Attachments are metered as File Storage.
- File Storage and Knowledge Base Storage: Stored bytes (for Knowledge Base Storage, Knowledge Base source bytes) are measured once a day, and the Usage Period’s average is metered. 1 GB = 1,000,000,000 bytes.
- Active Phone Numbers: Each phone number active at any point in the Usage Period.
- Calculation: AI Tokens and storage are metered proportionally, without rounding up to a whole Billing Unit. [Rounding of fractional Credits in a Usage Period total: to be confirmed.]
- Timestamp: Usage is recorded at the time the Transaction is logged by the Services (UTC).
6. SYMPHONA EXPLORE ACCOUNT PLANS
All plans include any number of users (subject to fair use under Section 5.2 of the TOS), every Transaction type in Section 3, and Activity retention of 90 days. Fees are charged monthly to your payment method, including on 12-month commitment plans.
| Plan | Commitment Term | Price per month | Included Credits per Usage Period | Add-On price | Add-On Credits | Default maximum Add-Ons per Billing Cycle |
|---|
| Symphona 1x | Monthly | $100 | 8,500 | $40 | 2,125 | 122 |
| Symphona 3x | Monthly | $300 | 25,500 | $115 | 6,375 | 40 |
| Symphona 10x | Monthly | $1,000 | 85,000 | $375 | 21,250 | 10 |
| Symphona 25x | Monthly | $2,500 | 212,500 | $940 | 53,125 | 2 |
| Symphona 1x | 12 months | $85 | 8,500 | $40 | 2,125 | 122 |
| Symphona 3x | 12 months | $255 | 25,500 | $115 | 6,375 | 40 |
| Symphona 10x | 12 months | $850 | 85,000 | $375 | 21,250 | 10 |
| Symphona 25x | 12 months | $2,125 | 212,500 | $940 | 53,125 | 2 |
The default maximum keeps a plan’s monthly price plus Add-Ons at or below US$5,000 per Billing Cycle (based on the monthly plan price). We may set a higher maximum for an approved customer; the maximum that applies to your subscription is shown in the Services. Add-On rules, including your Add-On setting, are in Section 21.1 of the TOS.
7. TRIAL
| Trial length | Trial Credits | Converts to |
|---|
| 14 days | 2,125 Credits, granted once | Symphona 1x (monthly), US$100 per month |
Trial eligibility, conversion and early-end rules are in Section 21.1 of the TOS.
8. PARTNER‑GOVERNED AND ENTERPRISE AGREEMENT ACCOUNTS
Plan prices, Included Credits, per-Credit overage rates and Overage Spend Limits are as set out in your signed order, agreement or Side Letter. Metering follows Sections 2 to 5. Unless your signed order states otherwise, Activity is retained for 90 days, or for 365 days on Business, Enterprise and Enterprise Scale plans.
9. MEASUREMENT FINALITY & DISPUTES
- Metering in the Services and our system logs (including Credits recorded per Transaction) is conclusive for billing purposes absent manifest error, as stated in the TOS.
- If you believe a manifest error occurred, notify us within the invoice dispute window specified in the applicable agreement.
10. ORDER & AGREEMENT PRECEDENCE
- If your signed order expressly fixes Included Credits and/or Credit Weights for your committed term, that order controls for that term.
- In any conflict between this page and a signed order or Enterprise Agreement on commercial pricing, the signed document controls for the committed term, subject to any regulatory adjustments permitted by the TOS.
11. CONTACT
Questions about this Pricing Schedule: legal@simplyask.ai