Aggregators

An Aggregator is the top-level concept in Fetchosaurus. It represents a unified data collection from multiple sources.

What is an Aggregator?

Think of an aggregator as a “table” that collects data from multiple websites into a consistent format. For example:

• A “Remote DevOps Jobs” aggregator collects job listings from Lever, Greenhouse, and WeWorkRemotely
• A “Vienna Events” aggregator collects events from local theaters, cinemas, and cultural centers
• A “Tech News” aggregator collects articles from multiple tech blogs

Aggregator Structure

Each aggregator has:

Component	Description
Name	A human-readable name for the aggregator
Schema	Defines the structure of collected data (versioned)
Sources	Websites that feed data into the aggregator
Items	The actual collected data records

Aggregator: "Remote DevOps Jobs"
├── Schema (versioned)
│   ├── v1: { title, company, location }
│   └── v2: { title, company, location, salary }
├── Sources
│   ├── lever.co (using schema v2)
│   ├── greenhouse.io (using schema v2)
│   └── weworkremotely.com (using schema v1)
└── Items
    ├── { title: "Engineer", company: "Stripe", ... }
    ├── { title: "DevOps Lead", company: "Vercel", ... }
    └── ... (thousands of items)

Creating an Aggregator

When you create an aggregator, you:

1. Choose a name
2. Select a built-in schema (Job, Event, Listing, Article, or Recipe)
3. The schema is copied into your aggregator as version 1

From that point, you own the schema and can modify it as needed.

Limits

The number of aggregators you can create depends on your plan:

Plan	Aggregators
Free	1
Starter	5
Pro	20

Related Concepts

• Sources - How data flows into an aggregator
• Schemas - How data is structured
• Items - The collected data records