---
title: Probe
url: https://pr-4-390be2854416.thally.app/commands/probe
---

# Probe

The `schemaport probe` command sends a compiled tool definition to a provider API to determine whether the provider accepts the definition. The command returns one of four verdicts: accepted, rejected, error, or skipped. The accepted verdict indicates that the provider accepted the compiled definition. The rejected verdict indicates that the provider rejected the schema. The error verdict indicates that no verdict was reached, and the skipped verdict indicates that probing does not apply to the target provider. The command requires credentials for each target provider and makes a network request to the provider API. The `--targets` flag specifies which providers to probe, and the `--format` flag specifies the output format as either text or JSON. The `--model` flag specifies the model to use for probing, and the `--allow-lossy` flag allows lossy transformations during compilation. The command exits with a code of 0 if nothing is rejected or errored, 1 if a provider rejects a schema or a compilation is refused, and 3 if no rejection or refused compilation occurs but at least one probe reaches no verdict.
<!-- thally-cite:v1:685c94637d330605c62c56c1c1efaf29d55f3958a8ab269a3a3ca1cc1100be2e -->
<!-- thally-cite:v1:57e489e3844c65143f4eefcc2b97b427637e595292359e58f772eced6ed7d05a -->

- [MCP](/providers/mcp) — local validation instead of probing
- [Exit codes](/reference/exit-codes) — the `1` versus `3` distinction in full
- [Diff](/commands/diff) — did this release break any callers?