Guide 08 // Agent Preflight
Straight answers about what a controlled, read-only connection check can inspect—and what it deliberately cannot do.
It is a bounded, account-scoped, read-only way to check a declared proposed tool, API, webhook or workflow connection before action. It can identify issues such as missing required fields, incompatible formats, an output without a declared consumer, or an assumed adapter that is not present.
It does not change a workflow, configure a destination, sign policy, queue or execute work, activate a system, or make arbitrary network calls. A result is a redacted compatibility finding and a bounded next action for human review.
No. A compatible result is not permission, execution authority, deployment approval or a safety guarantee. Scope, destination and data-boundary decisions remain separate human responsibilities.
No. Do not use a public-safe pilot conversation or compatibility check for credentials, private keys, confidential payloads or production secrets.
No. Agent Preflight checks a proposed connection before action. Webhook Boundary is the separate Ingress Shield surface for protecting and observing declared webhook traffic on a reviewed route.
Approved clients can use a protected MCP interface for the bounded read-only tools. Exact live availability and argument schemas are discovered through approved onboarding and tools/list, not copied into a public page.
No. The pilot is controlled and reviewed; external pilot access is not yet available. It does not claim public self-service enrolment, general availability or a contractual uptime guarantee.
A person reviews the stated next action. Agent Preflight does not execute remediation or change the connected systems.
For a pilot or business conversation, describe the proposed connection, intended use and expected volume without sending credentials, personal data or confidential payloads. The appropriate secure route can be agreed separately.
