Which Exchange asset type represents a complete API specification in RAML or OAS format?

In Anypoint Exchange, the "REST API" asset type is used to publish a complete API specification. This specification serves as the contract for the API and is defined using standard languages like the RESTful API Modeling Language (RAML) or the OpenAPI Specification (OAS). Publishing a REST API asset to Exchange makes the API's design discoverable, reusable, and available for feedback, mocking, and implementation by developers.

A. SOAP APIs: This asset type represents an API specification defined using WSDL (Web Services Description Language), not RAML or OAS.

B. API Spec Fragments: These are reusable, partial components of an API specification, such as data types or security schemes, not the complete specification itself.

D. Connectors: These are pre-built Mule components that provide connectivity to external systems. They are implementation assets, not API design specifications.

1. MuleSoft Official Documentation, "Asset Types":

Section: Asset Types > REST API

Content: "A RESTful API specification, written in RAML or OAS." This directly confirms that the "REST API" asset type is for complete specifications in these formats.

Section: Asset Types > API fragment

Content: "A reusable component of an API specification, such as a data type or a security scheme." This confirms fragments are not complete specifications.

2. MuleSoft Official Documentation, "About Exchange":

Section: What Can I Do in Exchange? > Discover and Use Prebuilt Assets

Content: The documentation describes how Exchange is a catalog for various assets, including "API specifications (REST and SOAP)". It distinguishes between REST APIs (defined by RAML/OAS) and other asset types like connectors and fragments.