Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Copy HTTP Endpoint, 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%2Fsanity.io%2Fsanity-copy" | 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%2Fsanity.io%2Fsanity-copy" | 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 Copy HTTP Endpoint API.
Clone a dataset in the cloud with copyDataset by naming a new targetDataset
Leave document history out of the copy with skipHistory
Skip content releases and their document versions with skipContentReleases
List a project's dataset copy jobs newest first with listCopyJobs, filtered by state such as pending or running
GET STARTED
Read each job's sourceDataset, targetDataset, withHistory, and timestamps to confirm what was copied
Patterns agents use Copy HTTP Endpoint API for, with concrete tasks.
★ AI agent safe sandbox setup
Before an agent runs a bulk content change, it is safer to work on a clone. Through Jentic the agent searches for 'copy a Sanity dataset', loads the copyDataset operation, and sends a targetDataset for the source dataset while the Sanity token is injected at call time. It keeps the returned jobId to confirm the clone finished before starting work.
PUT /projects/abcd1234/datasets/production/copy with targetDataset production-sandbox and skipHistory true, then return the jobId
Pre-migration snapshot
Schema migrations are easier to roll back with a copy of the dataset taken just before. Cloud Clone duplicates the dataset inside Sanity without downloading it, copies content releases unless skipContentReleases is set, and returns 409 if a dataset with the target name already exists.
PUT /projects/abcd1234/datasets/production/copy with targetDataset production-pre-migration and skipContentReleases false
Copy job monitoring
Large copies run as background jobs. Listing copy jobs with state=pending,running shows what is still in progress, newest first, and each job reports its sourceDataset, targetDataset, whether history was included, and when it was created and last updated.
GET /projects/abcd1234/datasets/copy with state pending,running and limit 20, and report each job's id and targetDataset
2 endpoints — the sanity copy api, also known as cloud clone, copies an existing dataset into a new dataset inside sanity's cloud, as an alternative to exporting and re-importing it.
METHOD
PATH
DESCRIPTION
/projects/{projectId}/datasets/{dataset}/copy
Copy a dataset into a new dataset
/projects/{projectId}/datasets/copy
List copy jobs
/projects/{projectId}/datasets/{dataset}/copy
Copy a dataset into a new dataset
/projects/{projectId}/datasets/copy
List copy jobs
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Sanity Copy API by hand means templating the apiVersion into the host, sending a bearer token with the create grant on sanity.project.datasets, and handling the 400, 402, and 409 cases for plan, quota, and name clashes. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.
Permission scoping
The project and source dataset sit in the URL path (/projects/{projectId}/datasets/{dataset}/copy), so a rule can pin your agent to one project and one source dataset. The targetDataset travels in the request body, so a rule bounds what may be copied, not what the new dataset is called.
Credential isolation
Your Sanity token 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 'copy a Sanity dataset' or 'list Sanity copy jobs', and Jentic returns the matching operation with its path parameters and body schema.
Alternatives and complements available in the Jentic catalogue.
Specific to using Copy HTTP Endpoint API through Jentic.
What authentication does the Sanity Copy API use?
Per its OpenAPI spec, the Sanity Copy API uses bearer authentication with a Sanity token in the Authorization header. Starting a copy needs the create grant on sanity.project.datasets, and a missing grant returns 401 with code missing_grant; listing jobs needs the read grant. Through Jentic the token is stored by your own instance and attached at call time.
Is the Sanity Copy API free?
Copying a dataset is part of Sanity's Advanced Dataset Management offering on the enterprise plan, and projects without it get a 400 error. Listing copy jobs does not require that feature. A project at its dataset quota gets a 402 Quota exceeded error.
How do I check whether a Sanity dataset copy has finished?
Use the jobId returned by the copy request with Sanity's Jobs API, or list the project's copy jobs and check each job's state, which is one of pending, running, completed, failed, terminating, or terminated.
What are the rate limits for the Sanity Copy API?
The OpenAPI spec does not specify rate limits. It does return 409 if a copy from the same source to the same targetDataset is already in progress. Check https://www.sanity.io/docs for current API limits.
Is there a Sanity Copy MCP server?
You don't need an MCP server to give your agent the Sanity Copy API. Jentic connects it directly from the API Directory: import it, store your Sanity token once, and your agent calls the copy or job-listing operation when needed.
How do I clone a Sanity dataset through Jentic?
Search Jentic for 'copy a Sanity dataset', load the copyDataset operation, and execute PUT /projects/{projectId}/datasets/{dataset}/copy with a targetDataset in the body. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Sanity Copy API?
Yes. Allow only GET /projects/abcd1234/datasets/copy and the agent can report on copy jobs for that one project without starting any new copies, which count toward your dataset quota. Every call it makes is logged.
For Agents
Clone a Sanity dataset into a new dataset in the cloud, with or without history and content releases, and list a project's copy jobs by state.
Use for: Clone production into a staging dataset before the migration, Make a copy of the blog dataset without its history, Check whether my dataset copy has finished, List all copy jobs that are still running
Not supported: Does not export documents to files, restore backups, or delete datasets. Use for cloning a Sanity dataset in the cloud and listing copy jobs only.
The Sanity Copy API, also known as Cloud Clone, copies an existing dataset into a new dataset inside Sanity's cloud, as an alternative to exporting and re-importing it. A copy request names the targetDataset and can leave out document history with skipHistory or content releases with skipContentReleases; scheduled releases arrive unscheduled in the copy. Starting a copy returns a jobId whose progress you follow through the Jobs API, and a second operation lists a project's copy jobs newest first, filtered by state. Copying is part of the Advanced Dataset Management offering on Sanity's enterprise plan, while listing jobs is not.
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>