> For the complete documentation index, see [llms.txt](https://docs.sendme.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sendme.network/protocol-overview/participants-and-roles/individual.md).

# Individual

### Overview

Individuals or natural persons who participate in the **sendme** Protocol represent the targeted audience of the system. From their perspective, the system represents a one-stop shop that addresses their needs in a range from a simple DC transfer to a major investment into a campaign. 

Individuals may possess various Properties unlocking system functionalities within **sendme**. For instance, obtaining the ability to make peer-to-peer (P2P) transactions after going through KYC procedure or unlock investment opportunities passing qualified or accredited investor verifications. 

This section delves into their role and capabilities.

### Function

* Transactions Initiation:
  * Make P2P transactions with other Individuals in the system using DC.
  * Make transactions with Merchants and Entities who accept the DC.

### Relationship with Compliance Processor

Each transaction that involves (CB)DC, which an Individual makes, is enforced by the [Compliance Processor](/protocol-overview/compliance-processor.md) to ensure adherence to system rules and attached policies.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.sendme.network/protocol-overview/participants-and-roles/individual.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.