Integration

Rendex integration

Rendex is a rendering and web-capture API. Screenshot a web page, raw HTML or Markdown as PNG, JPEG, WebP or PDF (optionally filling a Mustache template with data), extract clean reader-mode Markdown, JSON or HTML from a page, mint signed hosted-render links for og:image tags, turn Markdown or HTML into a branded PDF and PNG with a share page, and monitor pages for visual or text changes with Rendex Watch (create, test, run, pause and read the run history of watches). Async and batch capture are not exposed (the vendor's OpenAPI document and its reference page disagree on their request and response shapes), nor are the health checks, the GET screenshot variant (a subset of the POST one) and the route that serves a signed link. Authentication is a Rendex API key (rdx_...) sent as a Bearer token in the Authorization header.

Connect Rendex How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Rendex.Built from the 14 Rendex tools below, on the connection you add once.

What you can do with Rendex

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Watch, 5 operations

create_watchCreate watchPOSTStarts monitoring a URL for changes: Rendex renders it in Chrome on a schedule, diffs each capture against a baseline (visually and/or by text) and alerts by email or webhook. The baseline capture costs 1 credit.
delete_watchDelete watchDELETEPermanently deletes a watch and its run history.
get_watchGet watchGETReturns one watch: URL, schedule, diff settings, alert channels, status, baseline, last run, last change and its what-changed summary.
list_watchesList watchesGETLists your watches, newest first, with their URL, schedule, diff settings, status, last run and last change. Filter by status and page with the cursor.
update_watchUpdate watchPATCHChanges a watch: URL, name, interval, diff settings, capture settings or alert channels. Set paused to true to pause it, false to resume it. Send only the fields to change.

Run, 2 operations

list_watch_runsList watch runsGETLists a watch's checks, newest first: whether the page changed, the diff score, signed before, after, overlay and crop image URLs, the text diff and a what-changed summary, and the credits charged.
run_watch_nowRun watch nowPOSTQueues an immediate check of an active watch (1 credit) and returns the run id. The result appears in list_watch_runs once the check completes.

Account, 1 operation

get_accountGet accountGETReturns the account's plan, this month's credit usage (used, limit, remaining, reset date), the per-minute rate limit and a recommended upgrade. Free: it does not consume credits.

Artifact, 1 operation

render_artifactRender artifactPOSTTurns Markdown or HTML plus an optional branding theme (logo, accent color, font, header, footer) into a PDF and/or PNG and a hosted share page. Returns short-lived signed URLs. Each requested format costs 1 credit.

Extract, 1 operation

extract_contentExtract contentPOSTTurns one web page into clean reader-mode content (Markdown, JSON or article HTML) read from the fully rendered page, so it works on JavaScript-heavy sites. Returns the content plus title, byline, excerpt and site name.

Json, 1 operation

capture_screenshot_jsonCapture screenshot jsonPOSTSame capture as capture_screenshot, but answers JSON: the image base64-encoded plus its metadata (size, viewport, load time, capture quality). With extract set to true it also returns the page's reader-mode content in data.extracted.

Link, 1 operation

create_render_linkCreate render linkPOSTMints a signed, self-contained URL that renders the given page, HTML or Markdown (same capture options as capture_screenshot) on its first request and serves the cached copy afterwards. Paste it into an og:image tag or an img src.

Screenshot, 1 operation

capture_screenshotCapture screenshotPOSTCaptures a web page (url), raw HTML (html) or Markdown (markdown) and returns the image or PDF as a file. Pass exactly one source. With data, html or markdown is filled as a Mustache template first.

Test, 1 operation

test_watchTest watchPOSTDry-runs a watch configuration: renders the page once as a live check would and reports whether it is reachable, with a screenshot URL and the text a text watch would compare. Creates nothing. Costs 1 credit, refunded if unreadable.

Use Rendex from Claude Code, Cursor or Codex

Connect Rendex in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Rendex operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Rendex

Create your workspace
Sign up free. Nothing to install.
Connect Rendex once
Add your Rendex connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.