Publishing

render_page

JPEG screenshot of a published page as an image content block plus metadata. Use to visually verify a publish; not for editing. full_page=true verifies the full rendered document: below-the-fold lazy images are prepared with bounded waits before capture, so images that can load are visible (broken or blocked resources still cannot be forced to load). Uses an owner/render bypass: it verifies published page appearance and renderability ONLY, and does NOT prove that an anonymous visitor will encounter the configured gate or paywall, nor that checkout/access works (gate_bypassed is always true, visitor_access_verified always false). Published only (drafts -> E_NOT_FOUND). Daily caps per account (free 10, pro 200); over-cap -> E_RATE_LIMITED with retry_after.

Behaviour

Effect
Read only. Calling it never changes anything in the account.
Repeat calls
Idempotent. Repeating the same call produces the same result.
Plan
Available on every plan, including free.

Parameters

NameTypeRequiredDescription
site_iduuidYesSite UUID from list_sites.
pathstringYesPage URL path to render. Defaults to '/', the site's homepage. '/index' is an ordinary page, not the root.
viewportenum
desktop | mobile
Yesdesktop=1440x900 or mobile=390x844. Default desktop.
full_pagebooleanYesWhen true, verify the whole rendered document: the capture prepares below-the-fold content first (lazy images are made eager and the viewport is stepped down the page with bounded waits) so images that CAN load are visible in the screenshot, not just a taller canvas. Images that are broken, blocked or unreachable cannot be forced to load and still capture as-is. When false, capture the viewport only.

Returns

NameTypeDescription
site_iduuid-
pathstring-
viewportenum
desktop | mobile
-
widthinteger-
heightinteger-
revisionstring-
full_pageboolean-
captured_atstring-
gate_bypassedtrueALWAYS true. render_page captures the page through an owner/render bypass, so any configured gate, allowlist or paywall was SKIPPED for this capture. The image is not evidence that access control works.
visitor_access_verifiedfalseALWAYS false. render_page verifies only that the published page renders; it does NOT prove an anonymous visitor would encounter the configured gate/paywall, nor that checkout, entitlements or access grants work. Verify access separately with get_site_access / get_paid_access and a real visitor purchase.

Using it

render_page is called by an AI assistant connected to Sentway over MCP, not by hand. Point the assistant at the Sentway MCP endpoint and complete the OAuth flow, and the tool becomes available in the same session as the other 56 Sentway tools. See connecting over MCP.