The Loaditout index still appears to expose old TweetClaw metadata in public search results:
Full X/Twitter automation via Xquik - 120 endpoints, reads from $0.00015/call...
Current TweetClaw metadata has moved away from that wording:
- Repo: https://github.com/Xquik-dev/tweetclaw
- npm package: https://www.npmjs.com/package/@xquik/tweetclaw
- Current install:
openclaw plugins install @xquik/tweetclaw
- Current MPP wording: MPP covers 31 read-only X API endpoints.
- Account-backed workflows cover posting, replies, media upload/download, direct messages, monitor tweets, webhooks, giveaway draws, follower export, user lookup, tweet search, and reply search.
I also tried checking the live record through the public endpoints exposed by this MCP server:
https://www.loaditout.ai/api/agent/skill/Xquik-dev/tweetclawhttps://www.loaditout.ai/api/agent/search?query=tweetclaw&limit=5
Both returned DEPLOYMENT_NOT_FOUND from Vercel at the time of this report, so I could not use the registry API or the MCP server to inspect or flag the record directly.
Could you refresh the Xquik-dev/tweetclaw registry record and confirm the public Loaditout API path is still correct?
The Loaditout index still appears to expose old TweetClaw metadata in public search results:
Full X/Twitter automation via Xquik - 120 endpoints, reads from $0.00015/call...Current TweetClaw metadata has moved away from that wording:
openclaw plugins install @xquik/tweetclawI also tried checking the live record through the public endpoints exposed by this MCP server:
https://www.loaditout.ai/api/agent/skill/Xquik-dev/tweetclawhttps://www.loaditout.ai/api/agent/search?query=tweetclaw&limit=5Both returned
DEPLOYMENT_NOT_FOUNDfrom Vercel at the time of this report, so I could not use the registry API or the MCP server to inspect or flag the record directly.Could you refresh the
Xquik-dev/tweetclawregistry record and confirm the public Loaditout API path is still correct?