Web Page Content

Retrieve the contents of a webpage from its URL. The sample response includes URLs. Use it in developer tools or technical research. Choose an implementation and check its published request fields, examples, and usage pricing before integrating.

Selected price
$0 / callPublished pricing
Sellers / implementations
4 / 4
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
URL of the page to fetch
Required application identifier. Values longer than 256 characters are truncated. Alternatively supply the keenable_title query parameter.
Optional parameters (3)
Maximum number of characters of content to return. Longer content is truncated and a notice is appended after the cut, so the response runs slightly past this number.
Fetch the page live from the source instead of returning Keenable's indexed copy. Enables fetching URLs that are not indexed.
Optional extraction instruction. When set, an LLM reads the fetched page and the response content is only the output for this instruction instead of the full page. Example: "List all pricing tiers with their monthly prices".

Sample response

{
  "author": "<author>",
  "content": "<content>",
  "description": "<description>",
  "published_at": "<published_at>",
  "title": "<title>",
  "url": "<url>"
}

Response result

Response structure

Inferred from examples
  • authorstring
  • contentstring
  • descriptionstring
  • published_atstring
  • titlestring
  • urlstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Web Page Content with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.