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:

   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

{
  "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							<total support (lbc)>									<recent uploads (full list)>						<video duration (seconds)>			<is this video new?>		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.

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

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

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

Upload monitor: check for new videos since last run.

{
  "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.

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.