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

# Welcome to Assay

Choose your path to use AI tools or earn from your API.

Assay is the trust and credit layer for agent payments. Agents pay for what endpoints actually deliver, providers back delivery with stake, and agents have recourse through no charge or a refund when a call fails.

## I want my AI to use tools

[Use tools](https://docs.goassay.ai/use-tools/en) → **Get started** — know what a tool delivers before your AI pays for it. [Create your account](https://docs.goassay.ai/use-tools/en/create-your-account), connect your AI app and make a free call. Add funds and approve spending only when you want paid tools through a local app.

<figure><img src="https://3137597766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fae1PP1bmUPVQyrp8VrU5%2Fuploads%2Fgit-blob-ee6ddba7f543d99a8cf7b7c8e0657a1bd8995c74%2Fwelcome-to-assay-1.png?alt=media" alt="Assay Spend page showing charged and not-charged totals for the last 24 hours, grouped by tool"><figcaption><p>See what your tools cost and which calls were not charged.</p></figcaption></figure>

## I have an API to earn from

[List your API](https://docs.goassay.ai/list-your-api/en) → **Get started** — earn from your API and back its quality promise with stake. [Set up your account and wallet](https://docs.goassay.ai/list-your-api/en/set-up-your-account), connect your API to a tool and put your listing live. Choose an existing catalogue tool or publish your own.

<figure><img src="https://3137597766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fae1PP1bmUPVQyrp8VrU5%2Fuploads%2Fgit-blob-298cd8c2a22af8bcd5a2f0caec5fb9203c55a93f%2Fwelcome-to-assay-2.png?alt=media" alt="Provider console listing two tools with their status, price per call, calls and earnings"><figcaption><p>Your listings show each tool's status, price and earnings.</p></figcaption></figure>

## Start here

* [What is Assay](/start-here/what-is-assay.md) — what it does and the words you will meet.
* [How it works](/start-here/how-it-works.md) — follow one call and its money.

## Help

* [Glossary](/help/glossary.md) — look up a word.
* [FAQ](/help/faq.md) — costs, payments, safety and getting paid.
* [Troubleshooting](/help/troubleshooting.md) — find the guide for a problem.

## Go further

* Developers (optional): [Developer docs](https://docs.goassay.ai/developers/en) for people connecting software.

## Next

* [What is Assay](/start-here/what-is-assay.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.goassay.ai/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.