Skip to main content
YCloud Developer Kit helps your AI coding agent plan integrations, generate server-side code, and test workflows in your existing project. Describe what you want to build, such as WhatsApp order notifications, appointment reminders, or customer support, and the agent uses YCloud API contracts to guide the work. You can also ask the agent to review an existing integration or perform a specific live API operation with your configured server-side credentials.

Before you begin

For installation and local development, you need:
  • Codex, Claude Code, or WorkBuddy.
  • Node.js and npx available in your terminal.
  • The project where you want to build your integration.
You do not need a YCloud API key for the installation check or tests that use mocks. For live API requests, you need a YCloud account, a server-side API key, and the resources required by your workflow. See Authentication for credential setup.

Install the skills

Run the command for your coding agent from your project directory. Each command installs the full set of 17 skills in that project.
To choose your coding agent interactively, run:
You can find versioned plugin ZIP packages and checksums on the official releases page.

Check the installation

Start a new session in your coding agent and send:
The expected response is:
This check confirms that the agent can discover and invoke the readiness skill. It does not read credentials, call YCloud, or validate your account configuration. If the agent cannot find the skill, confirm that you ran the installation command in the correct project, selected the correct agent, and opened a new session for that project.

Build your first integration

Describe your business goal, project stack, and the result you need. Start with ycloud-integration-architect when the workflow spans several capabilities, such as templates, message sending, and webhooks. For example, send this prompt from your application project:
The agent uses the relevant domain skills for your selected workflow. Review the generated code and test results, then configure the required YCloud resources before requesting a live test. Give the agent the following context when it is relevant: Reference credentials through your server configuration or secret manager. Do not paste API keys or webhook signing secrets into prompts.

What the kit covers

Version 0.7.13 includes 17 skills covering 88 API operations, plus API authentication and webhook receiving. The table groups the domain skills by the work you can request. The remaining two skills are ycloud-integration-architect, which coordinates workflows across domains, and ycloud-developer-kit-smoke-test, which checks installation readiness.
This release does not cover SMS, Verify, Voice, or Email integrations. Those products remain available through YCloud APIs. Use their API guides and reference pages for integration details.

More example prompts

Add inbound messages and webhooks

Review an existing integration

Request a live read

Local tests and live operations

Local mock tests let you check application behavior with synthetic data. A passing mock test does not confirm live authentication, message delivery, or production deployment. For live operations, specify the account, environment, target resources, and action. The agent uses the configured credentials within that scope. It asks for missing details when the target or effects are unclear. A request to develop code locally does not authorize unrelated live changes. For message sends and other asynchronous operations, distinguish an accepted request from its final outcome. Verify delivery or completion through the relevant retrieval API or webhook. If a live change times out, check the available resource state before retrying.

Next steps

Send a WhatsApp message

Prepare message templates, payloads, and delivery handling.

Configure webhooks

Connect your application to inbound messages and status updates.