Skip to content
Lobstack
GatewayOne endpoint, every model, a receipt on every callConsoleWatch what ran, what it cost, and what it would have costLob BotAgents on your own machine, with a gate before anything changesNexOur own model, learning where every request is worth sending
The Gateway routing a request and returning its cost
API OverviewThe endpoint and its shapeModelsEvery model, and its rateMCP serverThe Gateway inside your editorConsoleReading your own trafficPricingRates, per model
DocumentationEverything, by sectionCompareAgainst the alternativesAgent SkillsSKILL.md files, MITConnectorsBuilt in, plus any MCP serverStatusMeasured from real trafficGitHubThe source
AboutWhat we are building, and whyEnterpriseSSO, invoicing, an SLANewsWhat changed, and whenX / TwitterLinkedInContacthello@lobstack.ai
Start free
Lobstack Console

Know what your API is doing.

Every request through the Gateway, traced: what was asked, what served it, how long it took, what it cost, and — when it failed — why.

Run the first call →Log in
The Lobstack Console — Overview. What the runtime is doing right now.The Lobstack Console — API. Every request that reached the API, and what failed.The Lobstack Console — Usage. Spend by model and provider, priced when it was spent.The Lobstack Console — Logs. Every Gateway request, expandable to its full receipt.The Lobstack Console — Models. What auto can reach on your plan, and the rate for each.The Lobstack Console — API Keys. Mint, scope and rotate. The secret is shown once.
What the runtime is doing right now.What the runtime is doing right now.Sample data, not an account.
01

Requests

Every call that reached the API, including the ones that failed before a token existed. Counts, error rate, true p50, p95 and p99 latency, and cost — over time, by model, or by key.

02

Failures

Errors are classified, not listed. Auth, quota, validation, provider, timeout, internal — each with whose problem it is. A provider outage and a malformed request need different people.

03

Cost

Priced when the request ran and frozen, so a later change to a model price never moves a historical figure. Managed and bring-your-own-key spend are counted apart, because only one of them is yours.

Why it exists

An API you cannot observe is a liability. Every request carries an id you can quote; every failure carries a class that says whose problem it is; every dollar was priced when it was spent.

Run the first call →View pricing

The Console comes with every plan. Pair it with an API key and anything you build is on the same instruments.