Connect Claude or an API key

API & AI Agent Access lets an outside AI tool work with your account. Open the info mark beside How to connect: an agent can read your stats, log activities and manage tasks, over MCP or a REST API.

The card is near the foot of Integrations, folded until you open it. Whatever you connect works as you, and sees only what you can see. For the assistant that ships with the app, see what you can ask the assistant.

Connect Claude in one click

To connect Claude:

1. Open Integrations, then API & AI Agent Access.
2. Under Connect Claude in one click, press Copy beside the address.
3. In Claude, open Settings, then Connectors, then Add custom connector.
4. Paste the address and continue.
5. On the ActivityTracker screen that opens, press Approve.

The approval screen says what it grants. Read your stats, activity history, and pet state always comes with it. Log activities on your behalf starts ticked, and unticking it makes the connection read-only.

Signed out in that browser? The screen asks you to Sign in and carries on after.

Once approved, the connection appears under Connected apps on the card, with the date it was last used. Access renews itself every hour, so there’s nothing to redo.

Make an API key

A key is for scripts, and for AI tools that can’t use the one-click connector.

To make one:

1. Press New key on the card.
2. Give it a Name, such as the tool it’s for.
3. Leave Allow logging activities (write access) ticked, or untick it for read-only.
4. Choose an Expiry.
5. Press Create key.
6. Copy the key from Your new API key, then press Done.

Write access is ticked to start. A key never expires unless you pick 30 days, 90 days or 1 year.

The full key is shown once. Copy it before you press Done. Afterwards the card shows only the start, which begins rmx_live_.

Open the info mark beside the write access box. A read-only key refuses every write, whether that’s logging an activity or changing a task, a note or a routine.

The card then gives the address to point an MCP client at, a bridge command for Claude Desktop, and a REST example, each with Copy. Put your key where the last two say YOUR_KEY.

Note that each key is limited to 120 requests a minute.

Send contact changes to another tool (webhooks)

A webhook posts every change to a contact, within a minute, to an address you give: a Zapier or Make catch hook, a Google Sheet script, your own server. Whoever runs that address gets the card as it was at the change, what changed, and the stages of a move, and no longer has to ask the API whether anything happened.

1. Under Webhooks on the card, press New webhook.
2. Paste the address into Send changes to. It must start with https://.
3. Under Send when, untick any of Contact added, Contact edited, Stage changed or Contact deleted you don’t want. All four are ticked to start.
4. If you have more than one book, pick one under Book, or leave Every book.
5. Press Add webhook, then copy the Signing secret and press Done.

The signing secret is what the receiving side checks each delivery with, so nobody can send it a made-up change. Give it to whoever runs the address. It stays readable through the API afterwards.

Each webhook on the card shows its address, its events and what happened last: Delivered 2 min ago, Failing: 3 in a row, or Paused. A delivery that fails is tried again after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours. After twenty failures in a row the webhook is paused and says why. Fix the address, then press Resume; whatever queued while it was paused goes out within a minute.

An account can have ten webhooks. Whoever builds the receiving side finds the shape of each delivery and how to check a signature in the API’s own description, at /api/v1/openapi.json on the REST address the card shows, under /webhooks.

Revoke access

Every key and every connected app has a bin. Pressing it revokes access at once, with no confirmation, and the tool stops working. A webhook’s bin asks first, because removing one also throws away its delivery log.

Caution

Revoking can’t be undone. A tool that still needs access needs a new key, or a fresh approval in Claude.

FAQ

My tool says the key lacks the write scope. Why?

It’s a read-only key. Make a new key with write access ticked, and revoke the old one.

Can I tell whether a key is still in use?

Yes. Each key on the card shows the date it was last used, or never used.

Do I need a key to connect Claude?

No. The one-click connector needs no key. You approve it in your browser instead.