Docs navigation

Recipes

End-to-end worked examples for agents and scripts.

Each recipe is copy-paste runnable. All commands take --output json; set IPBOT_API_KEY and (for user-scoped steps) IPBOT_USER_ID first — see Authentication.

1. Run a free Power

The fastest end-to-end check — no connectors, no Winds:

bash

> npx @island-pitch/ip-bot-cli powers list --output json
> npx @island-pitch/ip-bot-cli powers run power-qr-code-generator \
>   --input '{"data":"https://islandpitch.bot"}' --output json

2. Photo → draft → review → schedule → publish

The full content pipeline with a human approval gate before anything publishes:

bash

> export SUB=$(npx @island-pitch/ip-bot-cli auth whoami --output json | jq -r .userId)
> 
> # 1. Turn an image into a draft
> DRAFT=$(npx @island-pitch/ip-bot-cli content create --type social_post --platform instagram \
>   --excerpt "New drop ☀️" --user-id $SUB --output json | jq -r .draftId)
> 
> # 2. Submit for review, then approve (needs a reviewer; --allow-self-review for solo)
> npx @island-pitch/ip-bot-cli content submit  $DRAFT --user-id $SUB
> npx @island-pitch/ip-bot-cli content approve $DRAFT --user-id $SUB --allow-self-review --output json
> 
> # 3. Schedule, then wait for the terminal state
> SCHED=$(npx @island-pitch/ip-bot-cli content schedule $DRAFT --at "in 10 minutes" --output json | jq -r .scheduleId)
> npx @island-pitch/ip-bot-cli calendar wait $SCHED --output json

Check the result with calendar get $SCHED; on failure see Troubleshooting (and schedule debug $SCHED for the failure category).

3. Drive it from an agent (MCP)

With the MCP server wired up, the same flow is tool calls: list_powers → get_winds_balance → run_power, or create_content_draft → submit_for_review → approve_draft → schedule_publication → wait_for_schedule. The Powers skill teaches this loop.