Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Webhooks 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-webhooks" | 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-webhooks" | 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 Webhooks HTTP Endpoint API.
Create a document webhook that fires on create, update, or delete for documents matching a GROQ rule.filter
Shape the outgoing payload with a GROQ rule.projection, and set httpMethod, headers, and a secret on document webhooks
Set up a transaction webhook that fires once per dataset transaction rather than once per document
Pause a webhook without deleting it by setting isDisabledByUser through the update operation
GET STARTED
List a webhook's messages with status such as queued, sending, success, failure, transientFailure, or canceled
Filter delivery attempts by state success or failure and read each attempt's resultCode, duration, and failureReason
Patterns agents use Webhooks HTTP Endpoint API for, with concrete tasks.
★ AI agent debugging failed webhook deliveries
When a site stops rebuilding after content edits, an agent searches Jentic for 'list failed Sanity webhook attempts', loads the listWebhookAttempts operation, and filters by state failure. It reads each attempt's resultCode, failureReason, and duration, then drills into a message's attempts to see whether the receiver is timing out or rejecting the payload, with the Sanity token injected at call time.
Call GET /hooks/projects/{projectId}/{id}/attempts for project abc123 and webhook hook_456 with state failure and limit 50, then summarize resultCode and failureReason
Rebuild a site when content is published
A static site needs a fresh build when certain documents change. A document webhook with rule.on set to create, update, and delete, a GROQ filter such as _type == 'post', and the build hook URL triggers a rebuild for matching changes in a chosen dataset, while a projection keeps the payload to the fields the build needs.
POST /hooks/projects/{projectId} with type document, name 'Rebuild site', url https://build.example.com/hook, dataset production, apiVersion v2025-02-19, and rule {on: ['create','update','delete'], filter: "_type == 'post'"}
Webhook housekeeping
Projects collect webhooks over time. Listing them shows each target URL and dataset, the update operation can rename a webhook, change its URL, or pause it with isDisabledByUser, and deleting removes ones that are no longer needed. Transaction webhooks reject document-only fields such as headers and secret on update.
Call GET /hooks/projects/{projectId} for project abc123, then PATCH /hooks/projects/{projectId}/{id} with isDisabledByUser true for any webhook pointing at a retired URL
9 endpoints — the sanity webhooks api sets up the webhooks that notify your services when content in a sanity project changes, and shows how each delivery went.
METHOD
PATH
DESCRIPTION
/hooks/projects/{projectId}
List all webhooks
/hooks/projects/{projectId}
Create a document or transaction webhook
/hooks/projects/{projectId}/{id}
Update or pause a webhook
/hooks/projects/{projectId}/{id}
Delete a webhook
/hooks/projects/{projectId}/{id}/messages
List webhook messages
/hooks/projects/{projectId}/{id}/attempts
List delivery attempts
/hooks/projects/{projectId}/{id}/messages/{messageId}/attempts
List attempts for one message
/hooks/projects/{projectId}
List all webhooks
/hooks/projects/{projectId}
Create a document or transaction webhook
/hooks/projects/{projectId}/{id}
Update or pause a webhook
/hooks/projects/{projectId}/{id}
Delete a webhook
/hooks/projects/{projectId}/{id}/messages
List webhook messages
/hooks/projects/{projectId}/{id}/attempts
List delivery attempts
/hooks/projects/{projectId}/{id}/messages/{messageId}/attempts
List attempts for one message
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Sanity Webhooks API by hand means templating the project ID and apiVersion into the host, sending a bearer token, and getting GROQ rule, projection, and apiVersion fields right on create. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.
Permission scoping
Sanity puts the project ID and the webhook id in the URL path (/hooks/projects/{projectId}/{id}), so a rule can pin your agent to one project or a single webhook and the operations you pick. You choose the operations it may call, so destructive ones like deleteWebhook are not included unless you add them.
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 'create a Sanity webhook' or 'list failed Sanity webhook attempts', and Jentic returns the matching operation, such as createWebhook or listWebhookAttempts, with its input schema.
Alternatives and complements available in the Jentic catalogue.
Specific to using Webhooks HTTP Endpoint API through Jentic.
What authentication does the Sanity Webhooks API use?
Per its OpenAPI spec, the Sanity Webhooks API uses a bearer token in the Authorization header on all nine operations. Through Jentic the Sanity token is stored by your own instance and attached at call time, so it stays out of the agent's context.
What is the difference between document and transaction webhooks in Sanity?
A document webhook fires for every document created, updated, or deleted, so a transaction touching three documents sends three requests, and it supports GROQ filters, projections, custom headers, and a secret. A transaction webhook fires once per dataset transaction. Sanity recommends document webhooks.
How do I see why a Sanity webhook failed?
List the webhook's attempts with state set to failure, or list its messages and then the attempts for one message. Each attempt includes resultCode, resultBody, duration, isFailure, and failureReason. The single-attempt lookup only covers transaction webhooks and returns 404 for document webhook attempts.
What are the rate limits for the Sanity Webhooks API?
The OpenAPI spec does not specify rate limits. Check the Sanity documentation at https://www.sanity.io/docs for current API limits for your plan.
Is there a Sanity MCP server?
You don't need an MCP server to give your agent the Sanity Webhooks API. Jentic connects it directly from the API Directory: import it, store your Sanity token once, and your agent calls the webhook and attempt operations when it needs them.
How do I create a Sanity webhook through Jentic?
Search Jentic for 'create a Sanity webhook', load the createWebhook operation, and execute POST /hooks/projects/{projectId} with type, name, url, dataset, and apiVersion, plus a rule with the events to fire on. 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 Webhooks API?
Yes. For a debugging agent, allow just the listWebhooks, listWebhookMessages, and listWebhookAttempts operations under project abc123. It can then trace failed deliveries for that project, but it has no route to create, change, or remove a webhook. Every call it makes is logged.
For Agents
Create, update, disable, or delete Sanity webhooks with GROQ filters and projections, and inspect webhook messages and delivery attempts to debug failed deliveries.
Use for: List all webhooks configured for my Sanity project, Create a webhook that posts to my build server when a post is published, Find all failed delivery attempts for the deploy webhook, I want to disable the Slack notification webhook for now
Not supported: Does not receive or retry webhooks on your side, edit content, or stream changes. Use for configuring Sanity webhooks and inspecting their deliveries only.
The Sanity Webhooks API sets up the webhooks that notify your services when content in a Sanity project changes, and shows how each delivery went. Document webhooks fire per document on create, update, or delete, narrowed by a GROQ filter and shaped by a GROQ projection, while transaction webhooks fire once per dataset transaction. Each webhook targets a URL and a dataset, or every dataset with *, and can set the HTTP method, custom headers, a secret, and whether drafts or all versions trigger it. Messages and delivery attempts record status, result codes, durations, and failure reasons for debugging.
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>