Inference API

Whenever you deploy a workload on Blaxel, an inference endpoint is generated on Global Agentics Network, the infrastructure powerhouse that hosts it. The inference API URL depends on the type of workload (sandbox, agent, model API, MCP server) you are interacting with:


https://sbx-{YOUR-SANDBOX}-{YOUR-WORKSPACE}.{REGION}.bl.run/mcp

Showing the full request, with the input payload:

Query sandbox
Query agent
Query model API (example on a chat completion model)
Execute a job

curl -X GET "https://sbx-{your-sandbox}-{your-workspace}.{region}.bl.run/filesystem/tree/etc" \
-H "Content-Type: application/json" \
-H "X-Blaxel-Authorization: Bearer <YOUR_API_KEY>"

If you have the Blaxel CLI bl installed, you can use it to directly interpolate your API key into the HTTP request, as shown below:

curl -X GET "https://sbx-{your-sandbox}-$(bl workspace --current).{region}.bl.run/filesystem/tree/etc" \
-H "Content-Type: application/json" \
-H "X-Blaxel-Authorization: Bearer $(bl token)"

curl -X POST "https://run.blaxel.ai/{your-workspace}/agents/{your-agent}" \
-H "Content-Type: application/json" \
-H "X-Blaxel-Authorization: Bearer <YOUR_API_KEY>" \
-d '{"inputs":"Hello, world!"}'

If you have the Blaxel CLI bl installed, you can use it to directly interpolate your API key into the HTTP request, as shown below:

curl -X POST "https://run.blaxel.ai/$(bl workspace --current)/agents/{your-agent}" \
-H "Content-Type: application/json" \
-H "X-Blaxel-Authorization: Bearer $(bl token)" \
-d '{"inputs":"Hello, world!"}'

curl -X POST "https://run.blaxel.ai/{your-workspace}/models/{your-model}/chat/completions" \
-H "Content-Type: application/json" \
-H "X-Blaxel-Authorization: Bearer <YOUR_API_KEY>" \
-d '{"messages":[{"role":"user","content":"Hello!"}]}'

If you have the Blaxel CLI bl installed, you can use it to directly interpolate your API key into the HTTP request, as shown below:

curl -X POST "https://run.blaxel.ai/$(bl workspace --current)/models/{your-model}/chat/completions" \
-H "Content-Type: application/json" \
-H "X-Blaxel-Authorization: Bearer $(bl token)" \
-d '{"messages":[{"role":"user","content":"Hello!"}]}'

curl -X POST "https://api.blaxel.ai/{your-workspace}/jobs/{your-job-name}/executions" \
-H "X-Blaxel-Authorization: Bearer <YOUR_API_KEY>" \
-d '{"tasks":[{"my_arg":"my_value"}]}'

If you have the Blaxel CLI bl installed, you can use it to directly interpolate your API key into the HTTP request, as shown below:

curl -X POST "https://api.blaxel.ai/$(bl workspace --current)/jobs/{your-job-name}/executions" \
-H "X-Blaxel-Authorization: Bearer $(bl token)" \
-d '{"tasks":[{"my_arg":"my_value"}]}'

Connect to MCP servers

MCP servers (Model Context Protocol) provide a toolkit of multiple capabilities for agents. These servers can be interacted with using Blaxel’s streamable HTTP transport implementation on the server’s global endpoint.

Connect to an MCP server

Learn how to run tool calls through your MCP server.

Manage sessions

To simulate multi-turn conversations, you can pass on request headers. You’ll need your client to generate this ID and pass it using any header which you can retrieve via the code (e.g. Thread-Id). Without a thread ID, the agent won’t maintain nor use any conversation memory when processing the request. This is only available for agent requests.

Query agent with thread ID

curl -X POST "https://run.blaxel.ai/{your-workspace}/agents/{your-agent}" \
-H 'Content-Type: application/json' \
-H "X-Blaxel-Authorization: Bearer <YOUR_API_KEY>" \
-H "X-Blaxel-Thread-Id: <THREAD_ID>" \
-d '{"inputs":"Hello, world!"}'

Product documentation

Read our product guide on querying an agent.

Overview

Billing API

Management API

Inference API

Connect to MCP servers

Connect to an MCP server

Manage sessions

Product documentation

Overview

Inference API

Billing API

Management API

Documentation Index

​Connect to MCP servers

Connect to an MCP server

​Manage sessions

Product documentation

Connect to MCP servers

Manage sessions