> For the complete documentation index, see [llms.txt](https://bluprynt.gitbook.io/bluprynt-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluprynt.gitbook.io/bluprynt-docs/overview/core-products.md).

# Core Products

## Core Products

Bluprynt is the Compliance OS of digital assets.

It combines issuer identity, disclosure infrastructure, supervisory workflows, and verifiable credentials in one operating environment.

***

## KYI (Know Your Issuer)

[KYI](/bluprynt-docs/kyi-know-your-issuer/what-is-kyi.md) verifies that a token is tied to a real legal entity and a verified controlling wallet.

It helps platforms answer two critical questions:

* Who stands behind this asset?
* Does that entity control the wallet with mint or admin authority?

The KYI workflow includes:

* Business verification and KYB review
* Wallet signature verification
* Onchain attestation linking entity, wallet, and token

Partners can integrate KYI through the [KYI API](/bluprynt-docs/kyi-know-your-issuer/kyi-api.md) or embed the flow directly with the [KYI Widget SDK](/bluprynt-docs/kyi-know-your-issuer/kyi-widget-sdk.md).

KYI reduces impersonation risk, supports exchange due diligence, and gives wallets, explorers, and compliance teams a reliable token provenance signal.

<figure><img src="https://4243707769-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVuK5hWylXwNc0qjldsRZ%2Fuploads%2FVJ8a8aHMVRngjp4cCqsK%2FScreenshot%202025-07-15%20at%202.13.07%E2%80%AFPM.png?alt=media&amp;token=cca9d703-b7a3-42f1-999e-b6ee0cc5f89a" alt=""><figcaption></figcaption></figure>

***

## Smart Disclosures

[Smart Disclosures](/bluprynt-docs/smart-disclosures/what-is-smart-disclosures.md) is Bluprynt's AI-assisted disclosure engine for tokenized assets.

Teams can upload existing documents, auto-fill structured disclosure forms, and generate regulator-ready outputs in multiple formats.

Key capabilities include:

* AI extraction from white papers, terms, and supporting files
* Guided composition with jurisdiction-specific requirements
* Real-time feedback on missing or weak disclosure content
* Final outputs in XBRL, PDF, and DOCX
* Onchain publication of disclosure attestations

Smart Disclosures is built for token issuers that need to prepare filings faster without sacrificing structure, traceability, or review quality.

<figure><img src="https://4243707769-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVuK5hWylXwNc0qjldsRZ%2Fuploads%2FsiefYErKgDqv3LMd8YyP%2FScreenshot%202025-07-15%20at%202.12.50%E2%80%AFPM.png?alt=media&amp;token=33ed025f-392d-4ccd-a472-aa4d9aa4810b" alt=""><figcaption></figcaption></figure>

***

## MiCA Checker

[MiCA Checker](/bluprynt-docs/mica-checker/mica-checker.md) is Bluprynt's free diagnostic tool for EU crypto-asset white paper compliance.

It lets teams upload a draft white paper and quickly assess alignment with MiCA Articles 4 and 5.

It is designed for:

* Founders preparing a launch
* Legal teams reviewing disclosure completeness
* Exchanges pre-screening listing candidates
* Regulators and analysts running quick document checks

MiCA Checker is the fastest way to identify disclosure gaps before moving into full drafting or submission workflows. Teams that need remediation can move from MiCA Checker into Smart Disclosures.

***

## Compliance Hub

[Compliance Hub](/bluprynt-docs/compliance-hub/compliance-hub-coming-soon.md) is Bluprynt's regulator-facing supervisory workspace.

It is the operational center for form publishing, submission review, credential issuance, and ongoing supervision.

Core workflows include:

* Reviewing disclosure submissions
* Managing license application pipelines
* Requesting clarification from applicants
* Approving or rejecting submissions
* Directly issuing credentials
* Monitoring issuer and asset activity

Together, Smart Disclosures and Compliance Hub create a full issuer-to-regulator operating loop. Issuers submit structured data. Supervisors review, decide, and issue verifiable outcomes.

***

## Credentials and Attestations

Bluprynt’s products produce machine-readable trust signals that can be consumed by platforms, supervisors, and connected systems.

These include:

* **KYI attestations** that link an asset to a verified issuer and wallet
* **Disclosure attestations** that prove a document was completed and published
* **Credentials** that show whether an issuer, asset, or wallet satisfies a required condition

For example, the [Proof of Collateral Credential](/bluprynt-docs/credentials/proof-of-collateral.md) gives platforms and counterparties a verifiable signal that an asset is backed by underlying reserves.

These records make issuer status and asset compliance easier to verify across wallets, exchanges, tokenization platforms, and regulatory systems.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://bluprynt.gitbook.io/bluprynt-docs/overview/core-products.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.