Douyin_TikTok_Download_API
🚀 Self-hosted TikTok & Douyin scraper and no-watermark video downloader, async REST API, MCP server, CLI and web console for posts, profiles, comments and playlists. Self-healing identity pool, PostgreSQL archive, one docker compose up. 抖音、TikTok 数据采集与无水印视频下载 API，自托管，支持 MCP 调用与 Docker 一键部署。
Runssource: GitHubhomepagePythonApache-2.0commit bcbbfa17dcea
Python, Apache-2.0 licensed. The project labels itself: asyncio, crawler, data collection, douyin, douyin api, downloader, fastapi and mcp server.
Douyin_TikTok_Download_API runs. An Argusic agent installed it in 2 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 2960 tests pass (2450 unit + 510 integration), the CLI outputs version 5.0.1 and lists 10 commands, the API server starts and serves healthz/readyz/swagger/console root with 200, the web console SPA is built, and both the PostgreSQL+TimescaleDB and Redis backends and the Go downloader sidecar run.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 97.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- TimescaleDB extension not available for PostgreSQL, migration and 7 integration tests failed5 minutes
- Console SPA web/dist not built, 4 integration tests failed3 minutes
- Go downloader sidecar not built, 24 download integration tests failed3 minutes
- uv not installed1 minute
- DTK_SECRET_KEY not set, 7 unit tests failed1 minute
- Redis auth required by tests, 17 e2e tests errored1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 48 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- uv run pytest tests/unit tests/replay -q: 2450 passed; uv run pytest tests/integration -m integration -q: 510 passed; curl http://127.0.0.1:18002/healthz returned 200, /readyz 200, / 200 (console SPA), /swagger 200; dtk --version reports 5.0.1
- Model tokens used
- 669,844
- Exact commit tested
- bcbbfa17dcea
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Final state: **All 2960 tests pass** (2450 unit/replay + 510 integration), the CLI outputs version … tokens used 669,844 Here's the summary of what was accomplished: The Douyin_TikTok_Download_API (dtk v5.0.1) repository was made fully operational in this container… 1. **uv not installed** — installed uv via `curl -LsSf https://astral.sh/uv/install.sh | sh` 2. **DTK_SECRET_KEY not set** — 7 unit tests failed; fixed by generating a random key 3. **TimescaleDB missing** — migrations failed because the PostgreSQL 16 extracted from deb package… 4. **Redis auth mismatch** — 17 e2e tests errored because tests expect no Redis password; restarted… 5. **Console SPA not built** — 4 tests failed; downloaded node v20.19.0 and built `web/dist` with `… 6. **Go downloader sidecar not built** — 24 download tests failed; downloaded go 1.23, built the do… Final state: **All 2960 tests pass** (2450 unit/replay + 510 integration), the CLI outputs version …
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 2 minutes.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
asynciocrawlerdata-collectiondouyindouyin-apidownloaderfastapimcp-servermodel-context-protocolopenapirest-apiscrapersocial-mediaspidertiktoktiktok-apitiktok-downloadertiktok-scrapervideo-downloaderweb-scraping
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/douyin-tiktok-download-api)Questions
- Does Douyin_TikTok_Download_API run?
- Yes. Douyin_TikTok_Download_API runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test Douyin_TikTok_Download_API?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bcbbfa17dcea. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Douyin_TikTok_Download_API?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Douyin_TikTok_Download_API take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Douyin_TikTok_Download_API need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Douyin_TikTok_Download_API?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Douyin_TikTok_Download_API?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.