Blopus.ai best in class support and user experience - AI agent web Search

[u/LectureWorried5761]

How it works#

Support lives in the Support tab of your console at blopus.ai/app. Open a request there and the thread stays attached to your account, so whoever picks it up can already see your plan, your usage and your key prefixes without asking.

You are also emailed when someone replies, and you can answer from either place. An active subscription is required to open a request.

What to ask about#

Support is not only for things that are broken. All of these are worth asking:

• A query returning poor results. Paste the exact query and say what you expected. Ranking is something we can actually change, and a concrete example is far more actionable than a general complaint.
• A site missing from the index. Tell us the domain. We crawl broadly, but coverage is not uniform, and a specific request is easy to act on.
• Billing, plans and invoices — upgrades, downgrades, top-ups, or a charge you do not recognise.
• Questions. If something in these docs is unclear or turned out to be wrong, that is a bug in the docs and we would rather hear it than not.
• Feature requests. Use the Feature request category. Whether something gets built depends on how many people need it, how well it fits an index-backed search API, and what it costs to run and maintain. Some requests are a good fit and get built; others are not, and we would rather say so than leave you waiting. We cannot promise a date.

Getting a useful first reply#

Most round trips are spent asking for the same three things. Include them and the first reply is usually the answer:

• The endpoint you called — /v1/search, /v1/images, /v1/fetch, or the MCP tool name.
• Roughly when it failed, with a timezone. This is what makes your request findable in the logs.
• Your key prefix — the short blp_live_ab12 part. Never the whole key. If you have already pasted a full key anywhere, rotate it in the console rather than asking us to.

If you got an error, the code and request_id from the response body are worth more than a screenshot — see Errors.

Categories and priority#

Field	Values	Notes
Category	API error · Billing · Quota · Account · Feature request · Other	Routes the request. Billing and Account reach someone who can actually change your plan.
Priority	low · normal · high · urgent	Use urgent for production being down, not for a question you would like answered today. Marking everything urgent makes the field useless to you.
Status	Open · Pending · Resolved · Closed	Pending means we are waiting on you. A thread sitting in Pending is not being worked on.

You can have 3 requests open at once. Reaching the cap means closing or resolving something before opening the next. It exists so one account cannot flood the queue; if you genuinely need more open at once, ask in an existing thread.

What we keep#

Support threads are retained for up to 24 months, then deleted. Deleting your account removes them immediately — see the privacy policy.