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

Build

Versions and live

Changing a toolset without downtime, and rolling back when a change makes things worse.

Every build of a toolset is a numbered version. Requests go to whichever version the live alias points at, so a new build never interrupts traffic: the old version answers until the new one is ready.

Immutable versions and zero-downtime live promotion

#Build a new version

Send the complete new tool list:

bash
curl https://api.bluwing.si/v1/bricks/brk_7m2q9xk4hd3vfc8r/versions \
  -H "Authorization: Bearer $BLUWING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "tools": [ ... ], "base_version": 3, "options": { "auto_activate": true } }'

base_version is the version you started from. If someone built another version in the meantime, the answer is 409 VERSION_CONFLICT instead of quietly overwriting their change.

Only tools that are new or changed are charged, one credit each. Sending the same list again costs nothing and returns the existing version with reused: true.

Note

The Free plan builds new toolsets but can't add versions to one (403 FREE_TIER_EDIT_NOT_ALLOWED). Any paid plan can.

#Patch instead of resending

For a large toolset, send only the differences with PATCH /v1/bricks/{id}/tools:

json
{
  "base_version": 3,
  "add": [ { "type": "function", "function": { "name": "issue_voucher", "description": "...", "parameters": { "type": "object", "properties": {} } } } ],
  "update": [ { "type": "function", "function": { "name": "refund_order", "description": "...", "parameters": { "type": "object", "properties": {} } } } ],
  "remove": ["legacy_refund"]
}

The result is a new version, charged the same way.

#Point live somewhere else

To roll back, or to release a version you built without auto_activate:

bash
curl -X PUT https://api.bluwing.si/v1/bricks/brk_7m2q9xk4hd3vfc8r/aliases/live \
  -H "Authorization: Bearer $BLUWING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "version": 2 }'

Only a ready version can be live. The change takes effect for the next request. Pass expected_row_version (from GET /v1/bricks/{id}) to make the move conditional; a mismatch answers 409 ALIAS_CONFLICT.

#Call a specific version

live is the default. To test a version before it goes live, name it in the request:

json
{ "input": "Refund order 4412", "version": 4 }

In the console, each toolset's page lists its versions with a Make live or Roll back button.

PreviousToolsets and buildsNext Resolve a request

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

On this page

  • Build a new version
  • Patch instead of resending
  • Point live somewhere else
  • Call a specific version