---
name: vcorp-super-agent
description: Hand work to the user's VCorp Super Agent, which does it in the cloud and on the user's own devices - make a finished video, do things on websites with the user's logins (research, forms, messages), operate desktop apps or their phone, post to social platforms, build and publish a landing page or web game, lay out a PCB in EasyEDA, design a 3D-printable part, or watch something on a schedule. Needs the vcorp-super-agent MCP server (https://maker-dev-test.vcorp.ai/mcp) or an OVM_API_KEY for its REST API.
---

# Handing a task to VCorp Super Agent

A task takes minutes to an hour and spends the user's credits, which they paid for, so be deliberate. It acts as the user, with their devices and logins: the devices still ask the user before sends and payments unless they turned that off.

## Before creating

- `get_capabilities` once: which `kind`s this server runs and what each delivers. Pick the kind by the result the user wants (a video, a report from websites, a live page, a part...).
- Write the whole task in `prompt`: goal, sites or apps involved, what to deliver, must-haves, how to use each attachment. One clear task beats a round of follow-ups.
- For work on the user's devices, `list_devices` shows what is online. Use `device_id` only if the user named a device.
- Video: pick `aspect` (9:16 for phone/social), `duration_seconds`, `voice`. Landing page or game: `slug` if the user wants a particular subdomain.
- Small files go in `files` as base64 (20 MB total); large material and web pages go in `links`.
- Set `budget` (credits) if the user named a spend limit. If unsure the account can pay, call `get_account` first.
- Always pass a `client_request_id` (any unique string) and reuse it if you retry, so a timeout never starts a second, billed task.
- `review: true` only if the user wants to see the plan first. A publish task always stops for approval before posting.
- Something to check again and again (new messages, prices, a queue): `kind: browse` with `repeat` and a `daily_cap` (credits) the user agreed to.

## While it runs

- Tell the user the `job_id` and that it takes a while.
- Call `wait_for_task` repeatedly while `status` is queued, planning or rendering; it returns within a minute. Follow the `next` field.
- If your session cannot stay open, stop polling: the task keeps running. Next time, `get_task` (or `list_tasks`) picks it up.
- In an automated pipeline, pass `callback_url` instead of polling (see https://maker-dev-test.vcorp.ai/docs/agents.md#webhooks).

## Outcomes

- `awaiting_approval`: read `report` (the plan); for a video, look at the contact sheet attached as an image. `approve_task`, or `send_message` with concrete changes.
- `done`: give the user the result: `report` and `files`, `video_url` for a video, `site_url` for a site (links valid 7 days; `get_task` refreshes them). For changes or the next step, `send_message` in the same task; it keeps its context.
- `failed` / `interrupted`: read `error`. A credits or budget problem needs the user (or `budget` on continue); otherwise `continue_task` once. Don't loop on failures.
- Never create a new task to "retry" a failed one; continue it. To build on a finished one with a different kind of work, create a task with `refs`.
- A repeating task that paused itself usually needs the user (see `repeat.paused_reason`); `repeat_task resume` after they fixed it.
- Beyond the deliverables, `list_task_files` / `read_task_file` show a task's notes, drafts and intermediate files.

## The user's library and profile

- `library_list` / `library_read` browse their files; `library_upload` puts material under `/shared` for later tasks (name the path in the prompt).
- `get_profile` before a task tells you their standing defaults (voice, brand, closing card); don't repeat those in the prompt.
- Change the profile only when the user asks: `get_profile`, edit that text, `update_profile` with its `base`. On a 409, read it again and redo the edit.

## Without MCP

The same operations exist as REST under https://maker-dev-test.vcorp.ai/v1 with `Authorization: Bearer $OVM_API_KEY`; see https://maker-dev-test.vcorp.ai/openapi.json.
