Skip to content
Merged
10 changes: 8 additions & 2 deletions docs/guides/frontends/service-discoverability.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,14 @@ When an agent working through ICP MCP is handed only your app's URL (for example

This guide describes what a canister app exposes to make that possible, ordered by priority.

:::caution[Adopting this protocol opts your app in]
Making an app available through [ICP MCP](https://internetcomputer.org/icp-mcp/) is governed by the [ICP MCP App Operator Terms](https://internetcomputer.org/icp-mcp/app-operator-terms/), an agreement between DFINITY and the app's operator: the person or entity legally authorized to operate the app and declare its canisters. The operator accepts the terms by registering, as their acceptance section describes, and what ICP MCP discloses to a participating app is described in its [privacy policy](https://internetcomputer.org/icp-mcp/privacy-policy/). Publishing the Layer 1 manifest at `/.well-known/ic-architecture` is the act that activates the app's participation (publishing without registering counts as accepting the terms by conduct): the layers are otherwise independently adoptable, and the rest of them describe how an agent works with an app once it has been discovered.
:::caution[Publishing the Layer 1 manifest opts your app in]
Making an app available through [ICP MCP](https://internetcomputer.org/icp-mcp/) is governed by the [ICP MCP App Operator Terms](https://internetcomputer.org/icp-mcp/app-operator-terms/), an agreement between DFINITY and the app's operator: the person or entity legally authorized to operate the app and declare its canisters.

**Publishing the Layer 1 manifest at `/.well-known/ic-architecture` opts the app into ICP MCP and constitutes the operator's acceptance of those terms**. It is sufficient to make its declared canisters eligible for state-changing calls from users who authorized actions; no separate registration is required. Publishing the manifest is the additional condition ICP MCP applies to state-changing calls. It does not require manifest publication for metadata retrieval or query calls.

**Registration is optional** and is not a condition of participation. It is how an operator tells DFINITY who they are, so they can be reached with the notices the terms provide for, and so there is a record of who accepted and which version; it can include the URL of the app's own privacy policy, so ICP MCP can present it to users. What ICP MCP discloses to a participating app, and what it processes if an operator registers, are described in the [ICP MCP Privacy Policy](https://internetcomputer.org/icp-mcp/privacy-policy/); under the App Operator Terms the operator remains responsible for handling the personal data that reaches the app lawfully, and for keeping the app's own privacy notice accurate and available to its users.

The layers below are otherwise independently adoptable, and the rest of them describe how an agent works with an app once it has been discovered.
Comment thread
aterga marked this conversation as resolved.
Outdated
:::

## The five layers
Expand Down
Loading