For Agents
Read and write product copy in a Ditto workspace: manage components, text items, projects, variants, variables, and style guides, and track workspace activity.
Use for: Fetch all text items in a project, Create a new text component in our workspace, Update the copy for a text item, List the projects in our Ditto workspace
Not supported: Does not handle website hosting, image or media assets, or code deployment. Use for managing and publishing product copy and text content only.
The Ditto API reads and writes the product copy stored in a Ditto workspace. It manages reusable text components and the text items inside projects and project blocks, publishes text items to the component library, and links them to Figma nodes. Variants and variables let you localize and vary copy, style guides and their rules enforce tone, and the activity feed tracks every change.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ditto 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdittowords.com%2Fdittowords" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdittowords.com%2Fdittowords" | 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 Ditto API.
Fetch, create, and update reusable text components in a workspace
Read, create, and export the text items inside projects and project blocks
Publish a text item to the component library and link text items to a component
Manage variants and variables to localize or vary copy
Apply style guides and style-guide rules across a workspace
Link text items to Figma nodes for design handoff
Read the workspace activity feed to track copy changes
Patterns agents use Ditto API for, with concrete tasks.
★ Agent-Synced Product Copy
An AI agent connected through Jentic fetches the latest text items for a project, applies edits, and writes them back so the app build always uses approved copy. The Ditto API exposes the text-item and component operations the agent needs, and Jentic injects the API key at call time.
Fetch the text items for a project, update three strings with approved copy, and export the project's text items
Localization and Variants
Teams shipping multiple languages maintain variants of each string and resolve variables at build time. The Ditto API creates and updates variants and variables so a localization workflow stays in sync with the source copy.
Create a new variant for a set of text items and update the variables they reference
Style Guide Enforcement
Content teams codify tone and wording in style guides and rules. The Ditto API creates and updates style guides and their rules, so an agent can keep copy aligned with the team's standards across projects.
Create a style guide, add two style-guide rules to it, and fetch the components affected
41 endpoints — the ditto api reads and writes the product copy stored in a ditto workspace.
METHOD
PATH
DESCRIPTION
/components
Fetch components
/components
Create components
/textItems
Fetch text items
/textItems
Create text items
/projects
Fetch projects
/variants
Fetch variants
/styleguides
Get style guides
/activity
Fetch workspace activity
/components
Fetch components
/components
Create components
/textItems
Fetch text items
/textItems
Create text items
/projects
Fetch projects
/variants
Fetch variants
/styleguides
Get style guides
/activity
Fetch workspace activity
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring Ditto by hand means managing its `Authorization` header API key and threading workspace, project, and component ids through the right calls yourself. Through Jentic you install once, import Ditto from the API Directory, store the key once, and your agent calls it.
Permission scoping
Ditto carries the component, project, and text-item ids in the request body or query rather than the URL path, so rules bound which operations your agent may call, not which project. Limit the agent to the operations it needs, such as fetching and creating text items, so deletes are not included unless you add them.
Credential isolation
Your Ditto API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'fetch text items' or 'publish a text component', and Jentic returns the matching Ditto operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Ditto API through Jentic.
What authentication does the Ditto API use?
The Ditto API authenticates with an API key sent in the `Authorization` request header, per its OpenAPI spec. Create the key in your Ditto workspace settings and send it on every call. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.
Can I read and write product copy with the Ditto API?
Yes. The API fetches and creates text components and text items, organizes them into projects and project blocks, publishes items to the component library, and manages variants, variables, and style guides. It also exposes a workspace activity feed so you can track changes.
Is there a Ditto MCP server?
You don't need an MCP server to give your agent the Ditto API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the component and text-item operations. Operations load on demand, so your agent's context stays lean instead of holding another server's tool definitions.
Can I limit what my agent is allowed to do with the Ditto API?
Yes. Write a rule that allows only the fetch and create operations for components and text items, so the agent can read and add copy but cannot delete components, variants, or style-guide rules. Every call the agent makes is logged.
What are the rate limits for the Ditto API?
The OpenAPI spec does not specify rate limits. Check the Ditto developer documentation at https://developer.dittowords.com for current limits before running large export or sync jobs.
How do I sync text items with the Ditto API through Jentic?
Search Jentic for an intent like 'fetch text items', add the Ditto API from the directory, and store your API key once. Your agent then calls the fetch, create, and export operations for the project you choose. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED