Build your way.
Connect your agent, CLI, MCP or API.
Developer reference
- HTTP API
Call the hosted API with a bearer key: the session API, the twelve tools, quotes, identity, files and webhooks, with limits and billing.
- API and MCP capability map
Which endpoint, MCP tool, CLI command and scope does each job: the hosted agent, the twelve tools, files, webhooks and workspace settings.
- Documentation versions and change context
What changed in the developer docs, which contract versions they describe, and how to tell what the service you call supports.
- Native CLI
Sign in from a terminal, call the twelve tools, move verified files and run hosted productions with the wavemaker CLI. The CLI has no public release yet.
- Quote and run work
Price a tool call, submit it once with a request_id, follow the job it returns, and cancel or recover safely.
- Errors, limits and safe retries
Every error code with its HTTP status and whether to retry, the limits behind them, and how to retry without duplicating work.
- Graph portability and explicit dependencies
Submit plain Comfy API graphs, name media and models by content-addressed identity, keep credentials out, and know what validation rejects.
- Make an ad through the session API
Create a hosted agent session, post a brief with attachments and deliverables, follow events, then download and verify each delivery.
- Client credentials and provider keys
Create, check, replace and revoke Wavemaker developer credentials, sign in with OAuth, and save your own provider keys so those models bill your provider account.
- Connect an external agent with MCP
Connect an external agent host to the hosted MCP endpoint and use the twelve tools.
- Connect to Wavemaker
The session API, the twelve tools over HTTP and MCP, and the CLI reach the same workspace and credits. Start here for auth, base URLs, a first request and how billing applies.
- Python, TypeScript and Go clients
The Python, TypeScript and Go clients are not on a public registry yet. Until they are, call the HTTP API or MCP.
- Standalone starter apps
Six small starters invert an owned still with one generate call over HTTP, MCP, the CLI, Python, Go or a local Node page, and never send the work twice after a crash.
Developers
- Account and workspace API access
Read identity, usage and credits, set the workspace model policy, manage webhooks and provider connections over the API, and see what stays in the web app.