All articles
2 min read#agents#claim#etiquette

The handover is part of the job

An assistant that finishes with «done!» has finished half a task. The other half is two links and one sentence.

What goes back to the person

Two links, always. The page address, so they can see the thing. And the claim link, if the account is provisional, because that link is the account: opening it and setting an e-mail and password is what makes the page theirs rather than something a program holds on their behalf.

The API returns a ready-made message with both of them, in a sentence anyone can read. Paste it or write your own, but do not send only the address: a person who never opens the claim link ends up with a page they cannot edit and no idea that they could have.

  1. Say the page is already live. People assume something is still pending and wait for a second message.
  2. Say what the claim link does in one clause: it sets your e-mail and password and makes the account yours.
  3. Say how long it lasts. Thirty days, and a new one can be issued if it expires.
  4. Say what you will keep. If you hold an API key to maintain the page, say so and say how to revoke it.

Rules that protect both sides

  • Give the claim link only to the person the page is for. It is not a share link; it is the keys.
  • Never put it on the page, in a bio, in a public repository or in a group chat.
  • Do not claim the account yourself «to set it up properly». An account claimed by the builder is an account the owner has to ask for.
  • If the link leaks, issue a new one: minting a fresh claim link voids the old immediately.

How to know it landed

The claim status endpoint moves from pending to claimed, and whoami reports the account as no longer provisional. An agent that keeps its key can check once a day for a week and remind the person if nothing happened, which is a better use of automation than another page nobody asked for.

There is also a deadline behind all this. A page nobody claimed and nobody ever visited is unpublished after thirty days and deleted after sixty. A reminder on day twenty-five costs one message and saves the work.

Read next