api-spec-import

You can import API specs by providing a URL or local file path. The tool detects the format, registers the OpenAPI, gRPC, or GraphQL spec into the pinky-promise registry, and generates IDL JSON with bindings for contract validation.

Yes, you can import OpenAPI 3.x/2.x, gRPC proto, and GraphQL SDL specifications from either a local file or a URL. The Skill automatically detects and classifies the input format before converting it to IDL JSON.

Registering an external API spec derives a stable service identity and external version, creates or updates registry entries, converts the spec to pinky-promise IDL JSON, and generates a bindings file with security mappings for downstream contract checks.

Yes, the import process applies security mappings to the generated IDL bindings file. This enables downstream tooling, including mocks and contract tests, to properly authenticate and validate consumer code against the external API.

Importing external API specs declares them as a dependency in the registry so api-contract-check can validate consumer code against the external API. Without importing, the registry lacks the IDL contract needed to verify consumer interactions.

The best way is to import the gRPC proto file into the pinky-promise registry using the API spec importer. This registers the service identity, generates IDL JSON, and enables contract checks to validate your consumer code automatically.