Prerender.io is a service that pre-renders JavaScript-heavy websites to improve SEO by serving static HTML versions to search engine crawlers.
Prerender.io is a service that pre-renders JavaScript-heavy websites to improve SEO by serving static HTML versions to search engine crawlers. On Nagent, Prerender is exposed as a fully-configurable developer tools integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Prerender into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Prerender to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Prerender into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Prerender, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PRERENDER_CHANGE_RECACHE_SPEEDTool to adjust the rendering speed of Manual/API and Automatic rendering queues. Use when you need to control how fast Prerender processes URLs in the recache queue.
Input parameters
Number of URLs to recache per hour. Use 0 for automatic delay, or a value between 3600 and 36000 (where 36000 is fastest).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PRERENDER_CHECK_HEALTHTool to check the health status of the Prerender API service. Use when you need to verify service availability or monitor system health.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PRERENDER_CLEAR_CACHETool to clear Prerender cache using SQL-like wildcard patterns. Schedules a cache clear job. Only one cache clear job can be scheduled per user at a time. Use when you need to invalidate cached pages for a URL pattern.
Input parameters
SQL-like pattern for URLs to clear from cache. Use '%' as wildcard. Example: 'https://example.com%' deletes all URLs starting with that prefix. Use 'https://example.com%' to clear all cached pages for a domain.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PRERENDER_CREATE_SEO_AUDIT_REPORTTool to generate SEO audit reports for a specific URL. Use when you need to analyze SEO performance metrics for a web page. The report will be sent to the provided email address.
Input parameters
Full URL of the page to audit. Must include scheme (http/https). The audit will analyze SEO performance metrics for this page.
Email address where the SEO audit report will be sent. Must be a valid email format.
Last name of the person requesting the audit report.
First name of the person requesting the audit report.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PRERENDER_GET_CACHE_CLEAR_STATUSTool to check the status of a cache clear job. Use when you need to verify if a cache clearing operation is still in progress or has completed.
Input parameters
Your Prerender API token. Used in the URL path to identify the cache clear job.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PRERENDER_GET_PRERENDERED_PAGETool to fetch a prerendered HTML page. Use when you need a static snapshot of a page before dynamic rendering.
Input parameters
Full URL of the page to prerender. Include scheme (http/https). URL will be percent-encoded as needed.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PRERENDER_LIST_HEALTHZTool to check Prerender API health and availability. Use when you need to verify the API is operational before making requests.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PRERENDER_LIST_V3Tool to get a greeting message from the Prerender API. Use when you need to verify basic API connectivity or retrieve the hello message.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PRERENDER_RECACHE_URLTool to cache or recache URLs in Prerender. Use when you need to refresh cached pages or cache new URLs. Supports single URL or batch operations (up to 1000 URLs).
Input parameters
Single URL to cache or recache. Include scheme (http/https). Use this parameter for a single URL, or use 'urls' for multiple URLs. Either 'url' or 'urls' must be provided, but not both.
Array of URLs to cache or recache. Maximum 1000 URLs per request. Include scheme (http/https) for each URL. Use this parameter for multiple URLs, or use 'url' for a single URL. Either 'url' or 'urls' must be provided, but not both.
Rendering device type for caching.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PRERENDER_SEARCH_CACHED_URLSTool to search for cached URLs in your Prerender account and view their cache status. Supports pagination (200 URLs per page) and filtering by desktop/mobile adaptive type. Use when you need to find specific cached pages or check cache status across your account.
Input parameters
Performs a 'contains' query on URLs. Searches for URLs containing this string. If both query and exact_match are provided, only exact_match is used.
Pagination offset. Search returns 200 URLs per page. Use 0 for first page, 200 for second page, 400 for third page, etc.
Returns results where the URL is fully identical to this value. Takes precedence over query parameter if both are provided.
Type of adaptive rendering for cached pages.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 51 agents privately built on Nagent that already use Prerender.
Build on Nagent
Connect Prerender to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Prerender, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Prerender is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Prerender is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Prerender steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Prerender event fires, the agent kicks off automatically.
Every Prerender action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Prerender ships with 10 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Prerender together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Prerender-based workflows tailored to your business.