Create account
For businesses and self-employed professionals only

Menu

Data per person, separate and erasable.

With external_identifier you assign history, memories and files to a person in your application. When you delete them, you get a receipt that stays available afterwards.

How an end user is created.

You assign the identifier yourself. It is a stable string of up to 255 characters and stays within your team. The first call with an unknown identifier creates the end user; you can also do this up front with POST /v1/end-users.

Call with an end-user identifier
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-42",
    "messages": [{ "role": "user", "content": "Which plan am I on again?" }]
  }'
Create an end user up front
curl https://api.flowmodels.one/v1/end-users \
  -H "Authorization: Bearer $FLOWMODELS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "external_identifier": "customer-42",
    "metadata": { "plan": "pro" }
  }'

What the identifier changes.

external_identifier

  • The history is held by FlowModels; you only send the new messages and the conversation from the last response.
  • Relevant memories and file passages of the same person are added to the context.
  • Long histories are summarized. These model calls are also part of the billed usage.

Without an identifier

  • The history is yours; you send it with every call.
  • FlowModels summarizes nothing on its own.
  • No memory is searched and none is stored.

What is stored per person.

DataLimitsAccess
Metadata At most 50 entries, values up to 1,000 characters PATCH /v1/end-users/{uuid}
Memories Text up to 10,000 characters per memory, automatic detection can be turned off POST, GET, PATCH, DELETE /v1/memories
Files 32 MB per file, 100 files per end user, 5 GB per team POST, GET, DELETE /v1/end_users/{uuid}/files

Files are evaluated as text. Allowed are pdf, docx, doc, rtf, xlsx, pptx, txt, md and csv.

Automatic memories are on for new end users. With memory_extraction_enabled: false you turn them off per person.

Write a memory
curl https://api.flowmodels.one/v1/memories \
  -H "Authorization: Bearer $FLOWMODELS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "external_identifier": "customer-42",
    "text": "Prefers answers in English."
  }'

Erasure with a receipt.

DELETE /v1/end-users/{uuid} removes this person's working data: history, memories, files and logs. Private files are deleted in the background, and the receipt shows you when that is finished. Billing and usage lines are kept.

The receipt only contains counts, no content. It stays available under the identifier after the deletion, because that is exactly when you need it.

Delete an end user
DELETE https://api.flowmodels.one/v1/end-users/018f1234-5678-7abc-9def-0123456789ab
Authorization: Bearer $FLOWMODELS_API_KEY
Fetch receipts
GET https://api.flowmodels.one/v1/end_users/018f1234-5678-7abc-9def-0123456789ab/erasures
Authorization: Bearer $FLOWMODELS_API_KEY
Erasure receipt Example
Status
completed
Requested
2026-11-09T08:15:00+01:00
Completed
2026-11-09T08:15:40+01:00
AreaBeforeAfter
memories 12 0
end_user_files 3 0
conversations 7 0
messages 86 0
stored_objects 3 0

objects_remaining 0

FlowModels has no budget per end user. How to keep track of usage per person anyway is covered under Budgets.

Create a key, name a model, start building.

FlowModels is aimed exclusively at businesses and self-employed professionals.