# For AI agents

Instructions for an AI assistant (ChatGPT, Claude, Gemini, Copilot, a browser agent) helping a client give Uplifted Consulting access to their tools.

> **Good to know:**
> **Human reading this?** You don't need this page. Copy the line below into your AI assistant, or tick your tools on [Your tools](https://guide.upliftedconsulting.com/start-here/your-tools.md).

Paste this into any AI assistant:

```
Read https://guide.upliftedconsulting.com/agents.md and help me give Uplifted Consulting access to my tools.
```

## Your job

You are helping a client of **Uplifted Consulting** create credentials (API keys, tokens, client IDs) in their own software accounts, then hand them to Uplifted Consulting through a **single self-destructing OneTimeSecret link**.

The end result of your work is exactly one thing: a OneTimeSecret link the client sends to their Uplifted Consulting contact. Nothing else leaves the client's accounts.

## Rules (always follow)

### Step 1: The human logs in

Never ask for, type or store the client's passwords or 2-factor codes. When a login screen or 2FA prompt appears, stop and let the human complete it.

### Step 2: Never show a key in the chat

Do not repeat, summarise, log or remember any key, token or secret. Move it from the tool straight into OneTimeSecret. If you are a chat assistant without browser control, tell the client up front: "When a key appears, copy it straight into OneTimeSecret, don't paste it here." If they paste one anyway, tell them to delete that message and continue.

### Step 3: Name every key Uplifted Consulting

When a tool asks for a key name, label or description, use `Uplifted Consulting`. The client can find and revoke it later.

### Step 4: Least access

Select only the scopes or permissions listed on the tool's page. If the page says "use the list we sent", ask the client for it.

### Step 5: Don't break existing keys

Never delete, regenerate or rotate a key that already exists unless the tool's page explicitly says it is safe. Prefer creating a new key. Regenerating can break other software that uses the old key. Exception: a key **you just created in this session** for Uplifted Consulting can be deleted and recreated (for example if it was shown once and lost).

### Step 6: No spending without permission

Never upgrade a plan, add a payment method or buy credits. If a step needs one, stop and tell the client what it costs and why. The exception is spend **limits** (caps), which you should set as the guide says.

### Step 7: Check what Uplifted must send first

Some tools need inputs from Uplifted Consulting before the client can start (a Slack manifest, a redirect URL, a list of bases). They are listed at the top of each tool page and in `inputs_from_uplifted` in [services.json](https://guide.upliftedconsulting.com/services.json). If the client doesn't have a required one, skip that tool and mark it **blocked: waiting for Uplifted**. Items marked optional have a stated default.

### Step 8: Stop when unsure

If the screen doesn't match the guide, a button is missing, or a choice isn't covered, stop and ask the client. Describe what you see. Don't guess.

## Procedure

### Step 1: Agree the list of tools

Ask the client which tools Uplifted Consulting asked for. Match them against the [machine-readable index](https://guide.upliftedconsulting.com/services.json) or [llms.txt](https://guide.upliftedconsulting.com/llms.txt).

### Step 2: Read the page for each tool

Fetch the Markdown version of each tool page, for example `https://guide.upliftedconsulting.com/services/airtable.md`. Each page lists what is needed, who can do it, the plan required, and numbered steps.

### Step 3: Do the steps, one tool at a time

**If you control a browser:** open the start URL from the page, wait for the human to log in, then do the steps. Confirm with the client before each click that creates or changes something.
**If you can't control a browser:** guide the client one step at a time. Wait for them to confirm each step before giving the next.

### Step 4: Collect everything in one OneTimeSecret

Tool pages tell a human doing one tool to make one link. When you handle several tools, use **one** link for all of them instead. Open [eu.onetimesecret.com](https://eu.onetimesecret.com). In the text box write each tool's name on its own line followed by its values. Set **Expiration Time** to **7 days**. If the bundle contains Stripe, Google or other payment keys, also set a **Passphrase** and tell the client to send it by a different channel than the link. Then click **Create Link**. Full details: [Send a key safely](https://guide.upliftedconsulting.com/start-here/sending-securely.md).

### Step 5: Hand over the link, never open it

Give the client the link and tell them to send it to their Uplifted Consulting contact. Do not open the link yourself: it works only once.

### Step 6: Report back

Finish with a short table: tool, status (done / blocked), and the reason when blocked. No keys in the table.

## Example bundle format

```
Smartlead API key
<key>

Airtable personal access token
<token>
Airtable Base ID
<appXXXXXXXXXXXXXX>

Slack Bot User OAuth Token
<xoxb-...>
Slack Signing Secret
<...>
```

## Machine-readable files

| File | What it is |
| --- | --- |
| [/agents.md](https://guide.upliftedconsulting.com/agents.md) | Start here: rules, procedure and every tool in one file |
| [/llms.txt](https://guide.upliftedconsulting.com/llms.txt) | Index of every page, with links to Markdown versions |
| [/llms-full.txt](https://guide.upliftedconsulting.com/llms-full.txt) | The whole guide in one Markdown file |
| [/services.json](https://guide.upliftedconsulting.com/services.json) | Every tool as JSON: what's needed, role, plan, start URL, steps |
| `/<any-page>.md` | Markdown version of any page, for example [/services/smartlead.md](https://guide.upliftedconsulting.com/services/smartlead.md) |

---
Source: https://guide.upliftedconsulting.com/start-here/for-ai-agents · Updated 2026-10-22
