# Odysee Channel Lookup: Followers, Claims, Recent Videos (`accountable_eel/odysee-channel-lookup`) Actor

Lookup Odysee channels: follower count, total claims, support stake, contact email, tags, and recent video uploads. Supports monitoring for new uploads.

- **URL**: https://apify.com/accountable_eel/odysee-channel-lookup.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Social media, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 channel returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Channel Lookup: Followers, Claims, Recent Videos

**Lookup Odysee channels: follower count, total claims, support stake, contact email, tags, and recent video uploads.**

Paste a list of Odysee channels (handles, profile URLs, or LBRY URIs) and get a structured table with follower count, total claims, LBC support stake, contact email, tags, and recent video uploads. Optionally monitor channels for new uploads since your last run.

### Who uses this

- **Media and creator researchers** tracking creator growth, audience size, and activity across decentralized video platforms.
- **Brand marketers and sponsorship teams** verifying an Odysee channel's follower count and recent upload frequency before outreach.
- **Content archivists and analysts** monitoring new video uploads by creator or channel into Google Sheets, Slack, or automated pipelines.

### Example output

| handle | title | followerCount | claimsInChannel | supportAmount | odyseeUrl |
|---|---|---|---|---|---|
| @Odysee | Odysee | 2,234,607 | 137 | 251,401.38 | https://odysee.com/@Odysee:8 |

Every row also carries channel description, contact email, website, avatar and cover images, joined date, LBRY canonical URL, and recent uploads with titles, release dates, durations, and thumbnails.

### What it costs

About **$2.00 per 1,000 channels found** ($0.002 per channel), and a channel that does not exist or fails to load is free. First runs fit inside Apify's monthly free tier.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `channels` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~odysee-channel-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"channels":["@Odysee"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "channels": [
    "@Odysee"
  ]
}
```

Enter channel handles or URLs (one per line). Accepts @channel, https://odysee.com/@channel, or lbry://@channel. Accepted formats: @Odysee, https://odysee.com/@Odysee, lbry://@Odysee.

### Output

| query | found | status | channelId | handle | title | description | followerCount | claimsInChannel | supportAmount | tags | websiteUrl | email | avatarUrl | coverUrl | joinedDate | canonicalUrl | odyseeUrl | recentVideos | newVideoCount | videoId | videoTitle | videoDescription | videoReleaseTime | videoDuration | videoThumbnailUrl | videoUrl | isNew | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| @Odysee | true | OK | <channel id> | <handle> | <channel name> | <description> | <followers> | <total claims> | \<total support (lbc)> | <tags> | <website url> | <email> | <avatar image> | <cover image> | <joined date> | <canonical url> | <odysee url> | \<recent uploads (full list)> | <new uploads since last run> | <video id> | <video title> | <video description> | <video release date> | \<video duration (seconds)> | <video thumbnail> | <video url> | \<is this video new?> | <first seen on a run> | 1970-01-01T00:00:00.000Z |

A miss comes back as a row with `"found": false` and is never charged. Missing fields are `null`, never `0` or empty strings.

### Pricing

### Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token, and no account of your own beyond an Apify login.

**Lookup Odysee official channel with 10 recent uploads.** The default seed input.

```json
{
  "channels": ["@Odysee"],
  "includeRecentVideos": 10
}
```

**Bulk lookup multiple channels for follower and claim stats only (skipping video fetch).**

```json
{
  "channels": [
    "@Odysee",
    "https://odysee.com/@veritasium",
    "lbry://@rossmanngroup"
  ],
  "includeRecentVideos": 0
}
```

**Upload monitor: check for new videos since last run.**

```json
{
  "channels": ["@Odysee"],
  "includeRecentVideos": 10,
  "onlyNewSinceLastRun": true
}
```

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~odysee-channel-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"channels":["@Odysee"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~odysee-channel-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"channels":["@Odysee"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~odysee-channel-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"channels":["{{channel}}"]}`, mapping the row's channel into the `channels` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "odysee scraper" — the agent will find and run this actor.

# Actor input Schema

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

Enter channel handles or URLs (one per line). Accepts @channel, https://odysee.com/@channel, or lbry://@channel. Accepted formats: @Odysee, https://odysee.com/@Odysee, lbry://@Odysee. You're only charged for the ones we actually find — a miss costs nothing.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

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

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `onlyNewSinceLastRun` (type: `boolean`):

Turns this actor into an upload monitor. A video counts as new when its Odysee claim ID has not been returned for that channel by a previous run of the same watchlist. Already-seen uploads are dropped from the list, so your Slack or n8n step only ever sees fresh videos. Its stats row always comes back (with an empty upload list when nothing was posted), and a run with nothing new for a channel is not charged. The first run has nothing to compare against, so it returns every recent upload and remembers it. Only the uploads inside 'How many recent uploads to include' are compared, so keep that at 10 or more for channels that post several times a day.

## `deltaName` (type: `string`):

Leave empty and we derive one from your channel list, so two schedules watching different channels keep separate memories. Editing the list then starts a fresh watchlist that re-announces each channel's recent uploads once; type your own name to keep one memory across list edits.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each video found gets its own row instead of being grouped under its channel. You're still only charged once per channel, no matter how many rows it produces.

## `includeRecentVideos` (type: `integer`):

Each channel's row includes its N most recent uploads (claim ID, title, description, release date, duration, thumbnail). Set to 0 to skip the extra request entirely and get channel stats only.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## Actor input object example

```json
{
  "channels": [
    "@Odysee"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "onlyNewSinceLastRun": false,
  "deltaName": "",
  "columns": [
    "channelId",
    "handle",
    "title",
    "description",
    "followerCount",
    "claimsInChannel",
    "supportAmount",
    "tags",
    "websiteUrl",
    "email",
    "avatarUrl",
    "coverUrl",
    "joinedDate",
    "canonicalUrl",
    "odyseeUrl",
    "recentVideos",
    "newVideoCount",
    "videoId",
    "videoTitle",
    "videoDescription",
    "videoReleaseTime",
    "videoDuration",
    "videoThumbnailUrl",
    "videoUrl",
    "isNew",
    "firstSeenAt"
  ],
  "expandRows": false,
  "includeRecentVideos": 10,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

No description

# 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 = {
    "channels": [
        "@Odysee"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/odysee-channel-lookup").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 = {
    "channels": ["@Odysee"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/odysee-channel-lookup").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 '{
  "channels": [
    "@Odysee"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/odysee-channel-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/odysee-channel-lookup"
        }
    }
}
```

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/kjHU6nFl2eUgeequY/builds/qQUlyfz0Wp28TdTvu/openapi.json