The Sanity Assets API uploads images and files into a dataset in Sanity's Content Lake and creates the matching sanity.imageAsset or sanity.fileAsset document with their metadata. Uploads can come from raw request bytes or from a public HTTPS URL that Sanity fetches itself, with optional title, description, label, credit line, and source attribution. Image uploads can extract metadata such as palette, lqip, blurhash, thumbhash, exif, and location. A separate operation links an existing Media Library asset to a dataset so it can be previewed and referenced from documents.
The Sanity Backups API turns backups on or off for a dataset, lists the backups that exist, and returns the files inside any one of them. Backup listings can be narrowed with after and before dates and return each backup's ID and creation time. Fetching a backup returns its total file count and a page of document, image, and file entries with signed download URLs that expire after 24 hours. It is the HTTP surface behind the sanity backups download command, which assembles those files into a tarball for sanity datasets import.
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.
The Sanity Export API streams every non-deleted document in a dataset as newline-delimited JSON, including drafts, release versions, and asset documents the caller can access. The export reflects the dataset as it was when the request started, and the types parameter narrows it to specific document types such as post, author, or sanity.imageAsset. For large datasets, cursor mode returns documents ordered by _id in time-boxed batches that end with a nextCursor object to resume from. An error after streaming begins keeps the 200 status and ends the stream with an error object, so the last line must be checked before an export counts as complete.
The Sanity Projects API administers Sanity projects and the datasets inside them. It lists, creates, updates, and deletes projects, and within a project creates datasets with a public, private, or custom ACL mode, updates or deletes them, copies one dataset into a new one, and lists the history of copy jobs. Projects also carry CORS origins, API tokens with assigned roles, tags that can be assigned to datasets, per-dataset embeddings index settings, active features, and the caller's own permissions. Role and permission management lives in Sanity's separate Access API.
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" | 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" | 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.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.