Makeswift REST
50
AI ReadinessFoundational (D+)50/100
Official vendor OpenAPI document · agent-readyMarketingContent ManagementapiKey29 EndpointsREST
For Agents
Create and duplicate Makeswift sites, add locales, create and update pages by pathname, and manage the swatches, typographies, and regions a site uses.
Use for: Create a new Makeswift page at /pricing, List all pages under the /blog path prefix, Duplicate our marketing site for a new brand, Add a German locale to the site with its own domain
Not supported: Does not handle hosting deployments, form submissions, analytics, or blog CMS entries. Use for managing Makeswift sites, locales, pages, and design tokens only.
The Makeswift REST API manages the sites, pages, and design system behind Makeswift visual websites. It creates, updates, duplicates, and deletes sites in a workspace, adds and restores locales with their own domains, and creates pages by pathname with an optional element tree. It also reads pages from a version reference such as the draft, lists pages by path prefix or locale, and maintains the color swatches, typographies, and beta reusable regions that a site's design draws on.
Install Jentic One Beta
Connect the REST to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the REST, 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.
1
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%2Fmakeswift.com%2Fmakeswift" | sh2
Step 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%2Fmakeswift.com%2Fmakeswift" | 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.
Capabilities
What an agent can do with REST API.
Create a site in a workspace with a name, hostOrigin, and defaultLocale, or duplicate an existing site with all its content
Add a locale to a site with its own domain, and restore a deleted locale
Create a page from a siteId, pathname, and name, optionally passing an elements tree
List a site's pages filtered by pathPrefix or locale, sorted with sortBy and sortDirection, and including offline pages on request
Read a page by ID or pathname from a versionRef such as ref:draft, with its elements when include is set
Define brand colors as swatches from hue, saturation, and lightness, and text styles as typographies
Create reusable regions from an element tree, a beta feature enabled per site or workspace
Use Cases
Patterns agents use REST API for, with concrete tasks.
★ Agent-managed site pages through Jentic
A content agent creates landing pages by pathname, lists existing pages under a prefix to avoid clashes, and updates page names as campaigns change. Through Jentic the agent finds the page operations by intent, the Makeswift x-api-key stays in the developer's own Jentic One instance, and a rule can hold the agent to page reads and edits while site deletion and duplication stay out.
Call GET /v6/pages with siteId and pathPrefix '/campaigns' to check for clashes, then POST /v6/pages with siteId, pathname '/campaigns/spring', and name 'Spring campaign'
Site rollout for a new brand or market
Launching a copy of an existing site starts with POST /v2/sites/{siteId}/duplicate and a new name, which copies all content and configuration. POST /v2/locales then adds a locale such as de-DE with its own domain, so the duplicated site can serve a new market without rebuilding pages by hand.
POST /v2/sites/{siteId}/duplicate with name 'Acme EU', then POST /v2/locales with the new siteId, locale 'de-DE', and domain 'acme.de'
Design system sync
Brand colors and type styles live as swatches and typographies on each site. POST /v4/swatches takes siteId, hue, saturation, and lightness, and POST /v4/typographies takes siteId, name, and style, so a design token source can push brand updates into Makeswift and keep sites consistent.
POST /v4/swatches with siteId, name 'Brand blue', hue 215, saturation 80, and lightness 45, then GET /v4/swatches with siteId to confirm it is listed
Key Endpoints
29 endpoints — the makeswift rest api manages the sites, pages, and design system behind makeswift visual websites.
METHOD
PATH
DESCRIPTION
POST
/v2/sites
Create a site
POST
/v2/sites/{siteId}/duplicate
Duplicate a site
POST
/v2/locales
Create a locale
POST
/v6/pages
Create a page
GET
/v6/pages
List pages for a site
GET
/v6/pages/{pageIdOrPathname}
Get a page by ID or pathname
PATCH
/v6/pages/{pageIdOrPathname}
Update a page
POST
/v4/swatches
Create a swatch
POST
/v2/sites
Create a site
POST
/v2/sites/{siteId}/duplicate
Duplicate a site
POST
/v2/locales
Create a locale
POST
/v6/pages
Create a page
GET
/v6/pages
List pages for a site
GET
/v6/pages/{pageIdOrPathname}
Get a page by ID or pathname
PATCH
/v6/pages/{pageIdOrPathname}
Update a page
POST
/v4/swatches
Create a swatch
Jentic AI Readiness Score
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.
R
REST
- Foundational (D+)50/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility26
AI-Readiness & Agent Experience94
Agent Usability50
Security77
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
26
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
39%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
66%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
77
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
77%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Makeswift by hand means choosing between an App API key and a Site API key, sending it in the x-api-key header, and handling cursor pagination with startingAfter across versioned endpoints yourself. Through Jentic you install once, import Makeswift from the API Directory, store the key once, and your agent calls it.
Permission scoping
Makeswift puts the site ID and page ID in the URL path for site and page operations, so a rule can pin your agent to one site or one page and the operations you pick. You choose the operations it may call, so destructive ones like DELETE /v2/sites/{siteId} or page deletion are not included unless you add them.
Credential isolation
Your Makeswift 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 'create a page' or 'add a locale to a site', and Jentic returns the matching Makeswift operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using REST API through Jentic.
Is there a Makeswift MCP server?
You don't need an MCP server to give your agent Makeswift. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.
What authentication does the Makeswift REST API use?
Per its OpenAPI spec, the Makeswift REST API takes an API key in the x-api-key header. It accepts either an App API key, which starts with sk_, or a Site API key in UUID format. 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 context.
Can I limit what my agent is allowed to do with Makeswift?
Yes. For example, write a rule that allows GET and PATCH on /v6/pages/{pageIdOrPathname} for one page ID, so the agent can read and update that page but cannot create new pages, delete sites, or duplicate them. Every call it makes is logged on your own machine.
Can I read the draft version of a page?
Yes. GET /v6/pages/{pageIdOrPathname} takes a versionRef parameter that defaults to ref:draft, a locale parameter that accepts a locale code such as en-US, and an include parameter that can add the page's elements to the response. When you address a page by pathname, also pass siteId.
How do I create a page through Jentic?
Install Jentic One, import the Makeswift REST API from the directory, and search for 'create a Makeswift page'. Jentic returns the Create Page operation with its input schema; your agent sends siteId, pathname, and name, plus an optional elements tree. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Are Makeswift regions available on every site?
Regions are marked as a beta feature in the spec. Region requests return 403 until the feature flag is enabled for your site or workspace, and a region in a non-default locale needs to exist in the default locale first.
What are the rate limits for the Makeswift REST API?
The OpenAPI spec does not specify rate limits. Check the Makeswift documentation at https://docs.makeswift.com for current limits.
GET STARTED