TypedBots.dev — Typed Agent Contract Schemas
Typed bots fail closed: every tool call is validated against a JSON Schema contract before execution. This page defines the contract format and includes a live validator so you can prove a call passes or fails before it ever reaches a runtime.
Typed Agent Contract Validator (JSON Schema)
Paste a JSON Schema for a tool call and a sample call payload. The validator enforces types, required fields, enums and additionalProperties — the typed-bots contract gate.
Paste schema + call and press Validate.
Contract rules
typemust be declared and enforced — string, number, integer, boolean, array, object, null.requiredlists keys that must be present; missing keys are violations.enumpins allowed values;minimum/maximum/minLengthbound scalars.additionalProperties:falseis the typed-bots default — undeclared keys are drift and fail.itemsrecurses into arrays; nestedpropertiesrecurse into objects.
Why typed contracts
Untyped agent I/O is where hallucinated fields, silent coercion and prompt-injected extras enter a pipeline. A schema contract makes the tool boundary a type boundary: the runtime can reject malformed calls deterministically instead of trusting model output.
Cluster
Sibling properties in the MCP/A2A protocol bridge and guardrail runtimes.
MCP Context ProMCP↔A2A HubA2A→MCP CompilerOverwatcherTypedBotsStrictBotsRunWeights · ForwardRouterReverseHarnessLinkProducers