Which key capability is not typically associated with REST APIs?

Utilizing WSDL (Web Services Description Language) for definitions is indeed not typically associated with REST APIs. REST, which stands for Representational State Transfer, is a standard architectural style that primarily uses HTTP for communication and operates on a request-response model without the need for a formal service contract like WSDL.

REST APIs are designed around resources, which are identified by URIs, and the interactions are generally performed using standard HTTP methods such as GET, POST, PUT, and DELETE. Unlike SOAP (Simple Object Access Protocol) services, which leverage WSDL to define service operations and data types in a formal, machine-readable way, REST relies on conventions and can return data in various formats, including JSON and XML, without necessitating a formal contract.

The other capabilities listed are integral to REST APIs. Exposing metadata to Anypoint Studio enables users to visualize and interact with API features, while providing endpoints for HTTP requests is a fundamental characteristic of RESTful services that allows clients to perform operations on resources. Supporting stateless communication means that each request from a client contains all the information needed to process the request, aligning with REST principles of simplicity and scalability.