Bluwing/Docsv0.9.0
Operational
API ReferenceConsole

Get started

  • Introduction
  • Quickstart
  • How it works

Build

  • Tool format
  • Matching hints
  • Toolsets and builds
  • Versions and live

Call

  • Resolve a request
  • Reading responses
  • OpenAI and Anthropic compatibility

Account

  • Authentication
  • Credits and billing
  • Limits
  • Errors
  • Security and data
  • FAQ

Account

FAQ

Short answers to the questions people ask first.

#Do I still need a language model?

Yes, for talking to your users. Bluwing replaces the part where the model reads every tool definition and decides which to call. Your model still writes the replies, and handles turns where the answer is no_tool.

#Will it work with my framework?

If the framework can call an HTTP endpoint, or lets you set an OpenAI base URL, yes. The compatibility page shows the OpenAI and Anthropic SDKs.

#What happens when it's not sure?

When a tool fits but a required value is missing, the answer is needs_input with a question. When nothing fits, it's no_tool. It doesn't guess an argument that isn't in the request or your facts. Each call also has a confidence you can set your own threshold on.

#Does it handle several steps in one message?

Yes. "Find the invoice from Acme and add its total to the sheet" comes back as calls in order, with steps that need an earlier result listed under pending.

#How many tools can a toolset have?

20 on Free, 2,000 on Plan A, 10,000 on Plan S, and no limit on S+. The cost is metered strictly at $0.015 per 1,000,000 input tokens (output tokens are completely free), whatever the size of the toolset.

#How long does a build take?

About a minute for a few dozen tools, a few minutes for thousands. The old version keeps answering while a new one builds.

#Can I test a change before it goes live?

Build without auto_activate, call the new version by number ("version": 4), then move live when you're happy. See Versions and live.

#Do tokens expire?

Monthly plan tokens are for that month. The 5,000,000 welcome tokens and all purchased top-ups never expire.

#Can I get a refund?

Failed builds are refunded automatically. For anything else, write to [email protected].

#Where do I see what's going on?

The console's overview shows credit use per day, split into calls and builds, and the Billing page has the full history with CSV export.

PreviousSecurity and data

Something unclear or missing? Write to [email protected] and we'll fix the page.

On this page

  • Do I still need a language model?
  • Will it work with my framework?
  • What happens when it's not sure?
  • Does it handle several steps in one message?
  • How many tools can a toolset have?
  • How long does a build take?
  • Can I test a change before it goes live?
  • Do tokens expire?
  • Can I get a refund?
  • Where do I see what's going on?