> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-docs/user-guide/resolution-6/peer-components.md).

# Peer components

The architecture of a All.id peer consists in the componenents presented bellow, also represented in the following diagram.

<figure><img src="/files/ceiE1VPD7ao1fnQcJZtu" alt=""><figcaption></figcaption></figure>

### Peer node

The peer node is responsible for communication between the All.id network and the internal peer components. It functions as a gateway to the peer, and is the only externally acessible component. It is responsible for communicating with the database, connecting with the router, dealing with network requests and responsed for biometric validations. It exposes ports for internal communication inside the client infrastructure, as well as ports for external communication with the All.id network.

### Facematch

The facematch component represent the core functionality of the All.id solution, being responsible for generating face embeddings (vectorial representations of a face), which is the main data used by the network, stored only in the peer database. It's also responsible for comparing embeddings to check if two faces match and correspond to the same person. It was developed by the All.id biometrics team as proprietary tech, being a AI algorithm.

### REST API

The REST API acts as a gateway to internal access for the peer node, exposing a API for integration between the client pipeline and the All.id network. This component has routes to insert new biometric assets in he peer, querying the network for biometric validations, generating usage reports, among other operations.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.caf.io/caf-docs/user-guide/resolution-6/peer-components.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.