AI Systems

Agent Kill Switch

The time to build the stop button is before you need it.

The stop that stops the agent but not the queue behind it.

What you get

6 things inside

A halt that every worker checks
A soft stop and a hard stop
Access you can revoke in one step
What to check once everything is quiet
A check you can run to prove the stop works
One page you fill in for your own setup

Buy · Free

How it is written

Every chapter opens with how it breaks and ends with the one decision that stays with a person.

Who it is for

Anyone who runs an agent that acts on real systems.

Format

A free PDF guide of 29 pages, 6 by 9 inches. Licensed for personal use. The file is protected: copying, editing and printing are restricted.

Stellarwind AI publishes how real AI systems are built, set up and run.

Keep exploring

AI Systems
MCP Server With OAuth 2.1
Your MCP server works when you try it once. Here is what it does in real use. One shared key in every client configuration cannot be revoked, cannot be attributed and never expires. What you get A credential ledger you can switch off, one client at a time OAuth 2.1 with PKCE and refresh rotation, built on RFC 7636 and RFC 7009 Self registering clients that still need a human to approve them Tokens bound to the one server they were issued for A stateless Streamable HTTP transport and a tool structure that scales The runbook for the day a token outlives its client How it is written Every chapter opens with how it breaks and ends with the one decision that stays with a person. Who it is for Builders who run an MCP server in real use, or are about to. Format A PDF e-book of 71 pages, 6 by 9 inches. Licensed for personal use. The file is protected: copying, editing and printing are restricted. Stellarwind AI publishes how real AI systems are built, set up and run.
Value$97
AI Systems
MCP Tool Design And One Registry
A tool an LLM cannot read is a tool it will misuse. The model sees only what you wrote: a name, a description and a schema. Everything else it guesses. What you get Three rules that make a tool description something a model can act on A ban list for vague verbs, and a policy of no delete tools One registry that declares each operation once and derives REST, OpenAPI, MCP and CLI Parity tests that prove the four never disagree The runbook for the day a tool is called wrongly How it is written Every chapter opens with how it breaks and ends with the one decision that stays with a person. Who it is for Builders who expose tools to a model and want fewer wrong calls. Format A PDF e-book of 49 pages, 6 by 9 inches. Licensed for personal use. The file is protected: copying, editing and printing are restricted. Stellarwind AI publishes how real AI systems are built, set up and run.
Value$47
AI Systems
Agent Orchestration With Deterministic Guardrails
Let the model interpret. Never let it decide alone. An agent system fails in four ordinary ways: a run resumes twice, an approval nobody sees expires, a model call is submitted again after a timeout, and an agent finds a second door around the check. What you get A typed split between what the model interprets and what code decides Leases and atomic checkpoints for runs that can crash Approvals bound to the exact thing that was reviewed A gate that turns intent into action, with no second door Receipts for every provider call, and replay from what the provider actually said A safe way to drive local AI command line tools as engines How it is written Every chapter opens with how it breaks and ends with the one decision that stays with a person. Who it is for Builders who run agents that act on real systems. Format A PDF e-book of 66 pages, 6 by 9 inches. Licensed for personal use. The file is protected: copying, editing and printing are restricted. Stellarwind AI publishes how real AI systems are built, set up and run.
Value$147