Odysee Video Search by Keyword, Channel & Tag: MCP config, n8n workflow and API
Odysee video records pair titles and channel identities with viewing links, publication dates, durations and optional public engagement counters. A research agent tracking open source coverage can collect keyword matches and prepare a dated viewing list. Store data checked 2026-11-13.
Supply mode, then identify the source with keyword, channel, tag or videoUrls according to the collection mode.
Fastest route, in Claude Code:
claude mcp add --transport http odysee-video-search-by-keyword-channel-and-tag "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag" One click, signs in with Apify on first use:
Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):
npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag" --name odysee-video-search-by-keyword-channel-and-tag Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
- MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
- n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- example input: 5 of 5 (All 1 required input field is present; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
- code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
- SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)
Good jobs for this Actor
- Create a keyword research digest using title, channelName, publishedAt and viewUrl.
- Browse a creator's uploads and organize the results by publication date and durationSeconds.
- Collect a science tag feed with includeStats enabled and compare views and channelFollowerCount.
Prompts to try
- Search Odysee with mode set to search and keyword set to open source, then return titles, channels and viewing links.
What a run costs
Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-13.
| Results in one run | Start | Results | Run total |
|---|---|---|---|
| 10 | $0.40 | $0.010 | $0.41 |
| 100 | $0.40 | $0.10 | $0.50 |
| 1,000 | $0.40 | $0.99 | $1.39 |
Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.
MCP config
One URL works in every client: https:/. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:
Claude Code configterminal or .mcp.json
claude mcp add --transport http odysee-video-search-by-keyword-channel-and-tag "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag" Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup
Claude Desktop configclaude_desktop_config.json
{
"mcpServers": {
"odysee-video-search-by-keyword-channel-and-tag": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--tools",
"fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN"
}
}
}
} Easiest: open Customize, then Connectors, choose Add custom connector, paste the server URL (the ChatGPT tab shows it on its own) and sign in to Apify. Full Claude Desktop setup
Cursor config~/.cursor/mcp.json
{
"mcpServers": {
"odysee-video-search-by-keyword-channel-and-tag": {
"url": "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag",
"headers": {
"Authorization": "Bearer ${env:APIFY_TOKEN}"
}
}
}
} Save as ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project. Merge with servers you already have. Full Cursor setup
VS Code config.vscode/mcp.json
{
"inputs": [
{
"type": "promptString",
"id": "apify-token",
"description": "Apify API token",
"password": true
}
],
"servers": {
"odysee-video-search-by-keyword-channel-and-tag": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag",
"headers": {
"Authorization": "Bearer ${input:apify-token}"
}
}
}
} Save as .vscode/mcp.json in your workspace. Full VS Code setup
ChatGPT configPlugins > Add custom MCP server
https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag In ChatGPT on the web, open Plugins, select + and choose Add custom MCP server. Full ChatGPT setup
Codex CLI config~/.codex/config.toml
[mcp_servers.odysee-video-search-by-keyword-channel-and-tag]
url = "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag"
bearer_token_env_var = "APIFY_TOKEN" Add the block to ~/.codex/config.toml, or .codex/config.toml in a project. Full Codex CLI setup
Gemini CLI configterminal (writes ~/.gemini/settings.json)
gemini mcp add -t http -s user -H "Authorization: Bearer $APIFY_TOKEN" odysee-video-search-by-keyword-channel-and-tag "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag" Export APIFY_TOKEN first: the shell expands it and Gemini CLI saves the header, token included, in plain text in ~/.gemini/settings.json (keep that file private). In PowerShell write $env:APIFY_TOKEN instead of $APIFY_TOKEN. Drop -s user to save it in the project's .gemini/settings.json. Full Gemini CLI setup
n8n AI Agent configMCP Client Tool node
https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag Add an AI Agent node, then attach an MCP Client Tool node to its tool input. Full n8n AI Agent setup
Tools your agent gets
Listed by Apify's MCP server 0.21.9 for this exact URL on 2026-11-12 (a tools/list call; nothing was run).
fetch-actor-detailsreads the input schemaget-actor-runchecks a run's statusget-dataset-itemsreads a run's resultsget-key-value-store-recordreads a stored record such as a file or summaryabort-actor-runstops a run that is still goingvexaloom-labs--odysee-video-search-by-keyword-channel-and-tagruns the Actor and returns its results
n8n workflow
A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.
- Run by hand
- Every day
- Run Apify Actor
n8n workflowodysee-video-search-by-keyword-channel-and-tag.n8n.json
{
"name": "Odysee Video Search by Keyword, Channel & Tag to n8n only",
"nodes": [
{
"id": "b8a576ca-05be-42ba-a846-288384bff18b",
"name": "Run by hand",
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
0,
0
],
"parameters": {}
},
{
"id": "4e483d6a-d38b-4454-a031-0a517cc4287b",
"name": "Every day",
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
0,
200
],
"parameters": {
"rule": {
"interval": [
{
"triggerAtHour": 8
}
]
}
},
"notes": "Activate the workflow to run on this schedule."
},
{
"id": "6c2531ce-51c7-47b1-a863-8260e5d59363",
"name": "Run Apify Actor",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
260,
100
],
"parameters": {
"method": "POST",
"url": "https://api.apify.com/v2/actors/vexaloom-labs~odysee-video-search-by-keyword-channel-and-tag/run-sync-get-dataset-items",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\n \"mode\": \"search\",\n \"keyword\": \"open source\",\n \"channel\": \"@veritasium\",\n \"tag\": \"science\",\n \"orderBy\": \"release_time\",\n \"mediaType\": \"video\",\n \"maxItems\": 3,\n \"includeStats\": true\n}",
"options": {
"timeout": 310000
}
},
"notes": "Actor: vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
"notesInFlow": false
},
{
"id": "1f579542-76ca-4b60-a666-b2b98cdaadbf",
"name": "Setup",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
0,
-370
],
"parameters": {
"content": "## Odysee Video Search by Keyword, Channel & Tag\n\nSource: [vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag](https://apify.com/vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
"height": 340,
"width": 460,
"color": 6
}
}
],
"connections": {
"Run by hand": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
},
"Every day": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
}
},
"pinData": {},
"active": false,
"settings": {
"executionOrder": "v1"
},
"meta": {
"templateCredsSetupCompleted": false
},
"tags": []
} Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.
All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.
Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).
Download the long-run workflow11 of 11 checks pass, not executed
Call it from code
Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.
curl
curl -X POST "https://api.apify.com/v2/actors/vexaloom-labs~odysee-video-search-by-keyword-channel-and-tag/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"mode":"search","keyword":"open source","channel":"@veritasium","tag":"science","orderBy":"release_time","mediaType":"video","maxItems":3,"includeStats":true}' Install: pip install "apify-client>=3"
Python
import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
run_input = {
"mode": "search",
"keyword": "open source",
"channel": "@veritasium",
"tag": "science",
"orderBy": "release_time",
"mediaType": "video",
"maxItems": 3,
"includeStats": True,
}
run = client.actor("vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag").call(run_input=run_input)
if run is None:
raise RuntimeError("The Actor run could not be started")
print(run.status, "dataset", run.default_dataset_id)
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item) Install: npm install apify-client
JavaScript
import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
"mode": "search",
"keyword": "open source",
"channel": "@veritasium",
"tag": "science",
"orderBy": "release_time",
"mediaType": "video",
"maxItems": 3,
"includeStats": true
};
const run = await client.actor("vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]); In an agent framework
The same Actor and input in the frameworks Apify documents: as a LangChain or CrewAI tool, a LlamaIndex document loader, or through the scoped MCP URL in the OpenAI Agents SDK and Mastra. Each snippet is run against the current package before it is shown (stub API, nothing billed). Framework guides
Install: pip install langchain-apify
LangChain
# Reads APIFY_TOKEN from the environment.
from langchain_apify import ApifyActorsTool
tool = ApifyActorsTool("vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag")
items = tool.invoke({"run_input": {
"mode": "search",
"keyword": "open source",
"channel": "@veritasium",
"tag": "science",
"orderBy": "release_time",
"mediaType": "video",
"maxItems": 3,
"includeStats": True,
}})
print(len(items), "records", items[:1])
# Give the same tool to an agent (pip install langchain langchain-openai):
# from langchain.agents import create_agent
# agent = create_agent(ChatOpenAI(model="gpt-5.4-mini"), [tool]) Install: pip install 'crewai[tools]' langchain-apify
CrewAI
# Reads APIFY_API_TOKEN (Apify token) and OPENAI_API_KEY from the environment.
from crewai import Agent, Crew, Task
from crewai_tools import ApifyActorsTool
tool = ApifyActorsTool(actor_name="vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag")
agent = Agent(
role="Data researcher",
goal="Collect records with the Apify Actor and summarise them",
backstory="You call Apify Actors to get live web data.",
tools=[tool],
)
task = Task(
description="Use Odysee Video Search by Keyword, Channel & Tag to get a few records and summarise what came back, with links. Call the tool with this run_input: {\"mode\":\"search\",\"keyword\":\"open source\",\"channel\":\"@veritasium\",\"tag\":\"science\",\"orderBy\":\"release_time\",\"mediaType\":\"video\",\"maxItems\":3,\"includeStats\":true}",
agent=agent,
expected_output="A short summary of the records with their links.",
)
print(Crew(agents=[agent], tasks=[task]).kickoff()) Install: pip install apify-client llama-index-core llama-index-readers-apify
LlamaIndex
import json
import os
from llama_index.core import Document
from llama_index.readers.apify import ApifyActor
reader = ApifyActor(os.environ["APIFY_TOKEN"])
documents = reader.load_data(
actor_id="vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag",
run_input={
"mode": "search",
"keyword": "open source",
"channel": "@veritasium",
"tag": "science",
"orderBy": "release_time",
"mediaType": "video",
"maxItems": 3,
"includeStats": True,
},
dataset_mapping_function=lambda item: Document(text=json.dumps(item), metadata={"url": item.get("viewUrl")}),
)
print(len(documents), "documents") Install: pip install openai-agents
OpenAI Agents SDK
import asyncio
import os
from agents import Agent, Runner
from agents.mcp import MCPServerStreamableHttp
async def main() -> None:
async with MCPServerStreamableHttp(
name="Apify",
params={
"url": "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag",
"headers": {"Authorization": f"Bearer {os.environ['APIFY_TOKEN']}"},
"timeout": 120,
},
cache_tools_list=True,
) as server:
tools = await server.list_tools()
print("tools:", [t.name for t in tools])
agent = Agent(name="Assistant", instructions="Use the Apify tools to get live data.", mcp_servers=[server])
result = await Runner.run(agent, "Use Odysee Video Search by Keyword, Channel & Tag to get a few records and summarise what came back, with links.")
print(result.final_output)
asyncio.run(main()) Install: npm install @mastra/core @mastra/mcp
Mastra
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
const mcp = new MCPClient({
servers: {
apify: {
url: new URL("https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag"),
requestInit: { headers: { Authorization: `Bearer ${process.env.APIFY_TOKEN}` } },
},
},
timeout: 300_000, // Actor runs can take minutes
});
const tools = await mcp.listTools();
console.log("tools:", Object.keys(tools));
const agent = new Agent({ id: "apify-agent", name: "Apify agent", instructions: "Use the Apify tools to get live data.", model: "openai/gpt-4o-mini", tools });
const result = await agent.generate("Use Odysee Video Search by Keyword, Channel & Tag to get a few records and summarise what came back, with links.");
console.log(result.text);
await mcp.disconnect(); Example input
These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.
Actor inputinput.json
{
"mode": "search",
"keyword": "open source",
"channel": "@veritasium",
"tag": "science",
"orderBy": "release_time",
"mediaType": "video",
"maxItems": 3,
"includeStats": true
} | Field | Type | What it does |
|---|---|---|
mode required | string (4 options) | Choose what to collect: a keyword search, a channel's uploads, a tag feed, or details for specific videos. |
keyword | string | Keyword used by mode=search. Supports ordinary words and non-English text. Odysee returns at most about 550 results per keyword. |
channel | string | Used by mode=byChannel. Accepts an @handle (@veritasium), an Odysee channel URL, an lbry:// channel URL, or a channel claim ID. |
tag | string | Used by mode=byTag. Tag text without the leading #, for example science, technology or gaming. |
orderBy | string (5 options) | Sort order for channel and tag modes. Keyword search always uses Odysee's relevance ranking. |
mediaType | string (5 options) | Filter channel, tag and keyword results by Odysee stream type. Details mode returns the referenced item as-is. |
maxItems | integer | Maximum number of records to collect across the whole run. |
includeStats | boolean | Add view count, likes, dislikes and channel follower count. These numbers come from Odysee's public counters and add a few small requests per record. |
1 more optional field on the Store input tab.
What your agent receives
Each run returns a list of records. The Actor publishes 7 fields, starting with title, channelName, viewUrl, publishedAt.
| Field |
|---|
title |
channelName |
viewUrl |
publishedAt |
durationSeconds |
views |
channelFollowerCount |
Agent skill
A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.
SKILL.mdodysee-video-search-by-keyword-channel-and-tag/SKILL.md
---
name: odysee-video-search-by-keyword-channel-and-tag
description: "Odysee video records with title, channel identity, description, thumbnail, duration, tags, publication date and engagement counters. Runs the Apify Actor vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag. Use when the user needs Odysee Video data with fields such as title, channelName, viewUrl, publishedAt, durationSeconds, views and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
actor: "vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag"
store-url: "https://apify.com/vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag"
---
# Odysee Video Search by Keyword, Channel & Tag
Use this skill to fetch Odysee Video data with the Apify Actor `vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag` and work with the returned rows.
## Before running
1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.
## Input fields
| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `search`, `byChannel`, `byTag`, `details`, required | Choose what to collect: a keyword search, a channel's uploads, a tag feed, or details for specific videos. |
| `keyword` | string | Keyword used by mode=search. Supports ordinary words and non-English text. Odysee returns at most about 550 results per keyword. |
| `channel` | string | Used by mode=byChannel. Accepts an @handle (@veritasium), an Odysee channel URL, an lbry:// channel URL, or a channel claim ID. |
| `tag` | string | Used by mode=byTag. Tag text without the leading #, for example science, technology or gaming. |
| `orderBy` | one of `release_time`, `effective_amount`, `support_amount`, `trending_group`, `trending_mixed` | Sort order for channel and tag modes. Keyword search always uses Odysee's relevance ranking. |
| `mediaType` | one of `video`, `audio`, `document`, `image`, `all` | Filter channel, tag and keyword results by Odysee stream type. Details mode returns the referenced item as-is. |
| `maxItems` | integer | Maximum number of records to collect across the whole run. |
| `includeStats` | boolean | Add view count, likes, dislikes and channel follower count. These numbers come from Odysee's public counters and add a few small requests per record. |
Example `input.json` (the Actor's published prefill):
```json
{
"mode": "search",
"keyword": "open source",
"channel": "@veritasium",
"tag": "science",
"orderBy": "release_time",
"mediaType": "video",
"maxItems": 3,
"includeStats": true
}
```
## Run
```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~odysee-video-search-by-keyword-channel-and-tag/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d @input.json > results.json
```
The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/vexaloom-labs~odysee-video-search-by-keyword-channel-and-tag/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.
## Output
Each item is one record. Published fields include: `title`, `channelName`, `viewUrl`, `publishedAt`, `durationSeconds`, `views`, `channelFollowerCount`.
Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.
- Claude Code: save it as
~/.claude/skills/odysee-video-search-by-keyword-channel-and-tag/SKILL.md, or.claude/skills/odysee-video-search-by-keyword-channel-and-tag/SKILL.mdin a project. - Codex and other agents:
~/.agents/skills/odysee-video-search-by-keyword-channel-and-tag/SKILL.md, or.agents/skills/odysee-video-search-by-keyword-channel-and-tag/in a project. - Or let the skills CLI place it for your agent:
npx skills add https://recipeforagents.com --skill odysee-video-search-by-keyword-channel-and-tag - Set
APIFY_TOKENin the agent's environment.
Troubleshooting
Why does the client say Unauthorized or invalid token?
Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.
Why did my agent's tool list change after an update?
Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.
What happens when the agent sends input the Actor rejects?
The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.
Questions
Can keyword search results be sorted by release time?
Keyword search always uses Odysee's relevance ranking. orderBy controls sorting for channel and tag modes.
How do I request engagement counters?
Enable includeStats to add views, likes, dislikes and channel follower counts. These values come from Odysee's public counters.
How do I connect Odysee Video Search by Keyword, Channel & Tag to Claude?
In Claude Code run: claude mcp add --transport http odysee-video-search-by-keyword-channel-and-tag "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/odysee-video-search-by-keyword-channel-and-tag and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.
What input does Odysee Video Search by Keyword, Channel & Tag need?
The published input schema requires mode. The example on this page uses the Actor's own Store prefill.
What does Odysee Video Search by Keyword, Channel & Tag cost to run?
The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-13. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.
Which tools does the MCP config give my agent?
6 tools: fetch-actor-details, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run, vexaloom-labs--odysee-video-search-by-keyword-channel-and-tag. Apify's MCP server listed them for this exact URL on 2026-11-12.
Made this Actor? Show it is listed
A small badge for your README, docs or Store page that links back here. It is a plain SVG file: no script, no tracking.
More video and streaming Actors
Bilibili Video Search, Ranking & Metadata Scraper
Search Bilibili videos by keyword, look up specific videos by URL or ID, or pull the popular feed and…
6 fields$0.99 per 1,000 resultsDailymotion Video Discovery by Topic & Channel
Search Dailymotion by keyword, browse trending or topic videos, or pull a channel's uploads, with language…
8 fields$0.99 per 1,000 resultsIMDb Top Charts & Advanced Title Search
Search IMDb movies and TV shows, fetch titles by IMDb ID, browse Top 250 and regional charts, or run an…
14 fields$0.99 per 1,000 resultsiQIYI Album Profile & Channel Ranking Scraper
Get iQIYI drama, movie, anime and variety-show details by album ID, pull the top-ranked titles for any…
13 fields$0.99 per 1,000 resultsPexels Stock Media Scraper
Scrape free stock photos and videos from Pexels. Search by keyword, browse curated/popular media, a…
13 fields$0.99 per 1,000 resultsSteam Game Reviews & Playtime Extractor
Pull Steam customer reviews for any game by URL or name, with thumbs up/down verdicts, reviewer playtime…
13 fields$0.99 per 1,000 results