Configuring Instances
Use Anypoint Exchange to configure whether instances are public or private in a private Exchange instance or in an Exchange public portal. For example, configure public or private visibility for proxies or policies associated with your asset and set using API Manager.
After you register an API from Exchange in API Manager, the instances for the asset appear in Exchange in the Instances list on the asset details page.
Instances for brokers are created in the YAML in Anypoint Code Builder. After the agent network project is published to Exchange, the instances appear in the Instances list.
Exchange also declares instances for assets managed by other asset management programs besides Anypoint Platform.
Visibility for each instance is either private or public. Users can see a private instance if the asset is shared with them or if they have an Anypoint Platform permission that grants access. All users accessing an Exchange public portal can see all public instances. All instances in an Exchange public portal are read only.
In a private Exchange instance, asset administrators have access to change the visibility of instances, and to add, edit, and delete instances.
REST APIs provide a mocking service with data to test API features. The mocking service is always public.
Configure Non-Managed Instances
Configure assets with instances not managed by API Manager. Add, edit, and delete nonmanaged instances that are serving AsyncAPIs, GraphQL, REST, HTTP APIs, agents, MCPs, and LLMs. You can change the name, URL, and visibility of nonmanaged instances and services.
-
Add a non-managed instance:
-
Select the asset.
-
In the navigation bar, select Instances.
-
Click Add new instance.
-
In the Non-managed instances section, enter the instance name, URL, select a visibility option, and click
.
-
-
Edit a non-managed instance:
-
Click
. -
Make your changes and click
.
-
-
Delete a non-managed instance by clicking
and clicking Delete instance.