Agent Utilities

Reliable external primitives for autonomous software.

Autonomous software often needs dependable capabilities outside its model context. Agent Utilities provides narrowly scoped, versioned services for those tasks, with contracts developers can inspect and build against.

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.

Developer preview

Page normalization

Convert an arbitrary public HTTPS page into a stable semantic representation suitable for software consumption. The response can include both a complete-page representation and a focused primary-content representation under the versioned schema pb.page.normalized.v1.

Read the Page Normalize guide

What the utility provides

  • Browser-rendered page capture
  • Normalized text and Markdown
  • Primary-content identification
  • Heading extraction and normalized links
  • Semantic page regions
  • Stable response schema
  • SSRF and redirect protections
  • Versioned normalization behavior

A small, explicit contract

Agents and applications are designed to use one external capability instead of repeatedly building rendering, extraction, and normalization logic into each workflow. The scope stays narrow, and changes are managed through a versioned API contract.

This is infrastructure for software systems; it does not replace the developer tools people use directly.

Example workflow

From public page to agent-ready data

Representative visualization · no live request

Public HTTPS URLhttps://example.com/article
header
mainDesigning dependable systemsRead the implementation notes
footer
Normalizesemantic regionsnormalized textstable links
Structured response200
pb.page.normalized.v1
{
"schema": "pb.page.normalized.v1",
"request": { "url": "https://example.com/article" },
"content": {
"main_text": "Readable primary content…"
},
"structure": { "regions": [...] }
}

Representative contents abbreviated from the versioned response contract.

Agent / application Ready to consume

Stage 1 of 5

Public URL received

The caller supplies a public HTTPS page to normalize.

Billing

A shared prepaid credit wallet

Practical Builds Agent Utilities uses a shared prepaid credit wallet. Each utility has its own published credit cost. Page Normalize currently consumes 1 credit per successful request.

Credit packs fund one Agent Utilities balance; they are not tied specifically to Page Normalize and do not apply to unrelated Developer Tools.

Starter

$5

1,000 Agent Utilities credits

$0.005 per Agent Utilities credit

Builder

$20

5,000 Agent Utilities credits

$0.004 per Agent Utilities credit

Scale

$75

25,000 Agent Utilities credits

$0.003 per Agent Utilities credit

Each Agent Utility defines its own credit cost. Future utilities may have different rates while using the same wallet.

Developer surfaces

Page Normalize Preview pricing Security