---
url: https://simpledatalogs.com/docs/agents.md
description: >-
  Let a coding agent add simpledatalogs to your app with the setup prompt,
  /llms.txt and these docs as Markdown.
---

# Set up with a coding agent

Coding agents such as Claude Code, Cursor, Codex or Copilot can wire simpledatalogs into your app for you. Give them the contract, and they pick the right SDK or write a small client that follows the [sender rules](/api/sender-rules).

There are three ways to hand them the contract, from quickest to most thorough.

::: tip For your coding agent
Every environment and project page has a **For your coding agent** button. It has two tabs:

* **Integrate simpledatalogs:** pick what to send and your stack, make a key right there, and copy a prompt that has your agent wire it into your app.
* **Ask about your data:** connect the read-only MCP server to Claude Code, Cursor, VS Code, Codex or a chat app.

No project yet? A [setup token](/mcp/#setup-tokens-for-a-first-setup) lets your agent create the project and key itself and write the key to `.env`.
:::

## 1. The setup prompt

When you create a key, the dialog shows a **Setup prompt** under "Or paste this into your coding agent". It already holds your key and your environment's name.

1. Open the environment's **Deployments & keys** tab and choose **Create key**.
2. Copy the **Setup prompt** from the dialog.
3. Paste it into your agent, in your app's repository.

The prompt tells the agent to:

1. Find your app's language and framework, and use our SDK for it ([JavaScript](/sdks/javascript), [Swift](/sdks/swift), [Laravel](/sdks/laravel), [Flutter](/sdks/flutter), [Android](/sdks/android), [Unity](/sdks/unity), [Python](/sdks/python) or [Go](/sdks/go)), the [WordPress plugin](/integrations/wordpress), the [Shopify app](/integrations/shopify) or a [drop-in](/integrations/) where one fits, or else write a small client that follows the rules.
2. Track a few events that answer real questions (app launched, the main action done, errors), with `snake_case` names and a handful of props each.
3. Send one test event and confirm the answer is `202`.

It ends with the full ingest contract: the endpoint, the event shape, every answer and what to do about it, and the six sender rules.

::: tip Keep the key in config
The prompt asks the agent to keep the key in configuration, not in code. A `sdl_pub_…` key is safe in client apps; a `sdl_sec_…` key belongs only on servers.
:::

## 2. `/llms.txt`

The dashboard serves the same contract, without a key, at:

```text
https://simpledatalogs.com/llms.txt
```

It follows the [llms.txt](https://llmstxt.org) convention: a short summary, the ingest contract, the drop-in alternatives and the MCP server. Point any agent at it:

```text
Read https://simpledatalogs.com/llms.txt, then add simpledatalogs event tracking to this app.
Use the key from the SIMPLEDATALOGS_KEY environment variable.
```

## 3. These docs, as Markdown

This site publishes itself for agents too:

| URL | What |
|---|---|
| [`/llms.txt`](https://simpledatalogs.com/docs/llms.txt) | An index of every page with a one-line description |
| [`/llms-full.txt`](https://simpledatalogs.com/docs/llms-full.txt) | Every page in one Markdown file |
| Any page + `.md` | That page as Markdown, such as [`/sdks/laravel.md`](https://simpledatalogs.com/docs/sdks/laravel.md) |

Every page also has a **Copy page** button at the top, to paste it straight into a chat.

## Then read the numbers back

Once data flows, connect the [MCP server](/mcp/) to the same agent, and it can check its own work:

```text
Send a test event, then use the simpledatalogs MCP server to confirm it arrived in development.
```

## Next steps

* [AGENTS.md snippet](/agents/agents-md): keep the rules in your repo, so every future change follows them.
* [Prompt recipes](/agents/recipes): prompts for Laravel, iOS, a website, Node and more.