Check your environment and choose a client
- The installer requires Node.js 18 or newer.
- Using PoYo CLI requires Node.js 20 or newer.
Coding client
Install poyo-ai-models in your coding agent, connect PoYo through MCP or CLI, and give the agent a reliable path from live model discovery to final delivery.
$npx skills add PoyoAPI/poyo-devtools --skill poyo-ai-modelsBuilt for coding agents such as Codex, Claude Code, Cursor, and GitHub Copilot. Not using a coding agent? Open the PoYo creation platform
Choose your client and install scope, configure the API key, then run a read-only verification.
Coding client
Choose your coding client and let the guide generate the exact project or global command.
Choose where to install
Choose a client first to generate a safe, deterministic command.After installation, reload or restart the client so it can discover the Skill.
Use an environment variable or your client's secret manager. Never put the key in a prompt or repository.
Open API KeysConfigure your API key
$export POYO_API_KEY="your_api_key"This command only affects the current terminal session. Use your client's secret manager for a persistent setup, and never commit the key.
Ask the agent to confirm the Skill and execution path, then query only models, input requirements, and public pricing.
Confirm that the poyo-ai-models Skill is loaded and state whether you will execute through PoYo hosted MCP or PoYo CLI. Only query currently available image models, input requirements, and public pricing. Do not submit a paid task.What the agent should confirm
Every example asks the agent to compare current capabilities and pricing before submitting against the real schema.
Agent request / video
“Turn this product image into a five-second ecommerce showcase with a slow push-in and no subject distortion. Compare image-to-video models and pricing before execution.”
One compact operating guide covers the four decisions that most often cause model tasks to fail.
Search the current catalog by task intent instead of inventing model IDs from memory.
catalog search
Inspect live schemas, required fields, and public pricing before execution.
schema + pricing
Use MCP for agent interaction and the PoYo CLI for scripts and CI jobs.
MCP / CLI
Save task_id and distinguish waiting, success, and failure while polling.
check job
The agent moves from discovery to live schema checks, selects an execution path, preserves task state, and reports usable results.
The Skill never replaces PoYo's live catalog, pricing, or task status. It teaches the agent when and how to read them.
The agent must accurately distinguish pending, running, succeeded, and failed.
Check balance and status, and preserve idempotency data and task_id to reduce duplicate charges.
After installation, agents still choose MCP or CLI for the environment. Your application services continue to use the REST API directly.
Agent conversations and coding clients
Reasoning, discovery, and execution happen together
Explore MCPTerminals, scripts, and CI
Reproducible commands, batches, and automation
View GitHubProduct backends and stable application traffic
Direct integration, queue control, or token streaming
Read docsThe most common questions, answered with the real product boundaries.
Still have a question? Contact PoYo support→
Create an API key, install the official Skill, and describe the outcome. One verifiable workflow handles model selection, parameter checks, and long-job recovery.