> 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/get-started/turn-on-paid-calls.md).
# Turn on paid calls
Approve the default spending limits and make a paid tool call from your local AI app.
Give your local AI app permission to spend from your Assay balance within limits. You approve this in your wallet once; the app can then pay for calls within those limits until permission expires or you stop it.
{% hint style="info" %}
**Before you start:** [connect a local AI app](/use-tools/get-started/connect-your-ai-app.md), [make a free call](/use-tools/get-started/make-your-first-call.md) and [add funds](/use-tools/get-started/add-funds.md). Hosted connectors in claude.ai and ChatGPT cannot pay. Only the **Everything** connection can pay by default; for a tool set or single-tool URL, also run the command shown on **Connect** under **Or let it also allow this URL for paid calls:**.
{% endhint %}
## Steps
{% stepper %}
{% step %}
### Ask for a paid tool
Ask your AI app to find a paid Assay tool for your task, show its price, and call one that costs no more than **$0.50**. For example:
> Find a paid Assay tool for my task. Show me what it does and its price. Use one costing at most $0.50 per call.
Replace “my task” with what you want to do. Choose a tool that actually needs payment; a free call will not open the payment setup.
The first paid attempt returns a message like this:
> This tool is paid, and paid calls are off for this agent. Open *(a link to Assay)* to turn them on (about a minute), then ask again. The page must show this payment key: 1A2B 9F3C.
The last part is the **payment key** fingerprint. The Assay local app creates this key on your computer. You do not need to create or paste it yourself.
{% endstep %}
{% step %}
### Open the link from your app
Open the complete link your app returned. It may also open in your browser automatically. Sign in to the same Assay account if asked.
The page is titled **Turn on paid calls for** your connected app. Check that it names the app you are using.
{% endstep %}
{% step %}
### Compare the payment key
Compare the fingerprint under **Payment key** on the page with the fingerprint your AI app showed. The fingerprint is the last 8 characters of the key, in two groups of four, such as `1A2B 9F3C`.
If both match, select **It matches what my app showed.** If they differ, do not approve. Return to your app and open its link again.
{% endstep %}
{% step %}
### Review the default limits
Keep the defaults:
| Limit | Default |
| ---------------- | ------- |
| **Per call** | $0.50 |
| **Per 24 hours** | $5 |
| **Days** | 30 |
Read **What your wallet will sign**. The page includes an account ceiling if one is missing or too low. That ceiling is an account-wide limit; the payment key also has its own limits above.
{% endstep %}
{% step %}
### Approve in your wallet
Choose **Approve**. Compare the key ending and limits in the wallet request with the page, then sign.
If your account ceiling must be set first, complete that signature and the payment-permission signature. Otherwise, only the payment-permission signature is needed. These approvals use free wallet signatures; you do not pay a network fee for them.
Wait for **Paid calls are on. Go back to your app and ask again.**
{% endstep %}
{% step %}
### Ask your app to try again
Return to your AI app and ask it to repeat the paid tool call. The setup attempt does not finish the tool call for you. With confirmed funds and permission active, the app can pay within the approved limits and return the result.
{% endstep %}
{% endstepper %}
## Check it worked
Your AI app returns the paid tool result without another setup link. In **Activity → Calls**, find the new call and open it to check its amount and payment status.
Find the paid call.
Check the charge on its receipt.
To stop future payments, open **Controls → Agents**, find this app's payment key and choose **Stop it paying**. Complete the wallet signature to remove its permission. Free calls keep working, and calls already made must still be settled and paid for. Stopping payment permission does not refund earlier calls or withdraw your balance.
## If something goes wrong
| You see | Do this |
| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **This link doesn't match the payment key bound to this app. Don't approve.** | Do not approve. Return to your app and open the link it gives you again. |
| **This app isn't on the account you are signed in with. Sign in with the account your app uses.** | Sign in with the account you used when connecting the app. |
| **This link is missing its payment key.** | Open the complete link your app printed; it must end with `#key=…`. |
| Funds are still confirming | Wait until the deposit is confirmed and available to spend, then retry. |
| The app refuses a call above its limits | Choose a tool within the default limits for your first paid call. |
Optional: change the default limits
Before choosing **Approve**, you can edit **Per call**, **Per 24 hours** and **Days** on this page. Review the resulting wallet request before signing. You do not need to change these fields for the basic setup.
The Assay local app also enforces its own limits: $0.50 per call and $5 per 24 hours by default. Browser limits cannot raise them. To change them, run `npx -y @goassay-ai/mcp limits set --per-call 1 --per-day 10` in a terminal.
## Next
* [Find tools](/use-tools/everyday-use/find-tools.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/get-started/turn-on-paid-calls.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.
