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

# Welcome

## Welcome to Pax

Welcome to **Pax Credential Platform** — a next-generation credential platform built to make **academic credential issuance and verification secure, transparent, and effortless**.

Pax provides institutions with the infrastructure to issue trusted digital credentials and enables employers, organizations, and other verifiers to verify those credentials quickly and reliably.

This documentation serves as a guide to understanding **Pax**, our technology, platform, ecosystem, and how you can participate with us.

### What You’ll Find Here

📌 **About Pax** – Learn about our vision, technology, and the problems we’re solving.

📌 **Product Documentation** – Explore how institutions can issue and manage digital credentials with Pax.

Whether you're an **institution or employer**, this documentation will provide the resources you need to understand and engage with Pax.

🚀 **Welcome to the future of trusted digital credentials.**

Need help? Connect with us via:

🔗 **Website:** [Pax Credential Platform](https://paxblockchain.com/)\
📢 **X:** [@paxcred](https://x.com/@paxcred)


---

# 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.paxblockchain.com/readme.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.