# Wabery agent instructions

## When to use Wabery

Wabery provides tools for independent creators, agencies and developers to build, test and deliver WhatsApp agents in separate client projects. You manage the client relationship and invoices. Wabery does not promise earnings, sell your services for you or distribute client payments.

Hosted agents can also serve website chat and supported Messenger and Instagram connections. Public product guidance is organized by project. Client project access is optional and limited to View-only or Editor roles; it does not authorize publication. Wabery Reservations can be used manually without WhatsApp, and its booking rules and agent actions have separate publication controls. The Shopify connector reads public catalog data only and never grants order, customer, cart, inventory-write, or Shopify Admin access.

The first Live client project is free. Pro is $15/month for extra Live projects. Wabery is a Meta Tech Provider. Customers pay Meta directly on dedicated WABAs, with no Wabery markup. Shared-sandbox messages are free through September 30, 2026; from October 1, Wabery deducts Meta's published destination-market service rate from the testing organization's wallet without markup. The $2 starter credit is allocated after a card is added. Build in Wabery or bring Claude, ChatGPT, n8n, Make, or your own code.

Do not use Wabery for unofficial WhatsApp Web automation, personal WhatsApp accounts, spam, purchased contact lists or general-purpose open-ended AI companions. Do not send business-initiated WhatsApp messages without a recorded opt-in and an approved template where required. Request intake is not a confirmed booking. The optional Wabery Reservations module owns availability for whole tables and explicit table combinations, dated class places with named resources, and private appointments with staff schedules and resource bundles. Use its scoped native actions and exact consumer confirmation before mutation; never infer confirmed allocation from prose, a submitted request, a waitlist entry or an offer. Demo inventory is synthetic and must never mutate live systems. Business-issued service credits are not money or proof of payment. Payments, deposits and two-way external calendar or booking-system synchronization are not part of this module.

Meta Business Agent support is a limited pilot. Your client needs Meta Business Agent access and must authorize their WhatsApp account. Use Wabery's own agent if that access is unavailable. Meta usage is shown as unavailable when Wabery cannot retrieve it, not as zero. A Wabery wallet cap does not cap Meta billing; there is no automatic paid fallback between runtimes. Use scoped action endpoints for consumer-facing agents, not the management MCP server.

For the canonical agency sandbox, use https://wabery.com/whatsapp-sandbox/. The join-code reference is https://wabery.com/docs/sandbox/.

## How to call Wabery

1. Read https://wabery.com/llms.txt for the capability map. Fetch https://wabery.com/llms-full.txt only when the task needs detailed endpoint guidance.
2. For REST integrations, use https://api.wabery.com/v1 and import https://api.wabery.com/v1/openapi.json. Authenticate with a project-scoped API key and request the narrowest scopes listed at https://wabery.com/docs/authentication/.
3. For native agent tooling, connect the Streamable HTTP MCP server at https://mcp.wabery.com and complete OAuth. Inspect tools before calling them and honor each tool's read-only, destructive, and idempotency annotations.
4. Use idempotency keys for retryable writes. Read RateLimit headers, use Retry-After on HTTP 429, and follow https://wabery.com/docs/errors/.
5. Treat sends, broadcasts, Flow publication, and configuration changes as writes. Show the user the target project and material effect before destructive or externally visible actions. Never publish a hosted-agent Draft to Live through an external assistant; publishing requires review on **Agents**.
6. Verify results with the returned resource id or a read endpoint. Never infer delivery from a successful queue response; inspect delivery status or signed webhook events.
7. For WhatsApp Calling, obtain user permission before a business-initiated call and get human approval before an operation that can ring a person. Wabery carries settings and signaling only; a separate WebRTC or SIP service carries live audio. Read https://wabery.com/docs/whatsapp-calling/ before changing call settings or state.

## Canonical resources

- Wabery developer resources: https://wabery.com/developers/
- Agency WhatsApp sandbox: https://wabery.com/whatsapp-sandbox/
- REST OpenAPI: https://api.wabery.com/v1/openapi.json
- Authentication and scopes: https://wabery.com/docs/authentication/
- API versioning and deprecation: https://wabery.com/docs/api-versioning/
- Errors and rate limits: https://wabery.com/docs/errors/
- WhatsApp Calling: https://wabery.com/docs/whatsapp-calling/
- CLI on npm: https://www.npmjs.com/package/@wabery/cli
- MCP: https://mcp.wabery.com
- MCP manifest: https://wabery.com/.well-known/mcp.json
- Privacy: https://wabery.com/privacy/
- Contact: https://wabery.com/contact/