> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/getting-started/tutorial/uploading-schema.md).

# Uploading the Credential Schema

**What We Are Doing:**

* Defining a credential schema that outlines the data fields (e.g., age, firstName, lastName).
* Uploading this schema to the Issuer so it knows how to structure the KYC Verifiable Credential.

**Why:** Without a schema, the Issuer does not know what the credential should contain. The schema ensures consistency and interoperability.

**Steps:** Create a `schema.json` file (locally) with:

```json
{
  "name": "KYC Verifiable Credential",
  "type": "KYC Verifiable Credential",
  "credentialSubject": {
    "type": "object",
    "properties": {
      "age": {
        "type": "number",
        "title": "age"
      },
      "firstName": {
        "type": "string",
        "title": "first_name"
      },
      "lastName": {
        "type": "string",
        "title": "last_name"
      }
    },
    "required": ["age", "firstName", "lastName"]
  }
}
```

Upload it using `curl`:

```bash
curl -X POST "$ISSUER_URL/api/v1/schemas" \
  -H "x-client-secret: $ISSUER_SECRET" \
  -H "Content-Type: application/json" \
  -d @schema.json
```

Now the Issuer knows how to issue a "KYC Verifiable Credential" with the specified fields.


---

# 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.empe.io/getting-started/tutorial/uploading-schema.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.