CONNECT APP
Build with Rendex
HTML, PDF & Screenshot Rendering API for Developers & AI Agents
Developer Tools
- API key
MCP
Give your agent Rendex tools
Every Rendex action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Rendex account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "rendex",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create Artifact:
const result = await mcp.callTool({
name: "rendex-create-artifact",
arguments: {
content: "Content",
inputFormat: "Input Format",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "rendex",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Create Artifact:
result = await session.call_tool("rendex-create-artifact", {
"content": "Content",
"inputFormat": "Input Format",
})API PROXY
Call the Rendex API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Rendex API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.rendex.dev/v1/jobs",
})
// Any allowed Rendex endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.rendex.dev/v1/jobs
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkucmVuZGV4LmRldi92MS9qb2Jz?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Rendex actions from your backend
Connect a user's Rendex account once, then run Create Artifact on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "rendex-create-artifact",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
rendex: { authProvisionId: "apn_xxxxxxx" },
content: "Content",
inputFormat: "Input Format",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="rendex-create-artifact",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"rendex": {"authProvisionId": "apn_xxxxxxx"},
"content": "Content",
"inputFormat": "Input Format",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "rendex-create-artifact",
"configured_props": {
"rendex": { "authProvisionId": "apn_xxxxxxx" },
"content": "Content",
"inputFormat": "Input Format"
}
}'TOOLS
Rendex actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create Artifact
actionTurn Markdown or HTML plus a small branding theme into a branded PDF + PNG and a hosted share page in one call. ReturnspdfUrl,pngUrl,shareUrl, andexpiresAt. See the documentation.Writev0.0.2 -
Create Render Link
actionMint a signed, hosted render URL for a page or HTML — ideal forog:imagetags. The returned URL serves the rendered image/PDF directly. See the documentation.Writev0.0.2 -
Create Watch
actionCreate a watch that monitors a page for visual or text changes. See the documentation.Writev0.0.1 -
Delete Watch
actionDelete a watch and its run history. See the documentation.Writev0.0.1 -
Extract Content
actionExtract the readable content of a page as Markdown, JSON, or HTML. See the documentation.Read-onlyv0.0.1 -
Get Account
actionGet your Rendex plan and this month's usage (credits used/limit/remaining), rate limit, and recommended upgrade. Read-only and free (no credits charged). See the documentation.Read-onlyv0.0.2 -
Get Watch
actionRetrieve a single watch by its ID. See the documentation.Read-onlyv0.0.1 -
List Watch Runs
actionList the run history for a watch (most recent first). See the documentation.Read-onlyv0.0.1 -
List Watches
actionList the watches on your Rendex account, optionally filtered by status. See the documentation.Read-onlyv0.0.1 -
Render Markdown
actionRender a Markdown string to an image or PDF via Rendex — clean default typography, no CSS required. Returns base64-encoded data with metadata. See the documentation.Writev0.0.1 -
Render to Image
actionRender an HTML string or a page URL to an image (or PDF) via Rendex. Returns base64-encoded image data with metadata. See the documentation.Writev0.1.0 -
Run Watch Now
actionTrigger an immediate check for a watch. The run is queued and its diff result is produced asynchronously — poll List Watch Runs for the completed run. See the documentation.Writev0.0.2 -
Update Watch
actionUpdate a watch, including pausing or resuming it. Only the fields you set are changed. See the documentation.Writev0.0.2
- App slug
- rendex
- Authentication
- API key
- Categories
- Developer Tools
- Actions
- 13
- Triggers
- 1
- API proxy
- Available