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

# Open Funding

- [Funding Basics](https://docs.projectcatalyst.io/open-funding/funding-basics.md)
- [Category Brief](https://docs.projectcatalyst.io/open-funding/funding-basics/category-brief.md)
- [Integration Guides](https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides.md)
- [Oracles: real-time data feeds](https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/oracles-real-time-data-feeds.md)
- [Stablecoins: building with verified stablecoin asset policies](https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/stablecoins-building-with-verified-stablecoin-asset-policies.md)
- [Programmable tokens (CIP-0113)](https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/programmable-tokens-cip-0113.md)
- [On-chain identity (CIP-0170)](https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/on-chain-identity-cip-0170.md)
- [Analytics: Dune and Cardano leaderboard](https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/analytics-dune-and-cardano-leaderboard.md)
- [Technology Readiness Levels](https://docs.projectcatalyst.io/open-funding/funding-basics/technology-readiness-levels.md)
- [Proof of Adoption & Standard](https://docs.projectcatalyst.io/open-funding/funding-basics/proof-of-adoption-and-standard.md): The Catalyst Pilot's plain-words card and Transaction Integrity Standard. Part I is the guide; Part II is the rulebook. Where the wording differs, Part II wins.
- [Fund Rules](https://docs.projectcatalyst.io/open-funding/funding-basics/fund-rules.md)
- [Pre-Submission Checklist](https://docs.projectcatalyst.io/open-funding/funding-basics/pre-submission-checklist.md)
- [Curation](https://docs.projectcatalyst.io/open-funding/curation.md)
- [Curation Guidance](https://docs.projectcatalyst.io/open-funding/curation/curation-guidance.md)
- [Curator Terms & Conditions](https://docs.projectcatalyst.io/open-funding/curation/curator-terms-and-conditions.md)
- [Decision](https://docs.projectcatalyst.io/open-funding/decision.md)
- [Panelist Guidance](https://docs.projectcatalyst.io/open-funding/decision/panelist-guidance.md)
- [Panelist Terms & Conditions](https://docs.projectcatalyst.io/open-funding/decision/panelist-terms-and-conditions.md)
- [Pilot Selection Process](https://docs.projectcatalyst.io/open-funding/decision/pilot-selection-process.md): This page explains how 117 applications became twelve conditionally selected teams. It also explains how the results are shared and what comes next.
- [Fine Print](https://docs.projectcatalyst.io/open-funding/fine-print.md)
- [Terms & Conditions](https://docs.projectcatalyst.io/open-funding/fine-print/terms-and-conditions.md)
- [Personal Data Consent Form](https://docs.projectcatalyst.io/open-funding/fine-print/personal-data-consent-form.md)
- [Terms of Use](https://docs.projectcatalyst.io/open-funding/fine-print/terms-of-use.md)
- [Privacy Policy](https://docs.projectcatalyst.io/open-funding/fine-print/privacy-policy.md)
- [Legal & Treasury Details](https://docs.projectcatalyst.io/open-funding/fine-print/legal-and-treasury-details.md)
- [Refunds Policy](https://docs.projectcatalyst.io/open-funding/fine-print/refunds-policy.md)


---

# 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.projectcatalyst.io/open-funding.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.