Sample audit

Preview the paid readiness report.

This illustrative sample shows the decision support an API team receives before turning an OpenAPI surface into MCP tools, coding-agent functions, or internal automation actions.

$249 founding review 1 API surface reviewed No secrets required

Request this audit Inspect API output

Example findings

What blocks agent launch.

Ambiguous write operations: three mutation endpoints need approval copy before agent exposure.
Weak response examples: two endpoints return objects without examples that help an agent choose the next step.
Auth scope mismatch: the docs describe broad account access where workflow-scoped tokens would be safer.
Missing dry-run mode: destructive actions need a preview response before an agent can propose execution.

Recommended first workflow

Ship a narrow toolset first.

Expose read-only lookup, draft creation, and validation tools before publishing irreversible actions. Keep account deletion, billing changes, and broad exports behind manual review until approval language is tested.

Scope my API Read market notes

Risk map

Example approval policy notes

Operation type	Agent exposure	Launch note
Read-only lookup	Allow with normal user confirmation	Keep response examples and pagination notes in the tool description.
Draft write	Allow with explicit approval	Return a draft identifier and require a separate publish action.
Destructive action	Hold for manual review	Add dry-run output, recovery notes, and a named human approval policy.

Input needed

Start with docs, not credentials.

Send an OpenAPI file, public docs URL, endpoint list, or sanitized workflow description. Production keys and live customer data are not needed for the readiness audit.

Next paid step

Use the audit to decide whether a launch pack is worth it.

If the findings justify implementation, the MCP Launch Pack turns selected workflows into toolsets, install snippets, docs copy, and approval-language drafts.