Prerender
for LuumenAI
Check what Prerender has cached, then recache the pages that went stale
Connect Prerender and Luumen can tell you what search crawlers are actually being served. Search your cached URLs, check when each was last rendered, and pull the prerendered HTML for a page to see it yourself. When a deploy leaves stale markup behind, recaching those URLs or clearing a path is a previewed step you approve first. Authentication is by API key.
The Prerender toolbox
10 tools: 6 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCheck HealthCheck the health status of the Prerender API service.
- ReadGet Cache Clear StatusCheck the status of a cache clear job.
- ReadGet Prerendered PageFetch a prerendered HTML page.
- ReadList HealthzCheck Prerender API health and availability.
- ReadList V3Get a greeting message from the Prerender API.
- ReadSearch Cached URLsSearch for cached URLs in your Prerender account and view their cache status.
- WriteChange Recache SpeedAdjust the rendering speed of Manual/API and Automatic rendering queues. Approval by default
- WriteClear CacheClear Prerender cache using SQL-like wildcard patterns. Approval by default
- WriteCreate SEO Audit ReportGenerate SEO audit reports for a specific URL. Approval by default
- WriteRecache URLCache or recache URLs in Prerender. Approval by default
One prompt, start to finish
What a governed Prerender 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.
Read actions answer immediately. Anything that writes — change recache speed, clear cache, create seo audit report, recache url — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 Prerender — 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 Prerender to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.