> For the complete documentation index, see [llms.txt](https://hypercerts.gitbook.io/hypercerts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hypercerts.gitbook.io/hypercerts-docs/readme.md).
# Welcome to the Hypercerts Protocol
{% columns %}
{% column %}
#### What are Hypercerts?
Hypercerts make real value creation legible and fundable.
The current economic system struggles to recognize, track, and reward the people and projects that create collective value — from digital public goods and open-source ecosystems to regenerative land management and community initiatives. Hypercerts are an open, interoperable protocol for making contributions legible, fundable, and coordinated across platforms — turning abstract value creation into structured, shareable, and interoperable data.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
At their core, hypercerts are digital records that describe who did what, when, where, and with what evidence — without prescribing a single metric or funding mechanism. By making work visible and traceable, hypercerts enable value recognition networks where contributors, evaluators, and funders can interact constructively. Hypercerts are designed not as a single application or marketplace, but as a shared language and infrastructure that supports experimentation in funding, evaluation, and impact coordination across domains.
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
#### Dive into the tech
Ready to jump in? Start by understanding the [hypercerts infrastructure](/hypercerts-docs/getting-started/the-hypercerts-infrastructure.md), or explore our [lexicons](/hypercerts-docs/lexicons/introduction-to-lexicons.md).
{% endcolumn %}
{% endcolumns %}
---
# 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://hypercerts.gitbook.io/hypercerts-docs/readme.md?ask=&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.
