# Roles and Responsibilities

Unlike the vault layer, which separates concerns across curator, admin, valuation provider, and whitelist manager, the ramp layer has a simpler trust model. The key roles are:

<table><thead><tr><th width="178.8125">Role</th><th width="180.1953125">Scope</th><th>Description</th></tr></thead><tbody><tr><td>Backend Operator</td><td>Credential Holder</td><td>Holds the MCE client ID and secret. Responsible for ensuring credentials are stored securely and never leaked to the frontend. All ramp calls originate from this role.</td></tr><tr><td>Participant</td><td>Account Identity</td><td>Identified by a <code>participantCode</code> within MCE. Each participant has their own deposit addresses, balances, and transaction history. A single backend operator may manage multiple participants.</td></tr><tr><td>Beneficiary</td><td>Off-Ramp Recipient</td><td>The external party receiving funds on a withdrawal. Their banking details are submitted as part of the withdrawal request and must be accurate for settlement to succeed.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://city-protocol.gitbook.io/docs/neofinance-as-a-service/on-off-ramp-module/roles-and-responsibilities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.