Codia Open API
Install Codia Open API tools into your AI coding agents
Give Codex, Claude, Cursor, and local agent workflows one CLI for image-to-design, PDF-to-design, PDF-to-PPT, background removal, image generation, SVG conversion, credits, and usage.
Platforms
One package, multiple agent surfaces
Install the same Codia API wrapper where your team already works.
Codex
Add Codia image, PDF, and design APIs to Codex skills with local authentication.
Claude
Package the same commands as reusable Claude skills for design automation tasks.
Cursor
Expose Codia API commands inside Cursor rules for coding and design-to-code workflows.
Capabilities
Design APIs packaged for agent execution
The CLI handles auth, uploads, API calls, and JSON output so agents can focus on the user task.
Image to design
Convert screenshots and UI images into structured, editable design data.
PDF to design
Extract page layouts, text, and visual structure from PDF files.
PDF to PPT
Generate editable PowerPoint output from image PDFs and document pages.
Remove background
Create clean cutouts for products, portraits, and creative assets.
Image generation
Generate, upscale, edit, remix, and describe images through Codia endpoints.
SVG conversion
Turn image assets into scalable SVG output for design and development.
Results
Clear inputs, agent-readable outputs
Each command makes the API call explicit and returns structured output that an agent can continue using.
Input
screenshot.png
Command
image-to-design --out design.json
Output
Editable design JSON
Input
deck.pdf
Command
pdf-to-ppt --poll --out deck.json
Output
PPTX download URL
Input
product.png
Command
remove-bg --out cutout.json
Output
Transparent asset URL
Install
A short setup that ends with a live balance check
Install the CLI, bind an Open API key, install templates for Codex, Claude, Cursor, then verify that your credits are reachable.
Install the CLI
Use npm to install the cross-platform codia-design command.
Bind your API access
Use browser login when available, or bind an existing Codia Open API key directly.
Install skill templates
Copy platform-specific skill files into Codex, Claude, Cursor, or all targets.
$ npm install -g @codia/design-skills$ codia-design auth set --api-key api_key_xxx$ codia-design install --platform all$ codia-design credits
Billing
One Open API credits balance for every command
Codia Open API uses the unified Open API credits SKU. Users buy or subscribe once, then spend the same balance across every public API capability.
Unified SKU
Image, PDF, PPT, SVG, and background removal APIs share the same balance.
Usage visibility
Check remaining credits and call-level usage from the CLI or dashboard.
Auto recharge
Optional recharge settings can keep production agent workflows from stopping.
codia-design creditscodia-design usage --page 1 --page_size 20codia-design auto-recharge set --enabled true --threshold 100 --credits 1000 --monthly_max 5000
Workflows
Agent-ready commands for common design tasks
Each command returns structured JSON and can write large responses to a file for follow-up agent steps.
codia-design image-to-design
Turn a UI screenshot into DSL
Agents can inspect a screenshot, call Codia, and use the returned design structure for code or deck generation.
codia-design pdf-to-ppt --poll
Convert PDFs into editable slides
Long-running conversion tasks can be polled from the CLI and stored as reusable output.
codia-design remove-bg
Prepare product and creative assets
Local files are uploaded automatically, then the result can flow into design or content pipelines.
FAQ
What teams need to know
The skills are a thin, local packaging layer over Codia Open API.
Do I need a Codia API key?
Yes. Use browser login when device-flow auth is available, or run codia-design auth set --api-key with an existing Open API key.
Which platforms are supported?
The package ships templates for Codex, Claude, and Cursor, with one CLI powering all platforms.
Are credits shared across APIs?
Yes. Public Open API calls spend from the unified Codia Open API balance.
Can agents use local image and PDF files?
Yes. The CLI uploads supported local files before calling the target endpoint.
Is this different from the REST API?
It wraps the same Codia Open API endpoints in commands and skill instructions that local AI agents can use safely.
Give your agent a design API toolbelt
Create an API key, install the skill package, and let your local agent call Codia APIs from the same workflow where it writes code and documents.