yt-research 0.1.0__tar.gz

yt_research-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,66 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  quality:
+    name: Quality
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+      - uses: astral-sh/setup-uv@d0d8abe699bfb85fec6de9f7adb5ae17292296ff # v6
+        with:
+          enable-cache: true
+          version: "0.11.29"
+      - run: uv sync --locked --all-groups
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - run: uv run mypy
+      - run: uv build
+
+  test:
+    name: ${{ matrix.os }} / Python ${{ matrix.python }}
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - os: ubuntu-latest
+            python: "3.11"
+          - os: ubuntu-latest
+            python: "3.12"
+          - os: ubuntu-latest
+            python: "3.13"
+          - os: ubuntu-latest
+            python: "3.14"
+          - os: macos-latest
+            python: "3.11"
+          - os: macos-latest
+            python: "3.14"
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+      - uses: astral-sh/setup-uv@d0d8abe699bfb85fec6de9f7adb5ae17292296ff # v6
+        with:
+          enable-cache: true
+          python-version: ${{ matrix.python }}
+          version: "0.11.29"
+      - run: uv sync --locked --all-groups
+      - run: uv run pytest --cov=yt_research --cov-report=term-missing
+      - run: uv build
+      - name: Smoke test built wheel
+        shell: bash
+        run: |
+          uv venv .smoke
+          uv pip install --python .smoke dist/*.whl
+          .smoke/bin/yt-research --help

yt_research-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,72 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+      - uses: astral-sh/setup-uv@d0d8abe699bfb85fec6de9f7adb5ae17292296ff # v6
+        with:
+          version: "0.11.29"
+      - run: uv sync --locked --all-groups
+      - name: Verify tag matches package version
+        env:
+          RELEASE_TAG: ${{ github.ref_name }}
+        run: |
+          uv run python - <<'PY'
+          import os
+          import tomllib
+          from pathlib import Path
+
+          version = tomllib.loads(Path("pyproject.toml").read_text())["project"]["version"]
+          expected = f"v{version}"
+          if os.environ["RELEASE_TAG"] != expected:
+              raise SystemExit(f"release tag must be {expected}")
+          PY
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - run: uv run mypy
+      - run: uv run pytest
+      - run: uv build
+      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
+        with:
+          name: python-distributions
+          path: dist/
+          if-no-files-found: error
+
+  publish-pypi:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/yt-research/
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
+        with:
+          name: python-distributions
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+
+  github-release:
+    needs: publish-pypi
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
+        with:
+          name: python-distributions
+          path: dist/
+      - name: Create GitHub release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: gh release create "${GITHUB_REF_NAME}" dist/* --generate-notes --verify-tag

yt_research-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.coverage
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+.venv/
+.smoke*/
+build/
+dist/
+htmlcov/
+.DS_Store
+.env

yt_research-0.1.0/CHANGELOG.md

@@ -0,0 +1,18 @@
+# Changelog
+
+All notable changes to this project are documented here. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-07-31
+
+### Added
+
+- Added `yt-research --version` for checking the installed release.
+- Initial public CLI for researching public YouTube channels and upload histories.
+- Human-readable tables and stable JSON and CSV output.
+- Native secret-store support and an environment variable for headless use.
+- Synthetic test suite and macOS and Linux continuous integration.
+
+[Unreleased]: https://github.com/vedntp/yt-research/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/vedntp/yt-research/releases/tag/v0.1.0

yt_research-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,18 @@
+# Contributor Covenant Code of Conduct
+
+## Our pledge
+
+We pledge to make participation in this project a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+## Our standards
+
+Examples of behavior that contributes to a positive environment include showing empathy, respecting differing viewpoints, accepting constructive feedback, and focusing on what is best for the community.
+
+Unacceptable behavior includes sexualized language or imagery, trolling, insulting comments, personal or political attacks, public or private harassment, publishing others' private information, and other conduct that could reasonably be considered inappropriate.
+
+## Enforcement
+
+Project maintainers may remove, edit, or reject contributions that do not align with this Code of Conduct. Report unacceptable behavior privately using the process in [SECURITY.md](SECURITY.md). Reports will be reviewed promptly and handled with respect for the reporter's privacy and safety.
+
+This policy is adapted from Contributor Covenant 2.1.
+

