Get the caller's recovery account

curl https://api.subscriby.net/v1/me/recovery \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

Recovering the creator's sign-in account, and keeping a backup account ahead of a ban, are two-sided handshakes: the API mints a code, the creator taps the link (or types the code) from the account to detect, the connector records which account that was, and the API confirms. Both sides have to agree, which is what keeps a leaked link from binding a stranger. These endpoints live under /v1/me because they are about the caller, never a project, and the actions behind them refuse anyone but the account holder.

These flows are deliberately not offered as MCP tools: moving a sign-in is a human act, and get_me already shows which accounts are linked.

• primary_display_name and backup_display_name name the accounts as the connector reported them; their identifiers on the connector never appear.
• relink_handshake and backup_handshake are the newest handshake of each kind, in whatever state, so a client can pick up a flow the creator started on the dashboard or in the bot.