Superflows says it adds an AI assistant to a SaaS product without an in-house AI team. The homepage describes three jobs: analytics that call your APIs and then write code, actions prepared for a user to confirm, and documentation answers. Setup is upload an OpenAPI spec and docs, approve what the assistant may say, paste one frontend snippet, and read the questions users ask. The pricing page sells that as Testing, Scale, and Enterprise.
SaaS teams that can upload an OpenAPI spec and want chat to call those endpoints.
Products where an action should be prepared in chat and confirmed before it runs.
Teams comparing a 50-query playground against Scale’s 10,000 Chat-to-API allowance.
Know the trade-offs
Testing’s 50 queries are described as playground queries, not as a production allowance.
Enterprise says “All Growth features,” but the public pricing page never defines a Growth plan.
The footer is dated 2023 and says the company pivoted.
Analytics, confirmed actions, and the four setup steps.
Answers that call your API and then calculate
Analytics is not a static help paragraph. The homepage says Superflows calls the product’s APIs to get data, and then writes code to crunch the numbers. Users can ask for a plot instead of waiting on a new dashboard. You approve answer formats, so you can trust the assistant will not go off the rails. The pricing footnote defines the billable unit. A Chat-to-API query is a message sent to the chat interface by a user that triggers a query to your API. Chat-to-Docs is a separate counter. The pages do not say whether one message can increment both.
The actions section says Superflows can take actions on behalf of your users. It prepares actions for users, and asks for confirmation before completing them. It also says anything the product can do, the assistant can do too. The CRM example has users type in a box to get information and complete tasks. Sample lines cover which deals to prioritise, how to progress them, creating reminder tasks, and which outreach made the most leads this month. Those are the site’s samples, not a customer transcript, and no CRM vendor is named.
The homepage numbers four steps. Connect your API and docs and define the endpoints available and docs your assistant can reference. Approve the answers the AI Assistant can give. Add one code snippet to your frontend, and your AI assistant is live. Then see what users ask and which answers they mark useful. Upload your OpenAPI spec and docs, and Superflows will build your AI assistant. Configure authentication, and start testing in the playground. The Testing card also lets you set endpoints and connect the API there. The pages do not paste the snippet or name a framework. An Open Source heading points to GitHub for releases and feature suggestions, and names a dashboard repo plus chat UI components. No license text is included.
Follows the CRM sample. A user types which deals to prioritise, weighted by size and close probability, instead of building that dashboard. The assistant is supposed to call APIs and write code. You still approve answer formats. Keep the question on endpoints you uploaded. Suggested only: the page does.
Turn a chat command into a confirmed task
A suggested action flow uses the sample line “Create tasks to remind me to take these steps.” The homepage says the assistant prepares the action and asks for confirmation before completing it. The user should see the task list before it is written back to the product. Do not skip that confirm step because the page also says the assistant can do anything the product can do.
Answer a how-to from your docs
A suggested docs path is the third homepage block: once Superflows is integrated, users have a product expert in the product. The setup step says the assistant can reference docs you define. On Scale and Enterprise, Chat-to-Docs is a separate allowance from Chat-to-API. Upload the docs you are willing to have quoted. This suggested use is not a support-ticket test.
How to get started with Superflows
1
Upload the spec and docs
Upload your OpenAPI spec and docs. Define which endpoints and documents the assistant may reference.
2
Test in the playground
Configure authentication and connect the API in the playground. Testing includes 50 queries there, one seat, and community support.
3
Approve answers, then embed
Approve the answers and formats the assistant can give. Add one code snippet to your frontend when you want it live.
4
Read the questions people ask
After launch, review what users ask and which answers they mark useful. Match that volume to Chat-to-API and Chat-to-Docs allowances before you leave Testing.
Testing, Scale, and Enterprise on the pricing page.
Testing is labeled Free. Scale is $999 Monthly. Enterprise is Custom. No other dollar amount appears on that page.
Testing
Evaluating in the playground before a production embed.
Free.
Labeled Free; no dollar amount.
50 queries in the testing playground
Set the API endpoints the assistant can access
Single seat and community support
Scale
A product with multiple seats and live API traffic.
$999.
Monthly.
10,000 Chat-to-API queries and 200,000 Chat-to-Docs queries
Unlimited testing in the playground and multi-tenant APIs
Unlimited seats, custom setup, and priority email support
Enterprise
Volumes above the Scale query counts.
Custom.
No dollar amount shown.
10,000+ Chat-to-API queries and 200,000+ Chat-to-Docs queries
Access audit logs and priority feature requests
The card says All Growth features; Growth is not defined on the page
A Chat-to-API query is a message sent to the chat interface by a user that triggers a query to your API. Scale says it includes all free features, then adds the allowances above. Enterprise’s “All Growth features” line does not match a Growth card on this page. Review sites quote other prices; those amounts are not on the public cards. The 2023 pivot line means you should confirm the card is current before you budget $999.
Use Chatbase when you want that assistant, not Superflows’ Testing or Scale cards.
Superflows’ public pages center on API calls, doc answers, and confirmed actions inside a SaaS product. They do not describe Chatbase. Use Chatbase when you mean that product, not Superflows’ Testing or Scale cards.
You need a general assistant, not one wired to your API.
Claude is a general assistant listing. Superflows is documented here as an embed that uses your OpenAPI spec, your docs, and a confirmation step before actions. These pages do not describe Claude. Pick Claude when the chat should not call your product’s endpoints.
Superflows: common questions
What does the public pricing page charge?
Testing is labeled Free and includes 50 queries in the testing playground, one seat, and community support. Scale is $999 Monthly, with 10,000 Chat-to-API queries, 200,000 Chat-to-Docs queries, unlimited seats, and priority email support. Enterprise is Custom. No other dollar price is shown.
The pricing page says a Chat-to-API query is a message sent to the chat interface by a user that triggers a query to your API. Chat-to-Docs is counted separately. The pages do not define a docs query the same way, and they do not price overage past the shown caps.
The homepage says it prepares actions for users, and asks for confirmation before completing them. It also says the assistant can do anything the product can do. The confirm step is the control the page states. It does not describe a bypass.
Upload your OpenAPI spec and docs, configure authentication, and test in the playground. Approve the answers the assistant can give. Add one code snippet to your frontend, and the homepage says the assistant is live. The public docs URLs did not return steps beyond that summary.
The homepage has an Open Source heading and tells you to follow GitHub, watch releases, and suggest features. It names a dashboard repo and a chat UI repo.
The Enterprise card says “All Growth features,” then lists higher query floors, audit logs, custom setup, and priority feature requests. Testing, Scale, and Enterprise are the only plan names on that page. Growth is not given its own price or feature list.
NavHunt did not run Superflows, did not upload an OpenAPI spec, and did not send a chat message. Behavior described here is from the homepage reviewed on 6 October 2026. The Testing, Scale, and Enterprise cards, including the $999 Scale price, are from the pricing page public the same day. Docs URLs in the research file returned no usable text. Review-site prices were not copied. The 2023 pivot line is quoted from the footer, not investigated further. This description is based on Superflows's official materials reviewed on 2026-10-06, including Superflows product homepage, Superflows Testing, Scale, and Enterprise cards, Superflows about page.