yt_research-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,28 @@
+# Contributing
+
+Thank you for helping improve `yt-research`.
+
+## Development setup
+
+Install [uv](https://docs.astral.sh/uv/), clone the repository, and run:
+
+```console
+uv sync
+uv run pytest
+uv run ruff check .
+uv run ruff format --check .
+uv run mypy
+```
+
+Tests must use synthetic data and must not call the live YouTube API. Keep real channel names, credentials, and API responses out of fixtures and bug reports.
+
+## Pull requests
+
+- Open an issue before large changes so the design can be discussed.
+- Keep each pull request focused and add tests for changed behavior.
+- Update documentation when the public command or output interface changes.
+- Add a changelog entry under `Unreleased` for user-visible changes.
+- Ensure all checks pass on Python 3.11 or newer.
+
+By participating, you agree to follow the [Code of Conduct](CODE_OF_CONDUCT.md).
+

yt_research-0.1.0/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 vp275
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

yt_research-0.1.0/PKG-INFO

@@ -0,0 +1,158 @@
+Metadata-Version: 2.5
+Name: yt-research
+Version: 0.1.0
+Summary: Research public YouTube channels from the command line
+Project-URL: Homepage, https://github.com/vedntp/yt-research
+Project-URL: Documentation, https://github.com/vedntp/yt-research/tree/main/docs
+Project-URL: Issues, https://github.com/vedntp/yt-research/issues
+Project-URL: Source, https://github.com/vedntp/yt-research
+Author: vedant
+License: MIT License
+        
+        Copyright (c) 2026 vp275
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+        
+License-File: LICENSE
+Keywords: cli,data-api,research,youtube
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: httpx<1,>=0.27
+Requires-Dist: keyring<27,>=25
+Requires-Dist: platformdirs<5,>=4
+Requires-Dist: pydantic<3,>=2.8
+Requires-Dist: rich<15,>=13.7
+Requires-Dist: typer<1,>=0.12
+Description-Content-Type: text/markdown
+
+# yt-research
+
+`yt-research` is an open source command-line tool for exploring public YouTube channel metadata and upload histories. It produces readable terminal tables for people and stable JSON or CSV for scripts and agents.
+
+> [!IMPORTANT]
+> This project is under active development. Version 0.1.0 is the first public interface and may evolve before 1.0.
+
+## What it does
+
+- Resolve a channel by handle, channel ID, or channel URL.
+- Search for channel candidates without silently choosing an ambiguous match.
+- Walk a channel's complete public uploads playlist.
+- Filter videos by title text or UTC publication date.
+- Sort by publication date, views, or likes.
+- Export versioned JSON and fixed-column CSV.
+
+`yt-research` uses the official YouTube Data API v3. You provide your own API key, and the tool only requests public data.
+
+## Install
+
+Python 3.11 or newer is required. The supported platforms are macOS and Linux.
+
+```console
+pipx install yt-research
+```
+
+Alternatively, use `uv`:
+
+```console
+uv tool install yt-research
+```
+
+Or run it without a persistent installation:
+
+```console
+uvx yt-research --help
+```
+
+For a development checkout:
+
+```console
+git clone https://github.com/vedntp/yt-research.git
+cd yt-research
+uv sync
+uv run yt-research --help
+```
+
+## Configure an API key
+
+Create an API key for the YouTube Data API v3, then store it in your operating system's native secret store:
+
+```console
+yt-research auth set
+yt-research auth status
+```
+
+For CI or headless Linux, set the environment variable instead:
+
+```console
+export YT_RESEARCH_API_KEY="your-api-key"
+```
+
+The environment variable takes precedence over the native secret store. See [API key setup](docs/api-key-setup.md) for complete instructions and security guidance.
+
+## Quick start
+
+Use a fictional placeholder handle in examples, replacing it with the public channel you want to research:
+
+```console
+yt-research channel info @examplecreator
+yt-research channel search "Example Creator"
+yt-research videos latest @examplecreator --limit 20
+yt-research videos top @examplecreator --year 2026 --limit 10
+yt-research videos first @examplecreator --match "tutorial"
+yt-research videos list @examplecreator --from 2025-01-01 --format json
+```
+
+When stdout is a terminal, results default to a table. Redirected output defaults to JSON:
+
+```console
+yt-research videos list @examplecreator > videos.json
+yt-research videos list @examplecreator --format csv --output videos.csv
+```
+
+Diagnostics and warnings are written to stderr, so JSON and CSV on stdout remain machine-readable.
+
+## Documentation
+
+- [Command reference](docs/commands.md)
+- [JSON output contract](docs/json-contract.md)
+- [API key setup](docs/api-key-setup.md)
+- [Troubleshooting](docs/troubleshooting.md)
+- [Optional Codex integration](integrations/codex/README.md)
+
+## Privacy and limitations
+
+The tool does not use OAuth or access private account data. Version 0.1.0 does not download videos, retrieve transcripts or comments, classify Shorts, or run as a hosted service. API calls consume quota from the Google Cloud project associated with your key.
+
+## Contributing
+
+Contributions are welcome. Read [CONTRIBUTING.md](CONTRIBUTING.md), the [Code of Conduct](CODE_OF_CONDUCT.md), and the [Security Policy](SECURITY.md) before opening a contribution.
+
+## License
+
+MIT. See [LICENSE](LICENSE).

yt_research-0.1.0/README.md

@@ -0,0 +1,105 @@
+# yt-research
+
+`yt-research` is an open source command-line tool for exploring public YouTube channel metadata and upload histories. It produces readable terminal tables for people and stable JSON or CSV for scripts and agents.
+
+> [!IMPORTANT]
+> This project is under active development. Version 0.1.0 is the first public interface and may evolve before 1.0.
+
+## What it does
+
+- Resolve a channel by handle, channel ID, or channel URL.
+- Search for channel candidates without silently choosing an ambiguous match.
+- Walk a channel's complete public uploads playlist.
+- Filter videos by title text or UTC publication date.
+- Sort by publication date, views, or likes.
+- Export versioned JSON and fixed-column CSV.
+
+`yt-research` uses the official YouTube Data API v3. You provide your own API key, and the tool only requests public data.
+
+## Install
+
+Python 3.11 or newer is required. The supported platforms are macOS and Linux.
+
+```console
+pipx install yt-research
+```
+
+Alternatively, use `uv`:
+
+```console
+uv tool install yt-research
+```
+
+Or run it without a persistent installation:
+
+```console
+uvx yt-research --help
+```
+
+For a development checkout:
+
+```console
+git clone https://github.com/vedntp/yt-research.git
+cd yt-research
+uv sync
+uv run yt-research --help
+```
+
+## Configure an API key
+
+Create an API key for the YouTube Data API v3, then store it in your operating system's native secret store:
+
+```console
+yt-research auth set
+yt-research auth status
+```
+
+For CI or headless Linux, set the environment variable instead:
+
+```console
+export YT_RESEARCH_API_KEY="your-api-key"
+```
+
+The environment variable takes precedence over the native secret store. See [API key setup](docs/api-key-setup.md) for complete instructions and security guidance.
+
+## Quick start
+
+Use a fictional placeholder handle in examples, replacing it with the public channel you want to research:
+
+```console
+yt-research channel info @examplecreator
+yt-research channel search "Example Creator"
+yt-research videos latest @examplecreator --limit 20
+yt-research videos top @examplecreator --year 2026 --limit 10
+yt-research videos first @examplecreator --match "tutorial"
+yt-research videos list @examplecreator --from 2025-01-01 --format json
+```
+
+When stdout is a terminal, results default to a table. Redirected output defaults to JSON:
+
+```console
+yt-research videos list @examplecreator > videos.json
+yt-research videos list @examplecreator --format csv --output videos.csv
+```
+
+Diagnostics and warnings are written to stderr, so JSON and CSV on stdout remain machine-readable.
+
+## Documentation
+
+- [Command reference](docs/commands.md)
+- [JSON output contract](docs/json-contract.md)
+- [API key setup](docs/api-key-setup.md)
+- [Troubleshooting](docs/troubleshooting.md)
+- [Optional Codex integration](integrations/codex/README.md)
+
+## Privacy and limitations
+
+The tool does not use OAuth or access private account data. Version 0.1.0 does not download videos, retrieve transcripts or comments, classify Shorts, or run as a hosted service. API calls consume quota from the Google Cloud project associated with your key.
+
+## Contributing
+
+Contributions are welcome. Read [CONTRIBUTING.md](CONTRIBUTING.md), the [Code of Conduct](CODE_OF_CONDUCT.md), and the [Security Policy](SECURITY.md) before opening a contribution.
+
+## License
+
+MIT. See [LICENSE](LICENSE).

yt_research-0.1.0/SECURITY.md

@@ -0,0 +1,16 @@
+# Security Policy
+
+## Supported versions
+
+Security fixes are provided for the latest released minor version.
+
+## Reporting a vulnerability
+
+Do not open a public issue for a suspected vulnerability or exposed credential. Use GitHub's private vulnerability reporting feature on the repository Security tab. Include reproduction steps, affected versions, impact, and any suggested mitigation.
+
+You can expect acknowledgement within seven days. Please allow time for investigation and a coordinated release before public disclosure.
+
+## Credential safety
+
+Never include a YouTube API key in an issue, test fixture, screenshot, log, or pull request. If a key is exposed, revoke it immediately in Google Cloud Console and create a replacement.
+

yt_research-0.1.0/docs/api-key-setup.md

@@ -0,0 +1,25 @@
+# API key setup
+
+`yt-research` requires a YouTube Data API v3 key for public API requests.
+
+1. Create or select a project in Google Cloud Console.
+2. Enable **YouTube Data API v3** for the project.
+3. Create an API key under **APIs & Services > Credentials**.
+4. Restrict the key to the YouTube Data API v3. Apply any additional restrictions that fit your environment.
+5. Run `yt-research auth set` and paste the key into the hidden prompt.
+
+Check or remove the stored credential with:
+
+```console
+yt-research auth status
+yt-research auth delete
+```
+
+On a headless Linux host without a native keyring, use an environment variable:
+
+```console
+export YT_RESEARCH_API_KEY="your-api-key"
+```
+
+The environment variable takes precedence over the keyring. Avoid placing it in shell history, committed environment files, or CI logs. Use your CI provider's encrypted secret storage.
+

yt_research-0.1.0/docs/commands.md

@@ -0,0 +1,45 @@
+# Command reference
+
+Run `yt-research COMMAND --help` for the authoritative options installed with your version.
+
+## Authentication
+
+- `auth set` stores an API key in the native secret store.
+- `auth status` reports whether a key is available and where it came from, without displaying it.
+- `auth delete` removes the key from the native secret store.
+
+## Channels
+
+- `channel info CHANNEL` retrieves public channel metadata. `CHANNEL` may be a handle, channel ID, or supported channel URL.
+- `channel search QUERY` returns channel candidates. It never silently selects one.
+
+## Videos
+
+- `videos list CHANNEL` lists all matching uploads, newest first by default.
+- `videos latest CHANNEL` returns the newest matching uploads, 20 by default.
+- `videos top CHANNEL` returns the most-viewed matching uploads, 10 by default.
+- `videos first CHANNEL` returns the oldest matching upload.
+
+Video commands accept:
+
+- `--match TEXT` for case-insensitive title substring matching.
+- `--year YYYY`, or the mutually exclusive `--from YYYY-MM-DD` and `--to YYYY-MM-DD` UTC boundaries.
+- `--sort published-asc|published-desc|views|likes`.
+- `--limit N`.
+- `--format table|json|csv`.
+- `--output PATH` to write the result to a file.
+- `--refresh` to bypass cached channel identity data.
+- `--no-color` to disable terminal styling.
+
+Plain channel names are intentionally rejected by research commands. Use `channel search`, then pass an exact handle or ID.
+
+## Exit codes
+
+| Code | Meaning |
+| ---: | --- |
+| 0 | Success |
+| 2 | Invalid arguments |
+| 3 | Missing or rejected credentials |
+| 4 | Channel or video not found, or ambiguous input |
+| 5 | Network, quota, or upstream YouTube failure |
+

yt_research-0.1.0/docs/json-contract.md

@@ -0,0 +1,31 @@
+# JSON output contract
+
+JSON output is intended for scripts and agents. Version 0.1.0 emits `schema_version: 1` and writes diagnostics only to stderr.
+
+```json
+{
+  "schema_version": 1,
+  "command": "videos.top",
+  "fetched_at": "2026-07-17T12:00:00Z",
+  "channel": {},
+  "query": {},
+  "items": [],
+  "meta": {
+    "matched": 0,
+    "returned": 0,
+    "requests": {},
+    "warnings": []
+  }
+}
+```
+
+Consumers may ignore unknown object properties. A future incompatible change will increment `schema_version`. Optional API statistics, such as likes or comments, are `null` when unavailable. An absent optional statistic does not remove the video from `items`.
+
+Timestamps use ISO 8601 in UTC. Request counts are estimates grouped by endpoint, not authoritative remaining Google quota.
+
+CSV output has these fixed columns:
+
+```text
+video_id,title,url,published_at,duration_seconds,views,likes,comments
+```
+

yt_research-0.1.0/docs/troubleshooting.md

@@ -0,0 +1,26 @@
+# Troubleshooting
+
+## No API key is available
+
+Run `yt-research auth set`. On headless Linux, set `YT_RESEARCH_API_KEY` in the process environment instead.
+
+## The API rejects the key
+
+Confirm that YouTube Data API v3 is enabled in the key's Google Cloud project and that API restrictions allow it. Revoke and replace any key that may have been exposed.
+
+## Quota has been exceeded
+
+Quota is managed by Google Cloud. Wait for quota reset or review the project's quota allocation. `yt-research` reports request estimates but cannot determine the authoritative quota remaining.
+
+## A channel name is ambiguous
+
+Research commands require a channel handle, channel ID, or supported URL. Run `yt-research channel search "name"`, inspect the candidates, and retry with the exact handle or ID.
+
+## A statistic is null
+
+YouTube may hide or omit likes, comments, or subscriber counts. The tool preserves the record and represents the unavailable value as `null`.
+
+## Results appear stale
+
+Live video and channel statistics are fetched for each research operation. If a channel identity has changed, add `--refresh` to bypass the local identity cache.
+

yt_research-0.1.0/integrations/codex/README.md

@@ -0,0 +1,15 @@
+# Codex integration
+
+Codex can call `yt-research` as a local research tool. This integration is optional and never modifies global Codex configuration automatically.
+
+1. Install and configure `yt-research`.
+2. Copy the sample instructions below into the relevant workspace `AGENTS.md`, adapting them to your project.
+3. Ensure the Codex process can access `YT_RESEARCH_API_KEY` or the native secret store.
+
+```markdown
+## YouTube research
+
+Use the relevant `yt-research` command with `--format json` for public YouTube channel and upload-history research, for example `yt-research videos list @channelhandle --format json`. Pass an exact channel handle, ID, or URL. Use `yt-research channel search` only when the user supplied an ambiguous channel name. Treat stdout as structured data and stderr as diagnostics.
+```
+
+Do not ask Codex to expose, print, or persist the API key.