# AI assistants

These docs are built to be read by machines as well as people. If you are integrating the SDK with an AI coding assistant, point it here rather than pasting snippets — everything below is available without an API key or an account.

## On every page

The **Ask AI** button at the bottom of each page opens the current page in ChatGPT or Claude, copies it as Markdown, and links the raw Markdown.

## Markdown routes

Append `.md` to any page URL to get its source rather than the rendered HTML:

```txt
https://docs.yodl.me/sdk/react-native/quickstart.md
```

Pages are also content-negotiated: a request without a browser `User-Agent` receives Markdown from the normal URL. So this returns Markdown, while your browser gets the rendered page:

```bash
curl https://docs.yodl.me/sdk/react-native
```

## llms.txt

Two files, both generated on every build:

| File | What it is |
| --- | --- |
| <a href="/llms.txt"><code>/llms.txt</code></a> | An index — every page with its title, path and one-line description. ~4 KB |
| <a href="/llms-full.txt"><code>/llms-full.txt</code></a> | The entire documentation concatenated into one file. ~80 KB |

Use the index to let a model choose what to read; use the full file when you want the whole corpus in context at once.

## What this does not serve

The SDK's source code. The packages are published on npm ([`@yodlpay/react-native`](https://www.npmjs.com/package/@yodlpay/react-native), [`@yodlpay/react-native-eip-7702-provider`](https://www.npmjs.com/package/@yodlpay/react-native-eip-7702-provider)) and their types travel with them, which is the better source for an assistant writing integration code.

## One caveat

An assistant that has read these docs still guesses. The SDK's config example is type-checked against the real package on every build, so what you see compiles — but a generated integration is not. Check anything an assistant writes against the [API reference](/sdk/react-native/api), and let the compiler decide.