Product guide

Switch the project in the header, manage the projects of the organization in the settings and see what each role opens.

The words the console and this reference use — operation, flow, version, execution, reservation, pool, customer, credits — and what each one means.

What a flow is, how an operation code leads a request to it, and the states a flow goes through from its first draft to the archive.

Start a flow from a template or an empty canvas, connect a model, publish the flow and bind the operation code your requests will name.

The palette, the canvas and the panel of a node, how the draft is saved as you work, and the keys that speed it up.

What a request runs, how a draft becomes a published version, how two versions are compared and how a flow goes back to an earlier one.

Find an execution of a flow, read its cost and the path it took node by node, and watch the executions that run or wait right now.

The nine templates of the gallery, the rule each one expresses, and how a template becomes a flow that runs.

Read the requests for approval, approve or reject one, and know what happens when nobody decides in time.

How Slen holds money before a model call, what the hold does to your budgets, and how it is settled afterwards.

Create a budget, choose its period and what it covers, read how much of it is left, and change or archive it.

Write a policy — the conditions a request is checked against and what happens when they hold — put the policies in order and try a request against them.

Add your customers, keep a balance of credits for each of them, top it up, set what an operation costs in credits, block a customer and read what was charged.

Read the feed of alerts, acknowledge one, and write the rules that decide what Slen tells you about.

Connect the chats of your team, decide who hears about which alert or approval, and choose what reaches you yourself and when.

Add the API key of a provider as a connection, check that it works, and rotate, switch off or delete it later.

Group connections into a pool, choose how the pool picks a connection for a call and what it does when a provider refuses or fails.

See which models Slen can call, what a million tokens of each costs and how many tokens one answer may hold.

Issue a key for a service, choose what it may do, replace its secret and revoke it on the keys page of the console.

Invite a person to the organization, give them a role and the projects they reach, then change or end their access on the members page.

Add the address of your service, choose the events it hears, keep the signing secret, and switch a webhook off or delete it.

Read the audit log — which changes of settings it records, who may open it and how to find an entry.

The four tabs of the overview page — spend, accuracy of the estimates, models and providers — and the analytics of one flow.

The Operations screen of the console — the model calls of a project, the holds they took and the money movements of the ledger.