English · Deutsch
Try one concrete use case: stop a tool loop
Problem: An agent keeps retrying connected tool calls. TollGate can stop calls routed through its configured gateway; it cannot stop arbitrary terminal processes or guarantee your provider invoice.
Source-only Protect demo (Python 3.11+, use permitted under LICENSE):
git clone https://github.com/landjunge/tollgate.git && cd tollgate
python3 -m venv .venv && .venv/bin/pip install -e .
./scripts/ten-minute.sh
You should see a blocked tool loop and a scorecard; the local dashboard is at http://127.0.0.1:8787/dashboard. No provider API key is required for this demo. Detailed quickstart · Product limits. No desktop installer is published.
The tool family and its limits
KiraBridge is the central voice and computer-control path for the NetzwerkPunkt tool family. With the right permissions it can open applications, change windows, write notes, enter text directly and use keyboard shortcuts. TollGate serves a different purpose: it helps apply safety and budget limits so that a convenient spoken request does not lead to uncontrolled retries, hidden usage or unexpected costs.
The family includes KiraBridge for connectivity and direct computer control, ThreadDesk for projects and work history, 4AllPass for credentials and keys, TollGate for usage limits and budgets, and Agent Authority for read-only observation and evidence. Each tool remains independent. Seamless control of the whole family through natural language is a development goal; individual integrations must be verified rather than assumed.
Understanding usage and limits in voice workflows
Natural-language control of computers and AI tools for everyone is the overarching goal of the NetzwerkPunkt family. KiraBridge relays requests while TollGate is intended to make usage, warnings, budget limits and stops understandable for connected calls. Even a simple spoken request must remain controllable.
Accessibility is intentionally considered as an additional benefit, not the primary purpose or an exclusive audience. Understandable feedback can particularly help people with disabilities or reduced mobility, but it also benefits anyone working by voice or without complex interfaces. Spoken commands never bypass access checks or human decisions about consequential costs and actions.
Development status: TollGate should not be mistaken for a finished cross-provider usage-monitoring system. Plan rules, reset times and access to usage data require separate verification for each provider and product. For Grok Team, individual weekly seat allowances and shared team add-on credits must be modeled separately. xAI API usage endpoints do not establish that the same data is available for Grok subscriptions. We continue improving reliability and visibility without presenting unverified data as live.
TollGate checks connected model and tool calls before they execute. It helps stop repeated calls, limit usage and explain decisions.
Source version: 1.0.12 · In development · Python 3.11 or newer
Quick start from source · View source
There is no published desktop installer. The announcement release has no packaged downloads. Private use is free under the license; business use needs written permission.
What TollGate helps you do
- Protect: usage limits, loop protection, rules for permitted access and a freeze for new calls.
- Route: health-aware routing and failover to configured providers.
- Prove: outage and recovery simulations with reports about the tested setup.
- Connections: an OpenAI-compatible gateway, MCP and n8n; English and German controls.
The local workflow-control core adds durable reservations and stops for explicitly connected adapters. Structured agent events are attributed idempotently on top of that budget and replay journal by job, session and event: a workflow task id is not a provider session id, and an unknown or stopped outcome blocks further dispatch instead of replaying it. This is local event attribution, not a live provider or a universal cost cap. Acceptance with synthetic adapters is separate from configured production use with KiraBridge or 4AllPass. Cost estimates are not provider invoices and do not guarantee a spending cap for arbitrary terminal agents. A runnable demo exercises this guard lifecycle with synthetic effects and no keys: workflow guard example. Workflow state can also be read back read-only — no reservation, dispatch, settle or stop — via the workflow observation projection; it reports only allowlisted fields and never grants a budget. Budget incident values are exported only as strict booleans; other types become null (unknown) without changing the journal.
Boundary: Freeze blocks new connected calls. It does not terminate arbitrary processes or undo effects already sent. Workflow control · Process stops.
Get started
With permission to use the software and Python 3.11 or newer:
- Set up. Follow the quick start to install TollGate locally.
- Run the demo. Run the Protect demo from the quick start.
- Inspect the result. Open the local dashboard to see why TollGate allowed or blocked a call.
The Protect demo needs no provider keys. Then check the local dashboard to see why a call was allowed or blocked. Real model calls and routing require your own provider accounts. Quick start.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
