---
schema_version: "1"
id: 7760b8b274c5675aad936c565ff951e6792f7dfad86c9c5ef35529f3e04a9e2d
title: Configuring Instances
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/exchange/to-configure-api-settings.md
canonical_url: https://docs.mulesoft.com/exchange/to-configure-api-settings
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 7777495e6b4283d91bd8683c91f22e33ae132006bbd1ba6eda8e62f87758300e
description: MuleSoft Documentation Site
latest: true
---
---
product: Exchange
---

# Configuring Instances

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

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 in API Manager.

After you register an API or other assets from Exchange in API Manager, the instances for the asset
appear in Exchange in the **Instances** list on the asset details page.

You can also verify agent instances via GoDaddy Agent Naming Service (ANS) during the registration
process in API Manager. Implement GoDaddy’s trust layer to verify and secure trusted agents across
Anypoint Platform. Verified agents appear in the **Agents & Tools** list and on asset details pages
with a verified badge. Managed instances in Exchange show if an agent is verified 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 non-managed
instances that are serving AsyncAPIs, GraphQL APIs, REST APIs, HTTP APIs, agents, MCP servers, and
LLMs. Add these manually on the asset’s **Instances** page by providing a display name and base URL
so developers know where the API is hosted. You can change the name, URL, and visibility of
non-managed instances and services.

- Add a non-managed instance:

  1.  Select the asset.

  2.  In the navigation bar, select **Instances**.

  3.  Click **Add new instance**.

  4.  In the **Non-managed instances** section, enter the instance name and URL.

  5.  Select a visibility option and click ![The checkmark icon.](/mulesoft/current/en-us/exchange/_images/ex-checkmark-icon.png).

- Edit a non-managed instance:

  1.  Click ![The pencil icon](/mulesoft/current/en-us/exchange/_images/ex-pencil-icon.png).

  2.  Make your changes and click ![The checkmark icon](/mulesoft/current/en-us/exchange/_images/ex-checkmark-icon.png).

- Delete a non-managed instance by clicking ![The trash can icon.](/mulesoft/current/en-us/exchange/_images/ex-trash-can-icon.png)
  and then clicking **Delete instance**.

## See Also

- [Register Agents with GoDaddy ANS](https://docs.mulesoft.com/api-manager/latest/godaddy-ans-registration)

- [View Instances](https://docs.mulesoft.com/exchange/asset-details#view-instances)

- [Simulate Calls to an API](https://docs.mulesoft.com/design-center/design-mocking-service)