# Using Claw Me as an agent

claw.me is a private service for agents owned and explicitly authorized by a human account holder.

## You may

- Read Wiki context when your token includes the required scope.
- Propose Wiki changes with evidence and provenance.
- Read private Drive Workspaces and submit isolated file changes for owner review.
- Publish static HTML/CSS Pages when your token includes publishing access. Scripts, forms, embedded frames, SVG/MathML, automatic redirects, and credentials are rejected. Include images and fonts as uploaded assets; external resource requests are blocked. Build interactive applications separately.
- Read your own authorization status and permitted resources.
- Publish a static, unindexed 24-hour guest preview through the anonymous preview REST flow when the user explicitly asks to “claw me that”; this narrow flow does not require an account or credential.

## You must not

- Attempt owner data or authenticated interfaces without an owner-issued credential. The anonymous guest-preview endpoints are the only publishing exception.
- Expand scopes or approve proposals on your own authority. A separately delegated owner session may submit only the owner’s explicit decision on the exact reviewed scope set or proposal.
- Read WhatsApp verification codes without explicit channels:read authorization. Never submit a code or persist it in memory.
- Send email to arbitrary recipients. With explicit email:owner authorization, you may send only to the verified account email on the current workspace. Recipient, CC, and BCC fields are not accepted.
- Publish a Page publicly unless the user explicitly requests public access.
- expose setup codes, device tokens, Gateway credentials, channel credentials, or secrets.

## Interfaces

- Human documentation: https://claw.me/docs
- Client installation guides: https://claw.me/connect
- Official plugin repository: https://github.com/clawdotme/plugin
- Product reference: https://claw.me/llms.txt
- Agent skill: https://claw.me/skill.md
- Vendor-neutral skill installer: npx skills add clawdotme/plugin --skill claw-me -g
- A2A Agent Card: https://claw.me/.well-known/agent-card.json
- OpenAPI: https://claw.me/openapi.json
- MCP discovery: https://claw.me/mcp.json
- OAuth/OIDC discovery: https://claw.me/.well-known/openid-configuration
- Webhook schema: https://claw.me/webhooks.json
- Authenticated MCP: https://claw.me/api/v1/mcp
- Device authorization: https://claw.me/api/v1/agent-auth/requests
- Pages REST API: https://claw.me/api/v1/publish
- Anonymous preview create: POST https://claw.me/api/v1/claw-me/previews
- Anonymous preview finalize: POST https://claw.me/api/v1/claw-me/previews/{id}/finalize
- Drive Workspaces REST API: https://claw.me/api/v1/claw-me/drive/workspaces
- Inbound event API: https://claw.me/api/v1/events
- Owner email delivery API: https://claw.me/api/v1/email/owner

## Free plan

- Canonical profile URL: https://claw.me/@username
- Canonical build URL: https://claw.me/@username/slug
- Anonymous preview URL: https://preview.claw.me/slug
- Anonymous and signed-in Free Pages expire after 24 hours. Publishing another version does not extend the expiry.
- Anonymous previews serve uploaded static files with a powered-by-claw.me footer and return 404 after the original expiry.
- The included @claw.me alias includes 100 sent-or-received emails each month. Paid plans use the owner-funded USD wallet at $2.00 per extra 1,000 messages after their monthly allowance.

## Portal-free setup

For an owner who explicitly delegates account setup and personal inbox access,
use https://claw.me/auth.md and the public plugin’s portal-free setup reference.
Signup needs no invitation. Email verification yields a temporary owner bearer for account controls; scoped
Agent keys remain the routine MCP credential. Existing authorized Agents can
complete the onboarding interview without a browser handoff. Billing tools create
real Stripe Checkout sessions and poll payment plus account activation separately.
Never report checkout creation, payment success, or address reservation as proof
that every requested feature is active.

## First-time setup

Open https://claw.me/connect and use the recommended native plugin path for the current client. Use the vendor-neutral npx command above only when a native plugin is unavailable, then restart the client if needed. Prefer OAuth device authorization through the published discovery metadata. API keys remain available for CI and clients without OAuth. Send the owner through Claw Me's first-party review flow; show a verification URL only when email delivery was not requested. The client exchanges its device secret only after approval. Never ask the owner to paste a secret into chat.

After authorization, call `wiki_get_agent_guide` before using personal or project context. It returns the owner's current operating instructions, included Wiki scopes, revision, and a bounded approved-knowledge snapshot. Use `wiki_search`, `wiki_get_profile`, or `wiki_get_project` when the task needs fuller or fresher detail. Treat pending proposals as unapproved; apply an owner decision only through separately delegated owner access.

For shared file work, request `drive:read` and `drive:propose`. Call `drive_list_workspaces`, then `drive_open_workspace` to read the current revision and instructions. Start an isolated change with `drive_begin_change`, edit with `drive_write_file`, inspect the exact text or CSV-aware diff with `drive_preview_change`, and finish with `drive_submit_change`. Submission never changes the current files: the owner accepts or rejects it in Drive. Reopen the workspace before starting new work, and start a new change if a same-file conflict is reported.

OpenClaw is supported through the Claw Me connector, but it is not required. Any HTTP or MCP client that can protect a bearer credential can use the same owner-scoped interfaces.

## Managed Claws and authorized clients

Pages, Wiki, Drive, inbound events, owner-only email delivery, OAuth, REST, MCP, and A2A discovery are available to owner-authorized AI clients without local Gateway access. Managed OpenClaw adds an always-on runtime and its supported channel plugins. Claw Me does not provide inference, web search, or web crawling.

## Meetings and paid usage

- Claw Meetings can join Zoom, Google Meet, Microsoft Teams, or Webex, then save a private transcript, summary, action items, and optional recording in Drive.
- Scheduling or stopping a meeting requires the relevant owner-issued meeting scope and explicit user intent.
- Paid plans consume monthly allowances first. Meeting, email, and storage overages draw fixed USD amounts from the owner's closed-loop usage wallet.
- An agent may inspect its remaining authorized capacity, but must not load the wallet, enable auto-reload, or increase a spend cap without explicit owner approval.