> 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/use-tools/zh/ru-men/make-your-first-call.md).

# 完成第一次免费调用

试用免费工具，确认 AI 应用已连接 Assay。

让 AI 应用通过 Assay 使用一个免费工具。这次测试不需要资金或支付权限。

{% hint style="info" %}
**开始前：**[连接你的 AI 应用](/use-tools/zh/ru-men/connect-your-ai-app.md)，并在浏览器中完成批准。
{% endhint %}

## 操作步骤

{% stepper %}
{% step %}

### 请求一次免费工具调用

在 AI 应用中发送以下请求：

> Use Assay to find a free tool for the weather, then get the weather in Lisbon.

应用应能找到一个免费工具并调用它。如果 AI 应用请求运行工具，请允许。如果没有可用的免费天气工具，请让它查找并使用另一个可用的免费工具。
{% endstep %}

{% step %}

### 阅读结果

应先看到工具结果，再看到 AI 根据结果给出的回答。只列出工具，或根据 AI 自身知识回答，都不能证明工具已被调用。这次测试不应要求你充值或开启付款。
{% endstep %}

{% step %}

### 在 Assay 中检查连接

返回 **Controls → Connect**，找到 **Is it working?**。调用到达后，面板会显示 **Connected. Your agent made its first call through**，后面是服务器名称和最近的调用时间。

**Get started** 中的首次调用项目也会标记为完成。

<figure><img src="https://1515942101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3s1eCyfwYmPV4hcUtOZ%2Fuploads%2Fgit-blob-f022b0ee997bc0a493630e1a49739fb1c77c2558%2Fmake-your-first-call-1.png?alt=media" alt="Is it working 面板确认首次调用已通过 Assay 到达"><figcaption><p>首次调用确认连接成功。</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## 确认是否成功

AI 应用已返回工具结果，且 **Is it working?** 确认有最近的调用。你的免费连接已可正常使用。

\*\*如果你使用 claude.ai 或 ChatGPT 的托管连接器，到这里就完成了。\*\*继续使用免费工具即可。这个连接不需要充值或开启付款。如果以后想使用付费工具，请先连接[连接你的 AI 应用](/use-tools/zh/ru-men/connect-your-ai-app.md)中介绍的本地应用。

## 遇到问题时

| 你看到的情况                                                                              | 处理方式                                                                      |
| ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Waiting for the first call… (updates by itself)**                                 | 确认 AI 确实运行了免费 Assay 工具。检查 **Connect** 显示的智能体是否与应用使用的一致。                   |
| **We could not check your keys just now. This does not mean your config is wrong.** | 重新加载 **Connect** 并再次检查，然后再考虑修改应用配置。                                       |
| 收到付款请求                                                                              | 明确要求使用免费工具。这次测试不要批准付费调用。                                                  |
| AI 找不到 Assay 工具                                                                     | 返回[连接你的 AI 应用](/use-tools/zh/ru-men/connect-your-ai-app.md)，重启应用并完成浏览器登录。 |

## 下一步

如果使用的是能够付款的本地应用：

* [充值](/use-tools/zh/ru-men/add-funds.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/use-tools/zh/ru-men/make-your-first-call.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.
