URL
On this page
Purpose
Web Fetch retrieves content from known URLs. It returns extracted pages or raw text for use in a flow or by Agent Core.
When to use it
- Retrieve content from a known public page.
- Fetch a page that needs dynamic rendering.
- Send extracted page content to a DataFrame-aware or text-based step.
Required setup
Use valid public URLs. Normal mode needs one or more URLs, while Agent Core supplies them in Tool Mode. Leave Linkup API Key empty to use the Arkus platform key. If the platform key is not configured, the run fails. To use your own Linkup account, select a saved Linkup Credential.
How to use it
Tool Mode
- Add Web Fetch, enable Tool Mode, and connect the tool output to Agent Core.
- Configure rendering and content controls, then give the Agent a clear URL scope.
- Test one known public URL.
Normal mode
- Enter the URLs to retrieve.
- Change rendering or content controls when the default extraction is not enough.
- Connect Extracted Pages to a DataFrame-aware component, or Raw Content to a text-based component.
Configuration
| Setting | What it controls | Recommended starting point |
|---|---|---|
| URLs | Lists up to 60 pages. Missing schemes receive https://, and duplicate normalized URLs are removed in first-seen order. | Start with one known URL. |
| Render Dynamic Content | Renders page content before extraction. It is enabled by default. | Leave it on for modern interactive pages. |
| Include Raw HTML | Adds the source HTML to the result. It is disabled by default. | Enable only when a downstream step needs markup. |
| Include Images | Adds image information to the result. It is disabled by default. | Leave it off unless the workflow needs it. |
| Linkup API Key | Uses your Linkup account when set. An empty field uses the Arkus platform key. | Leave empty for Arkus credits, or select a saved Linkup Credential. |
Expected result
Web Fetch runs up to six requests at once with a fixed 90-second provider timeout. Results stay in input order. Extracted Pages returns one row per successful URL with text, content, and url, plus raw_html or images when requested. Raw Content joins successful page text into a Message and is the Agent tool output.
Failed URLs do not create rows. Mixed batches return successful rows and record failures in component status; a run with no successful URL fails. Each successful platform-keyed URL consumes Arkus credits. A personal Linkup key bypasses Arkus web-call metering and may incur Linkup charges.
Reference details
Enable Tool Mode when Agent Core should fetch pages. Give the Agent a clear URL scope so it does not retrieve unrelated content.
Save credits with your own key
Select a saved Linkup Credential in Linkup API Key to bill Linkup directly instead of using Arkus web-call credits. A deployed flow requires a saved owner Credential. Credential changes apply to subsequent runs; deleting a required Credential prevents the flow from running.
Works well with
Send Extracted Pages to Split Text before retrieval or model processing. Use DataFrame Operations to filter page rows. In Tool Mode, connect the generated tool to Agent Core's tools input.