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
Category1 skill1 official

Gateway

Call it correctly; read it when it refuses.

Officialv1.0.0MIT169 lines

Debug a Gateway 400, 402 or 429

lobstack-gateway-errors

Diagnose a Lobstack Gateway failure from its status and error class and decide whether retrying can possibly help. Use when a call returns 400, 401, 402, 403, 429 or 5xx, when a stream ends in an error frame, or when someone reports that the Gateway is broken.

#gateway#errors#retries#debugging
Read SKILL.md
Other categories
Cost4

Know what a call cost, and stay inside a budget.

Migration2

Get existing code and tools onto one endpoint.

Observability2

Read back what actually happened.

Authoring1

Write skills, and know when not to.

← Back to the archive