# Site to Agent Feed (URL to RAG-ready Markdown) (`constant_quadruped/site-to-agent-feed`) Actor

Turn any URL into clean, RAG-ready Markdown + structured JSON for LLMs and AI agents. Self-healing main-content extraction (survives redesigns), headings/links/tables, optional change-detection. No paid APIs.

- **URL**: https://apify.com/constant\_quadruped/site-to-agent-feed.md
- **Developed by:** [CQ](https://apify.com/constant_quadruped) (community)
- **Categories:** AI, Agents, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Site to Agent Feed (URL → RAG-ready Markdown)

Give it any URL(s); get back **clean Markdown + structured JSON** built for LLMs and AI agents — main-content extraction (via [trafilatura](https://trafilatura.readthedocs.io/), which adapts to page layout instead of relying on brittle CSS selectors), plus title, headings, links, and a table count. Optional **change-detection** turns it into a site monitor.

### Why

Agents and RAG pipelines want **Markdown as a first-class return type** (not raw HTML), and extraction that doesn't break on every redesign.

### How it works

1. Fetches each URL's HTML over HTTP (`httpx`), optionally through Apify Proxy with an automatic direct-request fallback.
2. Extracts the main content with trafilatura → Markdown + plain text. Falls back to a BeautifulSoup strip + markdownify if trafilatura returns nothing.
3. Pulls structure (title, h1–h3 headings, links, table count) with BeautifulSoup.
4. If `detectChanges` is on, stores a SHA-256 content hash per URL in the actor's key-value store and sets `changed: true` when it differs from the previous run.

### Input

| Field | Type | Default | Notes |
|-------|------|---------|-------|
| `urls` | array of strings (**required**) | `["https://en.wikipedia.org/wiki/Retrieval-augmented_generation"]` | Pages to convert to Markdown + structured data. |
| `outputFormat` | string | `"markdown"` | `"markdown"` = structured item with `markdown` (no raw `text`); `"both"` = also include the raw extracted `text`. |
| `detectChanges` | boolean | `false` | Remember each URL's content hash and flag `changed` when it differs across runs. |
| `maxChars` | integer | `50000` | Truncate each page's `markdown` and `text` to at most this many characters (range 1000–500000). |
| `proxyConfiguration` | object | off (direct request) | Optionally route through Apify Proxy to get past simple datacenter-IP blocks. The actor falls back to a direct request if a proxy attempt fails. |

### Per-URL output

Each successfully fetched page produces a Dataset item with:
`url`, `fetched_at` (UTC ISO timestamp), `title`, `markdown`, `headings[]` (h1–h3, capped at 50), `links[]` (`{text, href}`, capped at 200), `table_count`, `word_count`, `content_hash` (SHA-256 of the extracted text), and (if `detectChanges`) `changed`. The raw `text` field is included only when `outputFormat: "both"`. `text` and `markdown` are truncated to `maxChars` per page.

If a URL fails to fetch **or** its content can't be extracted, its item is just `{ "url": ..., "error": ... }` — the run still completes successfully.

> **`outputFormat`:** `"markdown"` (default) returns the structured item with `markdown` (no raw `text` field); `"both"` additionally includes the raw extracted `text`. `markdown`, headings, links, and all other structured fields are present in both modes.

### Use as a monitor

Schedule it with `detectChanges: true` — each run flags which pages changed, so an agent only re-ingests what's new.

### Pricing

Billed on standard Apify platform usage (compute units for the run, plus Apify Proxy traffic only if you enable it). It calls **no paid third-party APIs** of its own.

### Limitations — read this

- **Server-rendered HTML only. No JavaScript execution.** It uses a plain HTTP fetch, not a browser. Single-page apps and content injected by JS will be missing or sparse. Use a browser-based scraper for those.
- **Heavily bot-protected sites return 403.** Sites behind Akamai/Cloudflare-class bot protection (e.g. **SEC.gov, FINRA.org**) block non-browser TLS fingerprints and will fail even through a residential proxy. This lightweight fetcher is for normal/server-rendered pages; use a real-browser scraper for those. Optional Apify Proxy (off by default) helps only with simple datacenter-IP blocks, not bot-protection.
- **Extraction quality depends on trafilatura.** On unusual layouts it may grab too much or too little; the fallback is a coarse text strip.
- **Change-detection is whole-page hashing.** Any change (including dynamic timestamps, view counters, or rotating banners) flips `changed` to true — it does not diff *what* changed. Hashes persist in the actor's default key-value store, so change flags are meaningful only across runs of the same actor/store.
- **No anti-bot handling, JS challenges, logins, or pagination.** Pages behind Cloudflare/auth or requiring clicks won't work. The actor fetches only the exact URLs you pass — it does not crawl or follow links.
- `links` and `headings` are capped (200 / 50) and may be truncated on large pages; `markdown`/`text` are capped at `maxChars`.
- Sends only a basic browser User-Agent; you are responsible for honoring each site's terms and robots policy.

# Actor input Schema

## `urls` (type: `array`):

Pages to convert into clean Markdown + structured data for agents/RAG. Works on normal/server-rendered pages; heavily bot-protected sites (e.g. SEC.gov, FINRA, Cloudflare-gated) will return a 403 — those need a browser-based scraper.

## `outputFormat` (type: `string`):

Choose Markdown + structured JSON, or also include the raw extracted text.

## `detectChanges` (type: `boolean`):

Remember each URL's content hash and flag `changed: true` when it differs — turns this into a site-change monitor for agents.

## `maxChars` (type: `integer`):

Truncate each page's markdown and text to at most this many characters.

## `proxyConfiguration` (type: `object`):

Optional. Route requests through Apify Proxy to get past datacenter-IP blocks on some sites. Off by default (direct = cheapest, fine for most pages). Enable RESIDENTIAL for stubborn sites — note it does NOT defeat Akamai/Cloudflare bot protection (e.g. SEC.gov still blocks). The actor falls back to a direct request if a proxy attempt fails.

## Actor input object example

```json
{
  "urls": [
    "https://en.wikipedia.org/wiki/Retrieval-augmented_generation"
  ],
  "outputFormat": "markdown",
  "detectChanges": false,
  "maxChars": 50000,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `feeds` (type: `string`):

Per-URL Markdown + structured metadata records in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://en.wikipedia.org/wiki/Retrieval-augmented_generation"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("constant_quadruped/site-to-agent-feed").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://en.wikipedia.org/wiki/Retrieval-augmented_generation"] }

# Run the Actor and wait for it to finish
run = client.actor("constant_quadruped/site-to-agent-feed").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://en.wikipedia.org/wiki/Retrieval-augmented_generation"
  ]
}' |
apify call constant_quadruped/site-to-agent-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=constant_quadruped/site-to-agent-feed",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/JrJhahpMcku0d2wbP/builds/AS7XwTsKlhjC0nHXZ/openapi.json