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

# Sharing your link

Once created, a request gives you two things: a short link like `recyv.xyz/r/8Kx29A`, and a QR code.

## Where links work

Anywhere text goes — X, Telegram, WhatsApp, Discord, email, an invoice PDF, or a website. There is nothing to install and no account for the payer to create.

## The QR code

Useful for anything physical: a counter, a receipt, a market stall, a business card. It is also the reliable option in a room with poor wifi, since scanning does not depend on the clipboard or a working paste.

## Links do not expire in practice

A request has a 30-day expiry that affects how it displays in your list. The link itself keeps resolving, and anyone holding it can still pay.

## What the payer sees

The address they are paying, what it is for, the amount, the token and its contract, and the network. If they are on the wrong network, the page offers to switch — and if their wallet has never heard of Robinhood Chain, it offers to add it.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.recyv.xyz/using-recyv/sharing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
