ConvoOK
Use cases

Your content, searchable by AI — inside your own product

Index everything you have written, then search it from your own software. No widget, no inbox, no agent. Just the part you actually need.

Start free Get a quote for this

What is going wrong

The situation today

You have thousands of pages of documentation, policies, product data and past answers. Your own search finds none of it, and building retrieval yourself means embeddings, a vector store, chunking, re-indexing and a bill that grows while you learn.

What ConvoOK does

The answer

Upload it, crawl it, or point us at a read-only database. We index it, keep it fresh, and answer searches through a documented REST API with your own key. You keep the interface; we do the retrieval.

In practice

What you actually get

  • PDFs, Word files, pasted text, your website, or a read-only query against your own database.
  • A re-crawl of an unchanged page costs nothing, so a nightly refresh is affordable.
  • Search from your own backend with an API key, scoped to exactly what it may read.
  • Tag knowledge by client, so one index can answer for many of your customers.
What you would pay for

The limits that actually move for this

Every limit is sold on its own. If this is the only thing you need, these are the only numbers your quote is built from — and the maximum you agree is the maximum the system enforces.

  • Knowledge pages pages Metered

    Pages of knowledge indexed: uploads, pasted text, website pages and database rows.

  • Knowledge searches searches a month Metered

    Semantic searches somebody runs: the Knowledge API from the customer's own software, Build → Vector store, and the test search on the Knowledge page. NOT the searches an agent makes while answering a customer — those are inside the chat message and voice minute prices.

  • File storage MB Metered

    Files held: uploads, attachments and call recordings.

  • Database connections connections Generous by default

    Read-only databases connected as knowledge.

This is the clearest example of buying one thing. A big knowledge allowance and a big search allowance, quoted on their own, with the maximum you agree enforced as a hard stop.

Get a quote for exactly this

Before you ask

Questions about Knowledge & AI search

Can I use only this, without the chat or voice parts?

Yes. Knowledge pages and API searches are their own limits, and a contract can raise those and leave everything else at the tier's amount. You are quoted for what you asked for.

What counts as one search?

One call to the Knowledge API from your software. Searches a ConvoOK agent makes while answering a customer are already inside that conversation and are not counted again.

What happens when I reach the agreed maximum?

Searches are refused rather than silently billed. The maximum is a stop you agreed, and you can see how close you are on your own billing screen.

Ready to put this to work?

Start on the free tier with your own documents, or tell us what you need and we will price exactly that.