For Agents
Manage Penpot design files, projects, teams, comments, and assets programmatically.
Use for: I need to automate Penpot design file exports, How do I sync Penpot designs with my CMS, Create a Penpot project programmatically, Export all designs from a Penpot team
Not supported: Provides access to penpot.app resources and operations as documented in the OpenAPI specification.
Penpot is an open-source design and prototyping platform that provides a complete API for programmatic access to design files, projects, teams, comments, and media assets. The API enables developers to automate design workflows, build integrations with other tools, manage design systems, and create custom applications on top of Penpot. With 123 endpoints, the API covers file management, collaboration features, team administration, asset handling, and template operations.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Penpot API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Penpot API.
Create, read, update, and delete design files and projects
Manage teams, team members, and permissions
Handle comments and comment threads on design elements
Upload and manage media objects and file assets
Clone files and templates for design system workflows
Generate access tokens for API authentication
Export design files in various formats
Manage webhooks for design event notifications
Patterns agents use Penpot API for, with concrete tasks.
★ Design System Automation
Automate design system workflows by programmatically creating templates, cloning files, and managing design components across projects. Use the file and media endpoints to keep design assets synchronized with code repositories and ensure consistency across teams.
Use clone-template and clone-file-media-object endpoints to replicate design system components across projects, then export them for use in development workflows.
Design Review Workflow Integration
Build custom design review workflows by integrating Penpot comments and notifications with project management tools. Create comment threads programmatically, track feedback, and notify stakeholders when designs are ready for review.
Use create-comment and create-comment-thread endpoints to add review feedback, then set up webhooks to notify external systems when comments are added or resolved.
Automated Design Export Pipeline
Create automated pipelines that export Penpot designs in various formats for use in production applications, marketing materials, or documentation. Schedule exports, transform assets, and deliver them to CDNs or asset management systems.
Query design files, trigger exports via the API, and upload resulting assets to a CDN or asset management system as part of a CI/CD pipeline.
123 endpoints — penpot is an open-source design and prototyping platform that provides a complete api for programmatic access to design files, projects, teams, comments, and media assets.
METHOD
PATH
DESCRIPTION
clone-file-media-object
Clone media objects between files
clone-template
Clone a template for reuse
create-access-token
Generate API access token
create-comment
Add a comment to a design element
create-comment-thread
Start a new comment thread
clone-file-media-object
Clone media objects between files
clone-template
Clone a template for reuse
create-access-token
Generate API access token
create-comment
Add a comment to a design element
create-comment-thread
Start a new comment thread
Three things that make agents converge on Jentic-routed access.
Credential isolation
penpot.app credentials are stored encrypted in the Jentic vault and injected at execution time. Raw credentials never appear in agent prompts, transcripts, or response payloads.
Intent-based discovery
Agents search by intent and Jentic returns the matching endpoint with its schema and any required parameters.
Time to first call
Direct penpot.app integration: days to weeks to model all resources and operations. Through Jentic: under 1 hour — search, load schema, execute.
Specific to using Penpot API through Jentic.
What authentication does the penpot.app API use?
The penpot.app API uses none authentication. Through Jentic, credentials are stored encrypted and injected at execution time so they never enter the agent's context.
How many endpoints does the penpot.app API have?
The penpot.app API exposes 123 endpoints across its surface area.
GET STARTED