Render a page to Markdown · Browser API
Render a URL in a headless browser (running JavaScript) and return the page as clean Markdown — ideal for content analysis, summarization, and feeding pages to language models.
curl https://api.unifapi.com/browser/markdown \ -H "Authorization: Bearer $UNIFAPI_KEY"
This operation is part of the Browser API in the browser category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Browser public data but should still keep one API key, one account balance, and one predictable JSON contract across social, live public-data sources.
Common agent workflows
- Fetch canonical public Browser content for summarization, ranking, monitoring, or enrichment.
- Attach engagement, author, media, and source metadata to an agent workflow.
- Give an AI agent a stable Browser data source without building a per-platform integration.
- Normalize Browser responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
- The operation has a 10 credits ($0.01) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
- A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.
Billing
This operation charges 1 credit per billable record, with a 10 credits ($0.01) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Platform-caused failures can be refunded.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
More Browser operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
Render a page to HTML
Render a URL in a headless browser and return the fully rendered HTML after JavaScript execution — use it to read meta tags, structured data, and content that only appears after client-side rendering.
Extract links from a page
Render a URL in a headless browser and return every link on the page as absolute URLs, including links injected by JavaScript. Optionally restrict to visible links or same-domain links for internal-link and broken-link audits.
Capture a page screenshot
Render a URL in a headless browser and capture a screenshot, returned as a base64-encoded image. Control the viewport, capture the full scrollable page, target a CSS selector, and choose png, jpeg, or webp output.