Channel
@webrobotltd
On this record: Growth · Engagement · Posts · Cite this entry
31subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001372767129 |
|---|---|
| Type | Channel |
| Username | @webrobotltd |
| Created | 1 December 2018 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/webrobotltd |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 18:14 | 31 | -1 |
| 11 Aug 2026, 02:16 | 32 | no change |
| 8 Aug 2026, 00:13 | 32 | first reading |
19 posts held, back to 1 December 2018 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.
⚡ From data to alpha: WebRobot meets NautilusTrader Two days of R&D turned our data platform into an end-to-end quantitative engine — NautilusTrader integrated as a trading node in our Bring-Your-Own-Cloud stack. WebRobot's alternative data (sentiment, on-chain signals, hype, mentions) becomes the signals that drive trading and portfolio-management strategies — while prices come from the exchanges. What we built and …
Signed WebRobot Social
🦊 R&D update — autonomous AI browsing, now on stealth Firefox Today we shipped a major piece of WebRobot's autonomous data-extraction engine: our AI browser agent now drives stealth Firefox (Camoufox) over WebDriver-BiDi — beyond the usual Chrome-only setups. What's new and live: ✅ Full autonomy — the agent navigates, reads the page, clicks and types to complete real multi-step tasks (validated end-to-end on live e-c…
Signed WebRobot Social
AI agent vs passive — a crypto-basket backtest. Setup: an agent dynamically rebalances BTC/ETH/SOL/IOTA/XRP + USDT, choosing the allocation itself (long/short), with Bitcoin's ~4-year halving cycle as the regime signal. No hard-coded rules, no lookahead. Results — agent | equal-weight rebalanced | buy & hold (return | max drawdown): Downtrend, 180d: −21.7% (−23%) | −34.5% (−45%) | −34.1% (−44%)Uptrend / accumulation:…
Signed WebRobot Social
WebRobot · R&D report — the last few weeks In the spirit of technical transparency, here's what we've been building on our agentic scraping & ETL runtime. This is a development report, not a product announcement. 🧠 Distributed multi-agent runtime — in production. An agentic runtime built on Ray + Claude Agent SDK: persistent, distributed teams of agents (each agent is its own Ray actor), with shared memory across tur…
Signed WebRobot Social
🤖 Why WebRobot's pricing almost looks like cloud hosting — and why that's the point. It's BYOC — Bring Your Own Cloud. The Ray cluster, stealth browsers, scraping and AI agents run in YOUR cloud, not ours. We run only the control plane — the brains — on our seed servers. The result: the number of subscriptions barely moves our operating costs. 100 customers or 10,000 — pure software margin, pure scalability. From €19…
Signed WebRobot Social
🚧 WebRobot — pre-beta engineering update We're deep in hardening WebRobot: an AI-agent–driven, distributed web-ETL platform. Pipelines are declarative manifests executed on Apache Spark, with a stealth browser tier (Camoufox) for JS-rendered sources — and the whole stack can run on your own cloud (BYOC). Landing in this pre-beta cycle: Conversational agent (Claude Agent SDK, orchestrated on Ray): turns a request into…
Signed WebRobot Social
🤖 WebRobot — work of the day (work in progress) Currently testing the engine's multi-source logic: a single YAML pipeline scrapes N sites in parallel and cross-matches the same items across sources (normalized key). It's the shared substrate behind our 4 use cases: 💷 Price comparison📰 Sentiment🎯 Sure-bets🏠 Real-estate arbitrage▶️ First results on price comparison (GPU cards, Scan ↔ Overclockers): working cross-retail…
Signed WebRobot Social
🚀 New on the blog — WebRobot: one agentic data platform, three ways to use it. Developers drive it via Claude Code skills + MCP; business users via an integrated conversational chat; power users via an AI-augmented drag-and-drop designer. One engine, three front doors — all on your own cloud (BYOC), orchestrated on the Anthropic Agent SDK. The interactive demo is incoming. 👉 Read it: https://www.webrobot.eu/webrobot-…
Signed WebRobot Social
🤖 What if you could drop a real AI agent into your website — running on your cloud, not someone else's API? Today "AI for your site" is usually a toy chatbot widget or a 6-month infrastructure project. We're validating a third option. The idea: a plugin (WordPress first, other CMS next) where an admin configures multiple AI agent profiles — and with one click provisions the entire backend on your own cloud (BYOC): a …
Signed WebRobot Social
🤖 WebRobot — ETL for AI Agents Welcome to the official channel. Here's what we're building, and why. The problem. The web is the world's largest dataset — but it's locked behind anti-bot walls, missing or gated APIs, and messy HTML. AI agents are only as good as the data they can reach, and today most of it is either out of reach or impossible to turn into clean, structured, analysis-ready datasets at scale. What Web…
Signed WebRobot Social
Channel name was changed to «WebRobot — ETL for AI Agents»
Channel name was changed to «WebRobot — ETL for AI Agent»
Showing the 12 most recent of 19 posts we hold for @webrobotltd. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 22 August 2026 — this entry's latest reading, not the date you are reading this.
“WebRobot — ETL for AI Agents” (@webrobotltd), 31 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/webrobotltd.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.