Make inference requests on your agents.
blaxel.toml
file.
blaxel.toml reference
type
so Blaxel knows which kind of entity to deploy. Others are not mandatory but allow you to customize the deployment.name
, workspace
, and type
fields are optional and serve as default values. Any bl command run in the folder will use these defaults rather than prompting you for input.agents
, functions
, and models
fields are also optional. They specify which resources to deploy with the agent. These resources are preloaded during build, eliminating runtime dependencies on the Blaxel control plane and dramatically improving performance.[env]
section defines environment variables that the agent can access via the SDK. Note that these are NOT secrets.[runtime]
section allows to override agent deployment parameters: timeout (in s) or memory (in MB) to allocate.[[triggers]]
and [triggers.configuration]
sections defines ways to send requests to the agent. You can create both synchronous and asynchronous trigger endpoints. You can also make them either private (default) or public.
A private synchronous HTTP endpoint is always created by default, even if you don’t define any trigger here.Thread-Id
). Without a thread ID, the agent won’t maintain nor use any conversation memory when processing the request.
blaxel.toml
configuration file, as explained above: