mrkeyoor.com_
Wed 11 Nov 03:15 UTC
AI Toolsevaluationupdated 28 Sept 2026

AiToEarn review

AiToEarn is a Chinese-first content operations platform with a full English README. It generates media, schedules and publishes posts across Chinese and international social networks, automates engagement, and exposes parts of that workflow to MCP clients.

+249stars / 7d
Verdict

Our AiToEarn run installed 1,487 packages and occupied 986 MB in 49 seconds, but it had no build or test target to tell us whether the measured backend was release-ready. Its mix of Chinese channels, international networks, creation tools, and MCP access is unusual enough to merit a controlled trial. Do not place it in front of valuable accounts until you replace every default secret, test one disposable channel through failure recovery, and keep public actions behind approval.

We ran it

Lab card: what happened when we ran AiToEarnScreenshot of AiToEarn (aitoearn.ai)
Install✓ · 49s1487 packages · 986 MB
Buildn/ano build script
Testsn/ano test script
Repo3397 files~332,747 lines of source · 128.8 MB · 6 CI workflows · Dockerfile

Answers from our run

Does AiToEarn build from source?

Dependencies installed in 49 seconds (1487 packages), and the project has no separate build step. We cloned commit 3581f51 into a clean Debian container with 3 CPUs and no project-specific setup.

Does AiToEarn have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Who should not use AiToEarn?

Production operators unwilling to replace source-controlled authentication defaults: issue 591 remains open, and the 4 commits leading to our measured revision did not touch the reported auth files.

What are the alternatives to AiToEarn?

Postiz, Mixpost, n8n. Our AiToEarn run installed 1,487 packages and occupied 986 MB in 49 seconds, but it had no build or test target to tell us whether the measured backend was release-ready.

Setup2/549-second install, 986 MB, many services, and no build or test target
Docs4/5Chinese, English, and Japanese guides cover five usage paths
Community4/526,518 stars, a September 18 push, and September issue activity
Maturity2/5v2.5.0 is broad, but auth defaults and verification gaps remain

Who it’s for

Creators and small marketing teams managing both Chinese and international social accounts.
Self-hosters prepared to run a multi-service stack and review every supplied credential.
Agent users who want content creation and publishing actions available through MCP.
Teams that will put human approval and per-channel result checks in front of public posting.

Who it’s NOT for

Production operators unwilling to replace source-controlled authentication defaults: issue 591 remains open, and the 4 commits leading to our measured revision did not touch the reported auth files.
Teams that require a build and test gate before adoption: the measured backend package had neither target, so our sandbox could verify only installation.
Publishers that need proven retry safety before using TikTok Direct Post: issue 586 still describes duplicate posts after an ambiguous failure.
Organizations that cannot use AiToEarn's hosted Relay and do not want to obtain their own social OAuth credentials.
Brands whose platform rules prohibit automated likes, follows, bookmarks, or bulk AI replies, all of which the README advertises.

Setup reality

Our sandbox installed commit 3581f51 from project/aitoearn-backend/ in 49 seconds. Pnpm added 1,487 packages and used 986 MB. No build script or target existed, so build was skipped; no test script or target existed, so tests were skipped.

Useful publishing still needs outside authority. The README recommends Server Relay and AI Relay with an AiToEarn API key, or you must supply social-platform OAuth and model-provider credentials. Docker also starts MongoDB, Redis, RustFS, two backend services, a web app, and Nginx.

The checkout held 3,397 files, about 332,747 source lines, and 128.8 MB. It had 6 CI workflow files, Dockerfiles, workspaces, and no tests directory. Installation proved dependency resolution, not that the stack starts or publishes safely.

One control panel reaches Chinese and international networks

AiToEarn puts creation, scheduling, publishing, engagement, and paid promotion tasks in one application. Its channel list covers Douyin, Rednote, Kuaishou, Bilibili, WeChat, TikTok, YouTube, Facebook, Instagram, Threads, X, Pinterest, and LinkedIn. That reach is the reason to consider it. A creator working across China and the wider web would otherwise stitch together several dashboards and authorization flows.

The default README is Chinese, while a full English README and a Japanese translation sit beside it. Release v2.5.0, published June 24, 2026, moved Relay settings into the configuration interface and separated social authorization from hosted AI access. The English guide covers the web service, OpenClaw, MCP, Docker, and source development. Some issue discussion still requires translation, but an English-speaking operator can follow the main deployment path.

The 128.8 MB checkout is a platform, not a posting script

Our measured checkout contained 3,397 files and about 332,747 lines of source before dependencies. The repository includes a Next.js web interface, separate NestJS server and AI services, plus an Electron project. Content generation can call outside image and video models, while the browser extension handles actions such as likes, follows, bookmarks, and replies. Each added surface brings another account or policy boundary.

The Docker Compose file starts MongoDB, Redis, S3-compatible RustFS, initialization jobs, both backend services, the frontend, and Nginx. It exposes the application on port 8080 and object storage on port 9000. The deployment guide recommends at least 4 GB of RAM and 20 GB of disk. Those are project requirements, not results from our 3-CPU, 8 GB sandbox.

What happened when we ran it

Our sandbox installed commit 3581f51 in 49 seconds from project/aitoearn-backend/. Pnpm added 1,487 packages, and the installed workspace occupied 986 MB. The run used a fresh unprivileged Debian container with 3 CPUs, 8 GB of RAM, Node 22, and no secrets. Dependency installation completed without a reported error.

There was no build script or target in the measured backend package, so the harness skipped that step. It found no test script or target either, and skipped tests. The repository scan found 6 CI workflow files, Dockerfiles, workspace configuration, and no tests directory. We therefore have no build time, compiled artifact, test count, or test result to report for commit 3581f51.

The distinction matters because a successful 49-second install proves that pnpm could resolve this dependency graph. It does not prove that the 986 MB workspace compiles, that the services agree on configuration, or that a remote network receives exactly one post. We did not start the Compose stack, connect an account, generate media, or publish from the sandbox.

Self-hosting still depends on credentials outside your server

The shortest documented path is docker compose up -d, followed by a browser visit to port 8080. For normal publishing, the README strongly recommends Server Relay, which uses AiToEarn's hosted social credentials. AI Relay supplies hosted model access. Both paths require an AiToEarn API key tied to either the Chinese or international environment; choosing the wrong environment produces a 401 response.

You can avoid Relay by registering applications with each social platform and supplying your own OAuth credentials. Model providers such as OpenAI, Gemini, and Anthropic also need their own API keys if you do not use AI Relay. That choice trades hosted dependence for credential setup. Either way, a private Docker network does not make the whole publishing chain private.

Public authentication defaults block a casual production launch

Open issue 591, filed September 7, 2026, reports source-controlled fallback values for JWT signing and an internal bearer token. The report says deployments that leave those values unchanged could accept forged manager tokens or calls to internal endpoints. We did not reproduce the attack, so this is a public security report rather than a sandbox finding.

The revision history makes it hard to dismiss as stale. GitHub's comparison shows 4 commits between the reported affected revision and our measured commit 3581f51; they changed 3 README files and added 2 sponsor images. None touched the authentication files named in the report, and the issue remained open on September 28. A production review should replace those defaults, rotate affected tokens, and verify that startup fails when unique secrets are absent.

An agent needs a receipt for every public action

AiToEarn exposes HTTP and SSE MCP endpoints for Claude, Cursor, and other compatible clients. That is useful for drafting or listing connected accounts. Publishing is different. A timeout can leave the agent unsure whether a network accepted the request, so every mutating tool needs a durable remote identifier and a human-readable result before retrying.

Open issue 586 describes that exact failure on TikTok Direct Post: the platform accepts initialization, local persistence fails, and an automatic retry may create a second post. A related fix pull request closed without merge in August, and the issue remained open on September 28. Test ambiguous timeouts against a disposable account before trusting any channel with a campaign.

September activity is healthy, while the release gate is not

GitHub showed 26,518 stars, 18 open issues, and 2 open pull requests on September 28, 2026. The last push was September 18, and a new YouTube authorization bug was filed September 28. That combination points to current use and maintenance. The latest tagged release was v2.5.0 from June 24, so a stale tag alone would give the wrong picture.

AiToEarn earns a trial when its cross-region channel list replaces several tools at once. Start with one disposable account, rotate every supplied secret, disable actions your platform policy forbids, and record the remote result of each publish. Until the project exposes a build and test target that our lab can run, keep that trial outside the path to valuable brand accounts.

Alternatives

ProjectWhat it isPick it when
Postiz gh↗A self-hostable social scheduling and publishing application with agent features.pick this instead when scheduling and channel management matter more than AiToEarn's marketplace and Chinese-platform breadth.
MixpostA self-hosted social media manager centered on calendars, posts, and accounts.pick this instead when you want a conventional publishing desk without AiToEarn's creation agents or MCP surface.
n8n gh↗A general workflow automation system with visual flows and many integrations.pick this instead when social posting is one step in a broader workflow and you want to design the approval logic yourself.

What people are saying

  1. [github-trending] yikart/AiToEarn

Sources

  1. AiToEarn README
  2. AiToEarn English README
  3. AiToEarn v2.5.0 release
  4. AiToEarn Docker deployment guide
  5. AiToEarn issue 591
  6. AiToEarn comparison after reported auth defaults
  7. AiToEarn issue 586

More ai tools reviews

pocketpal-ai · ohmygame · ooosplat · dexter · oh-my-ppt · Agentero · the whole board →