OpenAPI Import

OpenAPI import turns supported operations from an existing API spec into editable workspace files. You can import by:

• pasting an OpenAPI JSON or YAML document
• pasting a public spec URL
• asking the Assistant to look for API docs based on your provider domain

​

Supported operations

Agent Wonderland currently imports: Unsupported operations are reported as diagnostics instead of becoming editable endpoint files.

​

Supported auth

The MVP auth modes are:

• no auth
• bearer token
• one custom header API key

When auth is needed, the workspace stores a secretRef in auth.yaml. Paste the actual secret only into the secure secret field in the Assistant or auth flow.

​

Import results

After import, the workspace usually contains:

• api.yaml
• auth.yaml
• pricing.yaml
• distribution.yaml
• endpoint YAML files
• test JSON stubs
• unsupported operation diagnostics, when needed

Imported endpoints default to active: false. This keeps large imports safe: you can review, filter, search, and activate only the endpoints you want to publish.

​

Large specs

Large specs can create dozens or hundreds of endpoint files. Use Endpoints to filter and search across them, and use Files when you want direct YAML control. The Assistant summarizes large imports with:

• API count
• drafted endpoint count
• unsupported operation count
• auth requirements
• pricing defaults
• activation status

​

Common reasons an operation is not imported

• unsupported HTTP method
• unsupported request body media type
• multipart or file upload input
• complex auth scheme outside the MVP modes
• ambiguous server URL
• parameter style the importer cannot safely mirror

You can still create a manual endpoint for an operation that cannot be imported automatically, as long as the runtime endpoint can be represented with supported JSON inputs.