marketplace.rtila.com is live. Seven bots. All free. Every one of them a
real desktop executable — not a workflow you have to host, not a template you
have to import, not a JSON file that needs our app on the other end.
We named the company after a spider and then spent six years building software
that crawls the web. A public directory of standalone bots was always where this
was heading. It’s up now, and we want you to kick the tyres before we tell you
anything else about it.
- 7 bots, free, no account, no install. Windows
.exe, macOS Apple Silicon
.sh, macOS Intel.sh, Linux.sh. Four launchers per bot. - Every artifact publishes its SHA-256 and exact byte count. Verify before
you run. The commands are on each bot page. - The full project JSON is published on every bot page. You can read exactly
what a bot does — every command, selector and dataset — before you download it. - One-click “Open in your RTILA X” if you already have the desktop app.
Nothing here requires a licence, a purchase, or an upgrade. Go download something.
What’s actually live
| Bot | What it does | Category |
|---|---|---|
| On-Page SEO Auditor | The big one. Nine datasets per URL: indexability & canonical resolution, on-page elements, readability (Flesch, Flesch-Kincaid, Gunning Fog, SMOG, ARI, Coleman-Liau), full link census, image & CLS audit, render-blocking resources, structured-data validation with rich-result eligibility, and an axe-core accessibility audit with WCAG tags. Plus a pre-filtered Critical Issues and Healthy Pages set. | SEO & Web Audits |
| Link Crawler | Internal crawl to depth 3, concurrency 7, returning title, status, content-type, charset, content-length, server, cache-control and X-Robots-Tag per URL. Deduplicated. | SEO & Web Audits |
| Redirect Checker | Full chain per URL: every hop’s status and location, rendered three ways (codes, details, visual chain), plus 301/302/303/307/308 flags and a chain-length verdict. | SEO & Web Audits |
| Outbound Link Checker | Total, internal, external, unique domains, fragment/mailto/tel/javascript/empty-href counts, top external domains — then splits pages into High-Link and Good-Partner sets around a threshold you set. | SEO & Web Audits |
| Mass Alive Checker | Bulk URL status check. Blocks every resource type so it’s HTTP-fast, 3 concurrent workers, then three datasets: full report, alive, dead. | SEO & Web Audits |
| SEO Rank Tracker | Google web results (udm=14) across a keyword list, returning your domain’s rank position per keyword. |
SEO & Web Audits |
| Local Business Profile Scraper | Google Maps: search a category, infinite-scroll the results, then visit every place page and pull category, name, amenities, phone, website, menu, price range, rating, review count, address and plus code. Eleven columns per business, source page attached. | Lead Generation |
That’s 21 declared categories and 7 published bots. Nineteen categories are
empty. We’d rather show you the delivery model than fake the inventory.
Two minutes, and you’ll know if this is real
Don’t take our word for it. Pick any bot, download your platform’s launcher, and
verify the digest before you run it:
Windows (PowerShell)
Get-FileHash BOT_link-crawler.exe -Algorithm SHA256
macOS / Linux
shasum -a 256 BOT_link-crawler.sh
Compare against the digest and byte count published on the bot’s page. Then run
it. On macOS and Linux you’ll need chmod +x first, and on macOS
xattr -cr BOT_<botId>.sh to clear the Gatekeeper quarantine attribute — both
are documented on the Platforms page.
Do not rename the file. The filename carries the bot’s configuration id, and
the launcher derives its id from its own name. Rename it and it requests the
wrong id and fails closed. That’s deliberate, not a bug.
Why we built it this way
This is the part we’re most proud of, so bear with us.
A launcher is a universal binary, not a per-bot build. There are exactly four
launcher binaries in the release channel. Every bot is served from the same
artifact, renamed per bot, and the marketplace streams the bytes from the
publisher’s public release channel rather than storing copies. One integrity
surface to audit instead of seven.
The configuration channel is the update mechanism. A launcher fetches its
published configuration by id at launch, cached at the edge for 60 seconds.
On the live update channel, a selector repair propagates to every launcher
already in the field within that window — no re-download, no re-delivery, no
client email. If a target site redesigns on a Tuesday, your client’s bot is
fixed by Wednesday morning and they never knew.
Remote switch-off is real. A bot published with server-controlled activation
stops at its next launch when you update the stored state. Propagation bound is
the same 60-second cache window. The launcher still receives its configuration
plus a disabled-state header, so it renders your message rather than failing
silently. You never touch the client’s machine.
Machine-readable all the way down. /api/bots.json (whole catalogue),
/api/bots/{slug}.json (full detail incl. project), /api/bots/{slug}/config.json
(configuration only), /llms.txt, /llms-full.txt, /rss.xml. An agent can
read the entire directory without parsing a line of HTML.
Digests are checkable, not decorative. Every listing publishes a
configDigest — SHA-256 over the canonical JSON form. A daily reconciliation job
re-reads the stored configuration and compares. If someone edits outside the
pipeline, the digests disagree and you can detect it without diffing JSON.
Nothing is hosted for you and nothing is queued. A launcher runs locally and
writes its output beside itself. The only network calls are the configuration
fetch at launch and whatever pages the workflow itself visits.
The honest part
We’re going to say this before anyone has to ask.
The directory currently distributes free, RTILA-authored bots. There is no
public submission form. You cannot list your bot here today. That’s our own
sentence, from our own /sell page, and it stays true.
What every bot in there is — and this is the sentence that matters — is
working proof of what the standalone-export capability produces. Same
product, same compile step, same launcher, same configuration channel. The
launchers you can download are demonstrations of a capability you may already
hold a licence for. They are not a substitute for it, and we’re not presenting
them as one.
What we’d love from you
No purchase required for any of this:
- Run a bot and break it. Post the failure. Selector drift, wrong encoding,
a platform where the launcher won’t start — we want all of it. - Tell us your niche. Nineteen categories are empty. If you tell us what
belongs inecommerceorrecruitingorfinance, that shapes what we build
first. - Post your bot idea. Describe the workflow in a reply. We’ll tell you
honestly whether we think it sells, and if it’s good we may build it and put it
in the directory ourselves — with the conversation linked. - Verify a checksum in public. Seriously. Screenshot the match. It’s the
fastest way to show a sceptical client that this delivery model is trustworthy.
We’ll be in this thread all week answering everything.
Links
Marketplace — https://marketplace.rtila.com
All bots — All bots | RTILA Marketplace
The delivery model, explained — Sell bots you build | RTILA Marketplace
Security, threat model and the config-fetch design — Security | RTILA Marketplace
Install steps per platform — Supported platforms | RTILA Marketplace
Machine-readable catalogue — https://marketplace.rtila.com/llms.txt
Editorial standard & who reviews — About the directory | RTILA Marketplace
Pricing (authoritative source for tiers) — Simple Pricing. No Surprises. Start Free. | RTILA X
Lifetime deal — RTILA X Lifetime Deal — Pay Once, Own It Forever | 60-Day Guarantee | RTILA X
Responsible use, as always: RTILA X automates actions you could perform
manually. Review each target platform’s Terms of Service and applicable
data-protection law before running a bot against it. Publicly published business
contact details are personal data for sole traders in most jurisdictions — every
lead-generation listing carries that notice on the page.