> For the complete documentation index, see [llms.txt](https://myaipet.gitbook.io/myaipet-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://myaipet.gitbook.io/myaipet-docs/02-everyday-use.md).

# 2. Getting started and everyday use

## 2.1 Accounts and sign-in

Each account is identified by a wallet address. The web app uses Sign-In with Ethereum, or SIWE, to request a sign-in message and verify its signature. Signing that message is not a payment, does not send an on-chain transaction and does not require a network fee.

Connecting a wallet and signing in are separate steps. A connected wallet may still need to sign a login message before the service can load private account information or authorize a purchase.

Use the official application at [app.myaipet.ai](https://app.myaipet.ai), inspect wallet requests before approving them, and keep recovery phrases and private keys private.

## 2.2 A pet and its routine

A pet's profile and care state are maintained by the service. Users can interact with their pet, talk with it and use available customization features. Action availability and daily limits are shown in the app.

The current experience also includes a nighttime routine based on the owner's device time. Between 22:00 and 07:00, petting and talking do not wake the pet, while feeding, playing, walking or training do. Waking a pet does not carry a penalty. An eligible uninterrupted night can provide an energy and happiness benefit; this is a pet-state benefit, not a Season Points award.

## 2.3 Conversation

Conversations can draw on the pet's stored memories. This helps the pet refer to previous topics and preferences, although recall is selective and may be incomplete or wrong.

Daily reply capacity depends on the account's current access. Higher capacity is a usage allowance, not a promise of unlimited conversation or guaranteed response quality.

## 2.4 The Chrome extension

The official [MY AI PET Desktop Companion extension](https://chromewebstore.google.com/detail/lfcopcpgclgflcnnppjljdamjkimlmeh) connects to the same service account. It brings the pet into supported browser contexts and can let the pet respond to page context.

The public listing is version 2.5.8 for this edition. Install from the official listing and follow the extension's account-linking flow.

Page context is sensitive information. The extension has built-in blocked domains and limits the size of page summaries, but these controls do not make every page safe to share. Avoid exposing confidential information through browser-based AI features. Chapter 9 describes the relevant privacy boundaries.

## 2.5 Developer access

The MIT-licensed [PetClaw SDK](https://www.npmjs.com/package/@myaipet/petclaw-sdk), version 2.1.0 for this edition, includes a command-line interface and an MCP server. Developers can use these tools to chat with a pet, recall memory, access supported skills and export pet data.

Developer access uses credentials created through the web application. Treat those credentials as private, revoke them when no longer needed, and use the package's current installation instructions.

## 2.6 Agent Office

Agent Office runs supported tasks through a planning and execution loop. Available tools include memory recall and selected external information sources. A run may consume credits and is subject to task and execution limits.

GitHub and Notion connections are not currently enabled. Telegram, Slack, Discord and Twitter agent channels are also paused. Their presence in the underlying software does not make them available product integrations.

A separate Telegram groups beta, in which a pet's own bot replies in the owner's Telegram groups, is described in [Chapter 11](/myaipet-docs/11-telegram-groups-beta.md). It does not change the status of the paused agent channels.