# Odysee Scraper - Videos, Channels, Tags & Metadata (`crawlyard/odysee-scraper`) Actor

Scrape Odysee (LBRY) videos and channels by search term or channel handle: title, description, channel, duration, tags, language, release date and thumbnail. No login, no proxy.

- **URL**: https://apify.com/crawlyard/odysee-scraper.md
- **Developed by:** [Crawlyard Data](https://apify.com/crawlyard) (community)
- **Categories:** Videos, News, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 items

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 Scraper

Turns Odysee search terms and channel handles into clean rows of video
metadata — **title, description, channel, duration, tags, language, licence,
release date and thumbnail**.

No login, no API key, no proxy.

### What one row looks like

```json
{
  "title": "FREE TV FOR AS LONG AS IT LASTS!",
  "url": "https://odysee.com/@SomeChannel:8/free-tv:342fd11c8a",
  "claimId": "342fd11c8a...",
  "channel": "@SomeChannel",
  "channelTitle": "Some Channel",
  "durationSec": 45,
  "releaseTime": "2026-09-18T01:46:49+00:00",
  "tags": ["news", "politics"],
  "languages": ["en"],
  "license": "None",
  "thumbnail": "https://thumbnails.odycdn.com/..."
}
```

### Input

| Field | Meaning |
| --- | --- |
| `searchTerms` | Words or phrases to search for |
| `channels` | `@handle` or a full odysee.com channel URL |
| `maxItemsPerQuery` | Cap per term or channel, 1–1000 (default 50) |
| `orderBy` | Newest, trending, most supported, or name |
| `streamType` | Video, audio, or anything |
| `languages` | ISO codes to restrict to, e.g. `en`, `ko` |

### How it works

Odysee's own front end reads from an open JSON-RPC gateway. This Actor calls
the same `claim_search` and `resolve` methods directly, so a row costs a
fraction of what rendering the site would. The gateway caps a page at 50
claims, so larger requests are split into pages rather than quietly truncated.

### Notes

- Only publicly published claims are read. Nothing private, no account needed.
- `releaseTime` is set by the uploader and **can be faked**. A minority of
  claims set it to the 32-bit maximum, which reads as the year 2038 and floats
  them to the top of "newest first". Those rows are flagged with
  `releaseTimeSuspicious: true`. `creationTimestamp` is the chain time and
  cannot be set by the uploader — sort on that when the date has to be real.
- Paging walks a live index, so the same claim can appear on two pages. Rows
  are deduplicated by `claimId` before they reach the dataset.
- Videos without a thumbnail, licence or description return `null` for those
  fields rather than a guess.

# Actor input Schema

## `searchTerms` (type: `array`):

Words or phrases to search Odysee for. Give this, or channel handles below, or both. Each term is paged until the item cap is reached.

## `channels` (type: `array`):

Odysee channels, as @handle or a full odysee.com channel URL. Every published claim of the channel is walked.

## `maxItemsPerQuery` (type: `integer`):

Upper bound per search term or channel. The gateway pages 50 at a time, so larger values simply take more pages.

## `orderBy` (type: `string`):

How the result set is ordered before paging.

## `streamType` (type: `string`):

Which kind of claim to return. Odysee hosts both video and audio; 'Anything' also includes documents and images.

## `languages` (type: `array`):

Restrict to these ISO language codes, e.g. en, ko, es. Leave empty for every language.

## Actor input object example

```json
{
  "searchTerms": [
    "bitcoin",
    "documentary"
  ],
  "channels": [
    "@Odysee",
    "https://odysee.com/@lbry:3f"
  ],
  "maxItemsPerQuery": 50,
  "orderBy": "release_time",
  "streamType": "video",
  "languages": [
    "en"
  ]
}
```

# Actor output Schema

## `items` (type: `string`):

All scraped claims with metadata as JSON.

## `itemsCsv` (type: `string`):

Same dataset exported as CSV, one row per claim.

# 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 = {
    "searchTerms": [
        "politics"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawlyard/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 = { "searchTerms": ["politics"] }

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

```

## MCP server setup

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