# Odysee Video Scraper & Channel Monitor (`brick_joey_yto/odysee-scraper`) Actor

Scrape Odysee (LBRY) videos, channels, and search results — metadata, durations, tags, thumbnails. Watch mode detects new uploads by keyword or channel. Official public API, no key. From $1/1,000 results.

- **URL**: https://apify.com/brick\_joey\_yto/odysee-scraper.md
- **Developed by:** [William Billings](https://apify.com/brick_joey_yto) (community)
- **Categories:** Social media, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 results

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

## Odysee Video Scraper & Channel Monitor

**Scrape Odysee (LBRY) without an account.** Video search, channel uploads, full video metadata, and new-upload monitoring — all through Odysee's own public LBRY API. No API key, no login, no scraping workarounds.

Odysee is the largest decentralized video platform — millions of videos, a strong crypto/tech commentary community, and no official data export for researchers. This actor fills that gap.

### What it does

| Mode | Output |
|---|---|
| `search` | Videos matching any keyword — newest first, with channel, duration, tags, thumbnails |
| `channel` | Channel profile (title, description, subscriber proxy stats) + latest uploads |
| `video` | Full metadata for specific video URLs — duration, language, license, media type |
| `watch` | New-upload detection: keywords and/or channels + `releasedAfter` timestamp — the scheduled-monitoring primitive |

### Input examples

Keyword search:

```json
{ "mode": "search", "query": "bitcoin", "maxResults": 100 }
```

Channel profile + uploads:

```json
{ "mode": "channel", "channelUrl": "odysee.com/@veritasium", "maxResults": 20 }
```

Bulk video metadata:

```json
{ "mode": "video", "videoUrls": ["lbry://@samtime#f/episode-name#a", "odysee.com/@channel:f/video-title:8"] }
```

Monitor channels + keywords for new uploads (run hourly via Apify Schedules):

```json
{
  "mode": "watch",
  "queries": ["crypto", "privacy"],
  "channelUrls": ["odysee.com/@veritasium", "lbry://@samtime"],
  "releasedAfter": 1759000000,
  "maxResults": 50
}
```

### Output example

```json
{
  "recordType": "search_result",
  "claimId": "79f4b85922347dec67af0de7ba040e50d3df4354",
  "name": "bitcoin-will-not-wait-for-you",
  "title": "Bitcoin will NOT wait for you",
  "description": "...",
  "odyseeUrl": "https://odysee.com/@CryptoVigilante:f/bitcoin-will-not-wait-for-you:2",
  "streamType": "video",
  "mediaType": "video/mp4",
  "durationSeconds": 3704,
  "tags": ["bitcoin", "crypto"],
  "thumbnailUrl": "https://thumbs.odycdn.com/...",
  "channelName": "CryptoVigilante",
  "channelClaimId": "80c9147abaf...",
  "publishedAt": 1758636000
}
```

### Why scheduled monitoring matters

Odysee hosts content that gets removed from mainstream platforms — researchers tracking disinformation, crypto commentary, or niche creators need alerts when tracked channels upload. Pair `watch` with `releasedAfter` = last-run timestamp and an Apify Schedule for a self-maintaining alert pipeline.

### Pricing

**$1 per 1,000 results** (`$0.001` per dataset row).

### Notes & limitations

- Uses Odysee's own public proxy API (`api.na-backend.odysee.com`) — the same backend the website calls. Keyless, but be reasonable with request volume.
- View/like counts are not exposed by the API; engagement metrics aren't available.
- `release_time` on some content is a far-future sentinel — `publishedAt` (creation timestamp) is more reliable for monitoring.

### More from this fleet

Also by **brick\_joey\_yto**: [BitChute Scraper](https://apify.com/brick_joey_yto/bitchute-scraper) · [Rumble Scraper](https://apify.com/brick_joey_yto/rumble-scraper) · [Telegram Channel Scraper](https://apify.com/brick_joey_yto/telegram-scraper) · [4chan Scraper](https://apify.com/brick_joey_yto/4chan-scraper) · [Bitcointalk Scraper](https://apify.com/brick_joey_yto/bitcointalk-scraper) · [Gab Scraper](https://apify.com/brick_joey_yto/gab-scraper)

# Actor input Schema

## `mode` (type: `string`):

search = keyword video search. channel = channel info + latest uploads. video = metadata for specific video URLs. watch = new uploads matching keywords and/or channels.

## `query` (type: `string`):

search mode: keyword phrase — e.g. 'bitcoin', 'linux tutorial'.

## `channelUrl` (type: `string`):

channel mode: Odysee channel — e.g. 'odysee.com/@veritasium' or 'lbry://@veritasium'.

## `videoUrls` (type: `array`):

video mode: Odysee video URLs or lbry:// URIs to fetch full metadata for.

## `queries` (type: `array`):

watch mode: keywords to monitor for new uploads — e.g. \['crypto', 'privacy'].

## `channelUrls` (type: `array`):

watch mode: channels to monitor for new uploads.

## `releasedAfter` (type: `integer`):

Only content released after this unix timestamp — used by search and watch for incremental monitoring.

## `mediaType` (type: `string`):

Optional MIME filter — e.g. 'video/mp4', 'audio/mpeg'.

## `maxResults` (type: `integer`):

Global cap on rows returned.

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

Optional Apify proxy — the public API rarely needs it.

## Actor input object example

```json
{
  "mode": "search",
  "maxResults": 50
}
```

# Actor output Schema

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

Dataset containing video/channel records

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("brick_joey_yto/odysee-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("brick_joey_yto/odysee-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 '{}' |
apify call brick_joey_yto/odysee-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,brick_joey_yto/odysee-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/dRpWJw38iiaBjPX1r/builds/Q032bGCwRdKbPi1cH/openapi.json