# Bazos Scraper (`stone_jadex/bazos-scraper`) Actor

- **URL**: https://apify.com/stone_jadex/bazos-scraper.md
- **Developed by:** [Stone Jade](https://apify.com/stone_jadex) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Bazoš Scraper

Bazoš Scraper gives Czech and Slovak classifieds researchers structured results from public pages. Start with Bazoš section, category or listing URLs and export title, asking price, location, posted date and views.

### What you can do

- Compare asking prices across Czech and Slovak categories while retaining the published currency and raw price text.
- Group supply by town or postal code and distinguish promoted listings and public view counts when present.
- Review dates and descriptions alongside the source listing instead of copying each category card manually.

### Who uses it

- A used-phone reseller can compare CZK asking prices and locations for similar models before sourcing stock.
- A property researcher can group Slovak rental listings by postal code, then inspect full descriptions in detail mode.

### Result preview

**Illustrative only:** invented examples show the shape of the data; they are not real results. A dash indicates an unavailable value.

| Title | Price | Town | Postal code | Views |
| --- | --- | --- | --- | --- |
| Used bicycle | 2,500 CZK | Example town | 110 00 | 12 |
| Sofa | 120 EUR | Example district | 811 01 | 8 |
| Used phone | 3,000 CZK | Example city | 602 00 | — |

Fields may be absent when the source does not publish them.

### Why choose this Actor

- Both Bazoš country sites are supported in the same run, with country and currency retained on each result.
- Detail mode adds the full description, category path, gallery and coordinates where published; list rows contain a description snippet.

### Pricing

Prices in **USD**, verified on 4 November 2026. Check the current Pricing tab before running.

| Result type | Event price |
| --- | ---: |
| List listing | $1.5 per 1,000 results |
| Listing with details | $1.5 per 1,000 results |

The detail event replaces the list event for the same result; the two are not added together. For example, 1,000 results at the list listing rate incur $1.5 in result-event charges. This calculation covers Actor event charges. Review Pricing for any separately listed platform usage; later access to stored data follows Apify's applicable storage pricing.

### Try it in three steps

1. Enter Bazoš section, category or listing URLs. Set a small result limit for your first run.
2. Turn on **Open each listing page** for full descriptions and other detail fields, or leave it off for list results. Run the Actor.
3. Inspect the dataset and export the results in your preferred available format.

### Coverage and FAQ

**What are the limits?** Keyword search and filter URLs are not accepted. List rows omit detail-only fields; phone numbers and email addresses are not collected.

The requested result limit defaults to 50 and can be set up to 5,000 per run.

**Is this a live feed?** Each run is a snapshot of available source information. Listings, prices and other details may change after collection; a requested maximum is a ceiling, not a promise of that many results.

**Can I use the data for ongoing analysis?** Yes, export it to your own workflow. Scheduling repeated runs or acting on the exported results requires your own workflow.

# Changelog

This Actor's version history is a separate document: https://apify.com/stone_jadex/bazos-scraper/changelog.md

# Actor input Schema

## `startUrls` (type: `array`):

Bazoš section or category pages, e.g. https://mobil.bazos.cz/, https://mobil.bazos.cz/apple/, https://reality.bazos.sk/byty/, or a listing URL /inzerat/{id}/…php. Keyword search and filter URLs (search.php, ?hledat=, price/location filters) are disallowed by Bazos robots.txt and are rejected. Empty = mobil.bazos.cz + auto.bazos.sk.

## `maxItems` (type: `integer`):

Stop after this many listings (across all URLs).

## `maxPages` (type: `integer`):

Optional. 20 listings per page.

## `scrapeDetails` (type: `boolean`):

Adds full description, category path, all images and GPS. Same price per listing (charged as listing-detail instead of listing). Slower: one extra request per listing.

## `requestDelayMs` (type: `integer`):

Polite pacing, at least 1.5 s (values below 1500 are raised to 1500).

## `maxRunSeconds` (type: `integer`):

Stops cleanly and writes OUTPUT before this limit.

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

Direct connection by default (Bazos works without a proxy).

## `useProxyFallback` (type: `boolean`):

Stay direct until repeated 403/429, then switch to the configured proxy.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://mobil.bazos.cz/"
    }
  ],
  "maxItems": 50,
  "scrapeDetails": false,
  "requestDelayMs": 1500,
  "maxRunSeconds": 3600,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "useProxyFallback": false
}
```

# Actor output Schema

## `results` (type: `string`):

Public listing records in the default dataset, including an uncharged run-notice row when a run is truncated.

## `summary` (type: `string`):

Saved run statistics, seed and error details, and the reason the crawl stopped.

# 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 = {
    "startUrls": [
        {
            "url": "https://mobil.bazos.cz/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("stone_jadex/bazos-scraper").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 = { "startUrls": [{ "url": "https://mobil.bazos.cz/" }] }

# Run the Actor and wait for it to finish
run = client.actor("stone_jadex/bazos-scraper").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://mobil.bazos.cz/"
    }
  ]
}' |
apify call stone_jadex/bazos-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,stone_jadex/bazos-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

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