Documentation

Everything the gateway exposes, in one place.

looot exposes exactly six MCP tools, a CLI that mirrors them one for one, and a REST API underneath both. This page is the map, not the manual.

For humansFor agents
Open the setup center Start onboarding

The MCP surface

Six tools, no more.

Every client, human or agent, reaches the gateway through the same six operations. Nothing else is exposed.

discover
Search the catalog for operations that match what you're trying to do.
inspect
Look up one operation's contract: inputs, outputs, and price basis.
run
Execute an operation with an idempotency key and get back a run record.
runs_get
Fetch a single run by id, including its current status and result.
runs_list
List runs for the organization, filterable by status or capability.
balance
Check the organization's current reservation and settlement balance.

How you connect

Three surfaces, one contract.

CLI, REST, and MCP all call the same operations underneath, so nothing behaves differently depending on how you connect.

CLI
A command-line client that calls the same operations as the tools above.

Commands follow one shape: coset <group> <action> [id] [options].

Covers discovery and running operations (discover, run), run history (runs list, runs get), balance, catalog browsing, and connection management. Output defaults to JSON; human-readable output redacts secret-looking fields.

Secrets and capability tokens are read from environment variables only, never accepted as command arguments.

REST API
The HTTP surface the CLI and MCP server both call underneath.

The full contract is served live at /v1/openapi.json — every route, request shape, and response shape, generated from the same code that runs the gateway.

Every operation is versioned (ContractVersion), so a contract change never silently breaks a caller pinned to an older version.

MCP
Connect any MCP-compatible client directly to the gateway.

The same six tools (discover, inspect, run, runs_get, runs_list, balance) are exposed over MCP, so an AI client can browse the catalog and execute operations without a separate integration layer.

Organization isolation and fail-closed production connections apply the same way regardless of which surface a call comes through.

Next step

Setting up a real connection.

Every required account, environment variable, and scope
Without ever printing a secret.
Go to the setup center

Your workspace needs no account or provider key to start and uses example data. Production connections remain fail-closed until configured and approved.