Agents, built over MCP.
You do not write WaveAssist agents by hand. Your coding agent does, over MCP. This section is how that works, end to end.
Overview
WaveAssist connects to your editor over MCP. You describe a recurring job in plain English; your coding agent (Claude Code, Cursor, any MCP host) designs the pipeline, deploys it to WaveAssist, runs it once on real infrastructure, and arms the schedule only after that run passes.
The model does the thinking once, at build time. After that the agent runs as codified Python, with the model contained to wrapped, schema-locked calls. Same structure every run. The platform page covers the determinism model in depth.
Connect & keys
Auth is a rotatable mcp_token, separate from your UID. Get it from the Connect MCP panel at app.waveassist.io, then hand it to your editor as a bearer token. Regenerate it anytime without touching your identity or other keys.
Building an agent
Once connected, you build by asking. Name the sources, the job, and the schedule in one request. Your coding agent handles the wiring, writes the pipeline against the SDK, and deploys it.
"Using WaveAssist, build an agent that reads my ClickUp and emails me a Monday morning summary of last week."
It then runs a verify pass on live infrastructure. If it passes, the schedule arms. If it fails, it holds, so a broken agent never goes live unattended.
Examples
Each of these is a single request. The agent designs, tests, and schedules the rest.
“Connect my ClickUp and Slack. Every Monday at 9am, summarize last week's completed tasks and post it to #general.”
Reads ClickUp, summarizes with a schema-locked call, posts to Slack. Runs a test post, then arms the weekly schedule.
“Review every new pull request on my repo and post a risk level with inline comments.”
On each PR webhook, reads the diff, calls the model with a fixed schema, and posts a structured review.
“Every morning at 8am, email me a digest of yesterday's signups and revenue.”
Pulls the numbers, renders a briefing, and emails it on a daily schedule.
Credits
Every account starts with $2 of runtime credit. After that, credits are prepaid and pay-as-you-go, no tiers and no subscription. A run consumes a fraction of a cent: the model tokens for any wrapped calls, plus the runtime.
You add credits from the same dashboard as your token. Balance and usage live on the WaveAssist Credits page.