Sanity
for LuumenAI
Read Sanity projects, roles, and documents, then change access as approved steps
Connect Sanity and your team can ask who has access to a project, what roles exist in the organization, and what a given document contains — answered from the live API. Changes to roles, user attributes, and documents run as previewed steps you approve first. Luumen authenticates with an API key.
The Sanity toolbox
21 tools: 14 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCreate Prompt PostSend a one-shot prompt to the Sanity Content Agent.
- ReadGet Document by IDFetch a single document by its ID from Sanity.
- ReadGet Invite By TokenRetrieve an invite by its public token.
- ReadGet Organization RoleRetrieve a specific organization role by its ID.
- ReadGet PermissionGet a permission for a specific resource.
- ReadGet ProjectRetrieve full details for a specific Sanity project by its ID.
- ReadGet RobotsGet robots with access to a resource.
- ReadGet RoleRetrieve a specific role for a given resource type and resource ID.
- ReadList Resource UsersList all users of a resource and their assigned roles.
- ReadList Organization RolesList all roles available for an organization.
- ReadList User AttributesRetrieve user attributes from a Sanity organization.
- ReadQuery All ScreeningExecute a GROQ query to fetch all screening documents from Sanity.
- ReadQuery DocumentsExecute an arbitrary GROQ query against a Sanity dataset.
- ReadValidate CredentialValidate Sanity API credentials by fetching the authenticated user's information.
- WriteAdd Default Role to UsersApply organization default role to all users. Approval by default
- WriteCreate Attribute DefinitionCreate a new user attribute definition in Sanity. Approval by default
- WriteDelete User Attribute DefinitionDelete a user attribute definition. Approval by default
- WriteDelete DocumentDelete a document from Sanity by ID or query. Approval by default
- WriteDelete User AttributesDelete custom attributes from a Sanity user within an organization. Approval by default
- WriteUpdate Organization ACLAssign a role to a member in a Sanity organization. Approval by default
- WriteUpdate User Attributes ValuesUpdate user attribute values for a resource. Approval by default
One prompt, start to finish
What a governed Sanity run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as add default role to users, create attribute definition, delete user attribute definition, delete document, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Sanity — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Sanity to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.