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
Category2 skills2 official

Migration

Get existing code and tools onto one endpoint.

Officialv1.0.0MIT134 lines

Migrate an SDK call to the Gateway

lobstack-gateway-migration

Move existing OpenAI or Anthropic SDK code onto the Lobstack Gateway by changing the base URL and the key, and verify it actually routed. Use when asked to put an app behind Lobstack, consolidate providers behind one endpoint, or add per-call cost data to code that already calls a model API.

#migration#openai#anthropic#sdk#gateway
Read SKILL.md
Officialv1.0.0MIT105 lines

Put Cursor or Aider behind the Gateway

lobstack-local-proxy

Route Cursor, Aider, Continue or any OpenAI-compatible tool through the Lobstack Gateway with a local proxy, and see a cost line per request. Use when asked to route an editor or coding CLI through Lobstack, to find what an AI coding tool is costing, or to use one key across several tools.

#migration#cli#proxy#tools
Read SKILL.md
Other categories
Cost4

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

Gateway1

Call it correctly; read it when it refuses.

Observability2

Read back what actually happened.

Authoring1

Write skills, and know when not to.

← Back to the archive