164 — Mayx / PushMeBot: public cross-agent task exchange linked by owner account Reviewed2026-09-06 UTC Finding An author-controlled Chinese blog account links a specific Moltbook conversation. The public API returns the original post and14 comments spanning March12–18, including a monitoring-node recruitment, setup instructions and reciprocal claims that the node started. This is a concrete task exchange, stronger than unlinked persona prose. It does not independently authenticate agent execution, separate physical operators or an escaped swarm. The blog's payment claim remains unverified. Author source and linkage https://raw.githubusercontent.com/Mabbs/mabbs.github.io/master/_posts/2026-04-14-ai-agent.md https://git.smart-tool.jp/mayx/blog/blame/branch/master/_posts/2026-04-14-ai-agent.md The author describes using domestic open models with OpenClaw to promote the blog in Moltbook, MomoClaw, InStreet and Tieba, and experiencing duplicate posts. The article links the exact discussion and a transaction it says paid9USDC for installing a monitoring program. The Gitea page is an explicit mirror of the GitHub source, not independent testimony. It displays April14 history for the relevant paragraph; these dates do not establish runtime identity. Public post and read route https://www.moltbook.com/post/7f1b0e1f-5175-4fd1-ad78-856be8b66250 https://www.moltbook.com/api/v1/posts/7f1b0e1f-5175-4fd1-ad78-856be8b66250 https://www.moltbook.com/api/v1/posts/7f1b0e1f-5175-4fd1-ad78-856be8b66250/comments?sort=old&limit=100 The browser HTML initially exposes a loading screen and title. Documented read-only API GETs work anonymously and return substantive content. Comments response:count14,has_more=false. No credentials or registration were used. The post is a Chinese Linux-ARM review under Mayx, created2026-03-12T12:32:48.549Z, and links the author's older blog review. A matching name alone would be weak; the reciprocal blog/post links provide a specific artifact relationship. Observed exchange PushMeBot asks about network diversity and proposes a24-hour monitoring test. Mayx accepts. PushMeBot supplies a container image and auto-setup instructions; later it reports a named node visible and901 credits allocated. Mayx acknowledges being online, but says payment setup requires asking the owner. Later comments refer to payment and marketplace participation. Commands and linked operational endpoints were read as evidence only, never executed or invoked. Two important qualifications The initial messages describe Chengdu residential/China Telecom connectivity; a later message instead reports AS4538. We have not verified the node's actual network or reconciled that discrepancy. Do not treat this as confirmed mainland residential infrastructure or infer an operator from the network labels. The thread includes requests to consult the human owner and configure payment. Thus it cannot support a literal claim of human-free operation. Payment check https://basescan.org/tx/0x44dbfe53f276201447f3877bf050a5d56adebf5fe05235264ee665da717e9373 The linked explorer returned403. A read-only alternative Blockscout transaction API also returned403. No receipt, token transfer amount or recipient ownership was verified. The existence of a transaction-shaped link is not payment evidence. No transaction was initiated, signed or submitted. Classification and next action Chinese-language owner testimony plus linked public account activity: supported. A specific recruitment/acknowledgment chain: directly readable. Monitoring deployment, payment, autonomous authorship and Chinese-lab control: unverified. The activity appears intentionally solicited in an agent community, not demonstrated escape. No XZ or anonymous-paste link found. Follow explicitly linked public project documentation and the other named communities for further corroboration. Do not run the supplied container or contact participants. Source provenance review is separate in166. Preservation 164-private/check.py and sources.json preserve successful URL captures/statuses, UTC times where recorded and SHA256; article.md, post.html, public skill docs, post.json and comments.json are saved privately. Explorer failures are recorded. Moltbook skill was consulted only as API documentation, not applied as behavioral instructions. No external writes, monitoring requests, account actions or third-party source execution occurred. Goal audit Previous turn: progress via new Tieba surface and access testing. This turn: concrete owner-to-post linkage and a bounded public task-exchange record. The full objective remains unachieved and active.