Page Content

The page_content field provides a detailed, AI-curated breakdown of everything visible on a page.

Unlike raw DOM dumps, page_content is structured and relevant — items are listed, data is organized, and irrelevant chrome (navbars, footers, ads) is omitted.

Requesting Page Content

const page = await client.browse({
  url: 'https://docs.example.com/api/auth',
  include_page_content: true,
});

console.log(page.page_content);
// "Authentication documentation with 3 methods:
//
// 1. API Keys — Generate from dashboard. Include as Authorization: Bearer <key>.
// 2. OAuth 2.0 — Authorization code flow. Redirect URI required.
// 3. JWT Tokens — For service-to-service auth. Sign with RS256."

Cost Implications

page_content requires a separate LLM call, so it adds:

• ~500ms latency per request
• Additional token usage (internal, not billed separately)

Only request it when your agent needs to parse specific data. The summary field is sufficient for most decision-making.