> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/1kosmos-as-a-credential-service-provider-csp.md).

# 1Kosmos as a Credential Service Provider (CSP)

How 1Kosmos performs identity proofing as a Credential Service Provider (CSP), aligned with NIST SP 800-63A enrollment and identity proofing requirements.

***

### Overview

NIST Special Publication [800-63A Enrollment and Identity Proofing](https://pages.nist.gov/800-63-3/sp800-63a.html) provides detailed requirements and controls for the enrollment and identity proofing of individuals into digital identity systems.

Identity proofing is the process by which a Credential Service Provider (CSP) collects and verifies information about a person in order to issue credentials to that person, as illustrated below:

These identity proofing processes, controls, and requirements are presented in [NIST SP 800-63A](https://pages.nist.gov/800-63-3/sp800-63a.html) to achieve the following processing objectives:

* **Resolve** a claimed identity to a single, unique identity within the context of the population of users served by the CSP.
* **Validate** that all supplied evidence is valid (correct) and genuine (not counterfeit or misappropriated), and that the claimed identity exists in the real world.
* **Verify** that the claimed identity is associated with the real person supplying the identity evidence.


---

# 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://docs.1kosmos.com/identity-verification/1kosmos-as-a-credential-service-provider-csp.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.