Browserbase: Fetch Page

Fetching a URL through Browserbase Fetch.

Tool ID: browserbase_fetch_page

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'browserbase_fetch_page',
  {
    "url": "https://example.com/resource"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute browserbase_fetch_page --input '{
  "url": "https://example.com/resource"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "id": "id_123",
    "statusCode": 123,
    "headers": {},
    "content": "Example message",
    "contentType": "example",
    "encoding": "example"
  }
}

Use deepline tools get browserbase_fetch_page --json for the latest machine-readable contract.

Input reference

Fetch a page and return its content, headers, and metadata.

Name	Type	Required	Default	Details
`payload.url`	`string`	Yes	—	The URL to fetch Format: `uri`.
`payload.allowRedirects`	`boolean`	No	`false`	Whether to follow HTTP redirects
`payload.allowInsecureSsl`	`boolean`	No	`false`	Whether to bypass TLS certificate verification
`payload.proxies`	`boolean`	No	`false`	Whether to enable proxy support for the request
`payload.format`	`"raw" \| "json" \| "markdown"`	No	`"raw"`	Output format for the response content. `raw` (default) returns the response body unchanged; `json` returns structured data (requires `schema`); `markdown` returns the page as markdown.
`payload.schema`	`record`	No	—	JSON Schema describing the desired structure of the response. Only used when `format` is `json`.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.id`	`string`	Yes	—	Unique identifier for the fetch request
`result.data.statusCode`	`integer`	Yes	—	HTTP status code of the fetched response
`result.data.headers`	`record`	Yes	—	Response headers as key-value pairs
`result.data.content`	`string \| record`	Yes	—	The response body content. A string for `raw` and `markdown` formats; a structured object for `json` format (the schema-extracted result).
`result.data.contentType`	`string`	Yes	—	The MIME type of the response
`result.data.encoding`	`string`	Yes	—	The character encoding of the response
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: provider_usage (provider usage).
Estimated Deepline credits: 0.01 per pricing unit.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Browserbase: Fetch Page

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation