canonical: https://jentic.com/apis/cresclab.com/cresclab # Cresclab CAAC Go Developer API The CAAC Go Developer API sends WhatsApp text messages and generates AI replies from a business's own content. One operation delivers a message from the workspace number, another drafts a reply grounded in the business content so responses stay on-brand, and a third verifies the workspace API key and returns the workspace it belongs to. It is a small, focused surface for wiring WhatsApp messaging and AI-assisted responses into an agent. ## For AI agents Send WhatsApp text messages from a workspace number and generate AI replies grounded in business content, plus verify the workspace a key belongs to. Authenticated with a workspace API key as a bearer token. ## Scope Does not handle voice calls, SMS, or contact-list management. Use for sending WhatsApp messages and generating AI replies only. ## Capabilities - Send a WhatsApp text message from the workspace number - Generate an AI reply drafted from the business's own content - Verify a workspace API key and read the workspace it belongs to ## Use cases ### WhatsApp Customer Messaging An agent sends a WhatsApp text message to a customer from the workspace number, for an order update, a reminder, or a reply in an ongoing thread. CAAC Go handles delivery through the workspace's connected number, so the agent only supplies the recipient and message content. Example prompt: Send a WhatsApp message with POST `/api/v1/messages` to the customer's number with the order-update text ### AI-Assisted Reply Drafting An agent generates an AI reply grounded in the business's own content before sending it, so the response stays accurate and on-brand. CAAC Go drafts the reply from the supplied business content, and the agent can then send it as a WhatsApp message in the same flow. Example prompt: Call POST `/api/v1/ai/reply` with the business content and incoming question, then send the draft with POST `/api/v1/messages` ### AI Agent Integration via Jentic An AI agent reaches CAAC Go through Jentic without handling the workspace key itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the credential injected at run time. This lets an agent send a WhatsApp message or draft a reply as one step in a support workflow without wiring the key in code. Example prompt: Search Jentic for 'send a WhatsApp message', load the POST `/api/v1/messages` schema, and execute it with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/me` | Verify the key and get the workspace | | POST | `/api/v1/messages` | Send a WhatsApp text message | | POST | `/api/v1/ai/reply` | Generate an AI reply from business content | ## Key resources - **Messages** — Send a WhatsApp text message from the workspace number via `/api/v1/messages` - **AI reply** — Generate an AI reply from business content via `/api/v1/ai/reply` - **Workspace** — Verify the API key and read its workspace via `/api/v1/me` ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 64 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 68 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/cresclab.com/cresclab/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring CAAC Go by hand means managing its workspace bearer key and threading it through each message-send and AI-reply call. Through Jentic you install once, import CAAC Go from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** CAAC Go carries the recipient inside the request body, so rules bound which operations your agent may call, not which contact it can reach. You choose the operations it may call, so message sending and AI-reply drafting can be allowed while the key-verification read stays separate. - **Credential handling:** Your CAAC Go key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a WhatsApp message' or 'generate an AI reply', and Jentic returns the matching CAAC Go operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Gupshup** — Conversational messaging platform with WhatsApp Business support - **WHAPI** — WhatsApp API with session-based message sending - **Sinch** — Multichannel messaging across SMS, WhatsApp, and voice ## FAQ ### What authentication does the CAAC Go Developer API use? The CAAC Go Developer API authenticates with a workspace API key (cwa_...) sent as a bearer token in the Authorization header, per its OpenAPI spec. The identity operation confirms which workspace a key belongs to. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent. ### Can I send a WhatsApp message with the CAAC Go Developer API? Yes. The messages operation sends a WhatsApp text from the workspace's connected number, so an agent supplies the recipient and content and CAAC Go handles delivery. You can pair it with the AI-reply operation to draft the message before sending. ### What are the rate limits for the CAAC Go Developer API? The OpenAPI spec does not publish specific rate-limit numbers; check https://caacgo.cresclab.com for current details. The identity operation confirms the active workspace, which is a cheap preflight before an agent sends a batch of messages. ### Is there a CAAC Go MCP server? You don't need an MCP server to give your agent CAAC Go. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the message and AI-reply operations. Nothing extra is loaded into the agent's context until an operation is actually invoked. ### Can I limit what my agent is allowed to do with the CAAC Go Developer API? Yes. CAAC Go carries the recipient inside the request body, so rules bound which operations your agent may call rather than which contact it can reach. Allow only the message-send and AI-reply operations and the key-verification read stays separate, with every call logged by your own Jentic One instance. ### How do I send a WhatsApp message with the CAAC Go Developer API through Jentic? Search Jentic for 'send a WhatsApp message', and it returns the CAAC Go message operation with its input schema. Load the schema and execute POST `/api/v1/messages` with the recipient and content, with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.