Agent Utility
Page Normalize
Convert a public HTTPS page into a stable semantic representation for software consumption.
Developer Preview
Public API access is not yet available.
Page Normalize is under active development and is not yet generally available for external API use.
Representative response
Inspect normalized output
Representative response using a saved Page Normalize fixture. The live service is not contacted.
Ready to load a saved response.
Select Normalize to inspect the local fixture.
Status: developer preview
When should an agent use Page Normalize?
Use Page Normalize when software needs the rendered content and structure of a public web page in a predictable response instead of raw, site-specific HTML. It is useful for retrieval, grounding, extraction, and workflows that need complete-page or primary-content representations.
When should it not be used?
Do not use it to reach private or internal networks, bypass authentication or access controls, interact with a page, submit forms, or replace a website-specific API that already provides authoritative structured data.
Preview interface
The planned interface accepts a public HTTPS URL and returns a versioned normalized representation. This is a conceptual preview, not actionable API onboarding.
Response and charging
Successful responses use the pb.page.normalized.v1 schema. Page Normalize currently consumes 1 Agent Utilities credit per successful request. Failed requests do not retain a charge.
Errors include a request ID for diagnostics. Some pages cannot be normalized because of availability, access controls, unsupported behavior, or safety restrictions.