> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/components/certificates.md).

# Certificates

Certificates on the network can be attached to [accounts](/components/accounts.md) to serve as digital credentials that validate the identity, qualifications, and capabilities of participants within the system. These certificates are fundamental to establishing trust and enabling secure interactions between various parties on the network.

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

### Scope & Flexibility

At their core, Keeta certificates are structured pieces of information that can represent a wide range of attributes. These may include Know Your Customer (KYC) verifications, business licenses, regulatory compliance certifications, and other important qualifications.

The flexibility of the certificate system allows for the representation of virtually any relevant attribute that may be required for network operations.

### Dynamic Nature

One of the key features of certificates on the Keeta Network is their dynamic nature. Unlike traditional static credentials, these certificates can be updated and modified over time through [Keeta's Dynamic Rule Engine](/features/native-tokenization/built-in-rules-engine.md). This adaptability ensures that the information remains current and relevant, reflecting any changes in a participant's status or qualifications.

### Compliance & Security

Certificates play a crucial role in the network's compliance and security framework. They not only validate the legitimacy of participants but also define their capabilities within the system.

For example, a certificate might specify transaction limits, access rights, or the types of operations a participant is authorized to perform. This certificate-based approach to identity and permissions management helps streamline processes, and reduce verification overhead.


---

# 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.keeta.com/components/certificates.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.