A support assistant for a shop.
The furniture workshop Lumivo Werkhaus wants to answer questions about orders automatically. The assistant reads the order status from the shop itself and is billed through its own key.
Fictional example: Lumivo Werkhaus does not exist. This page shows neither real customer data nor results, only how you would get there.
How it is built.
-
Its own key with a monthly limit
The shop gets its own API key with a monthly limit. Once the limit is reached, the API answers with
Budgets429 spend_limit_exceededand the shop shows how to get in touch. -
Streaming and your own tools
With
stream, the response arrives piece by piece. The model calls theorder_statustool, which runs in the shop, and the result goes back as a message with the roletool. -
One identifier per customer
With
End usersexternal_identifier, FlowModels keeps the history per person. Someone writing again after two days does not have to start from scratch. -
No double cost on retries
For the summary of a ticket without streaming, the shop sends an
Idempotency-Key. If the connection drops, the same key gets the same response instead of paying twice.
curl https://api.flowmodels.one/v1/chat/completions \
-H "Authorization: Bearer $FLOWMODELS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "anthropic/claude-fable-5-1",
"external_identifier": "customer-4711",
"stream": true,
"tools": [{
"type": "function",
"function": {
"name": "order_status",
"description": "Returns the status of an order",
"parameters": { "type": "object", "properties": { "order_number": { "type": "string" } } }
}
}],
"messages": [{ "role": "user", "content": "Where is my dining table?" }]
}'