Scan Platform ToS for Bot & Automation Clauses

How it works

ToS Automation-Clause Scanner answers one question before you point a script at a platform: what do its own Terms say about bots, scraping, automated posting and multiple accounts? You paste the Terms; it finds the relevant clauses and quotes them word for word. It never gives a legal verdict.

Phase 1 — Intake. Which documents you pasted, the retrieved date, the document's last-updated date, region and whether the text is a translation. URL only and no way to fetch it? It asks you to paste the text and never judges from memory.

Phase 2 — Locate. Reads the whole text and searches automation, scraping, posting, account, access and blanket-wording terms, plus cross-references to documents you did not supply.

Phase 3 — Classify. Every clause gets one label: EXPLICIT_PROHIBITION, CATCH_ALL (blanket wording such as "any unauthorized means" or "abuse"), PERMITTED_OR_API_PATH, SILENT (full text, nothing relevant) or NOT_CONFIRMED (text missing or truncated).

Phase 4 — Not-confirmed table. What is still open and what would close it, with a regional and translation caveat. Every output starts with a "not legal advice" line.

Sample output

Real, unedited output from running this Skill on a sample problem (a hand-written fictional "ExampleChat" Terms of Service excerpt, not a real platform):

> NOT LEGAL ADVICE. This report only locates and quotes clauses in the text you provided. It does not say whether an activity is allowed, enforceable, or safe.

# ToS clause scan — ExampleChat (fictional sample)

Summary: EXPLICIT_PROHIBITION 4 clauses, CATCH_ALL 3 clauses, PERMITTED_OR_API_PATH 1 pointer (conditions NOT_CONFIRMED), SILENT 4 sub-items, NOT_CONFIRMED 1 item in findings plus 5 rows in the table — 1 document scanned (Terms of Service). Topics checked: bots/automation, scraping/crawling, automated posting/engagement, multiple accounts, API use (default: all five).

## Source details

| Field | Value |
|---|---|
| Documents provided | Terms of Service — provided in full (you state it was the whole page; text runs from the title to §15 Contact with no cut-off or "[...]" seen). Developer Terms — referenced in §5.2, **not provided**. |
| Retrieved date | 2026-10-15 (your statement) |
| Document last-updated date | "Last updated: September 1, 2026" (as shown in the pasted text) |
| Region / locale | English site, US region (your statement) |
| Original language or translation | Not stated whether this is the original-language text; the pasted text is in English |
| Completeness note | Numbered §1–§15, consecutive; no truncation seen. Page footer/header content beyond what you pasted was not seen. |

## Findings by topic

### 1. Bots / automation
- [EXPLICIT_PROHIBITION] §5.2 — "use any robot, spider, scraper, or other automated means to access the Service or collect content or user information, except through the interfaces described in the Developer Terms;" — why this category: contains "robot", "automated means".
- [EXPLICIT_PROHIBITION] §5.3 — "post, like, follow or message using scripts, macros or scheduling software that operate without a person initiating each action;" — why this category: contains "scripts, macros or scheduling software".
- [CATCH_ALL] §5.4 — "access the Service by any unauthorized means or through any interface not provided by ExampleChat;" — why this category: contains "any unauthorized means"; does not name automation.
- [CATCH_ALL] §5.5 — "interfere with or disrupt the Service or place an unreasonable load on our infrastructure;" — why this category: contains "interfere with or disrupt", "unreasonable load"; does not name automation.
- [CATCH_ALL] §6 — "ExampleChat may remove content or restrict accounts for abuse of the Service, as determined in our sole discretion." — why this category: contains "abuse", "sole discretion".
- Consequence clause exists (recorded, not interpreted): §11 — "We may suspend or terminate your account if you violate these Terms."

### 2. Scraping / crawling
- [EXPLICIT_PROHIBITION] §5.2 — "use any robot, spider, scraper, or other automated means to access the Service or collect content or user information, except through the interfaces described in the Developer Terms;" — why this category: contains "spider", "scraper", "collect content or user information".
- [CATCH_ALL] §5.4 — "access the Service by any unauthorized means or through any interface not provided by ExampleChat;" — why this category: contains "any unauthorized means".
- [CATCH_ALL] §5.5 — "interfere with or disrupt the Service or place an unreasonable load on our infrastructure;" — why this category: contains "unreasonable load".
- [SILENT] robots.txt / crawling-policy wording — searched "robots.txt", "crawl", "text and data mining", "bulk download" in the full provided document; no hit for those terms other than "spider" in §5.2 quoted above.
- [SILENT] numeric rate limits or request quotas — searched "rate limit", "throttle", "requests per"; no hit in the provided document.

### 3. Automated posting / engagement
- [EXPLICIT_PROHIBITION] §5.3 — "post, like, follow or message using scripts, macros or scheduling software that operate without a person initiating each action;" — why this category: contains "post, like, follow or message", "scheduling software".
- [CATCH_ALL] §6 — "ExampleChat may remove content or restrict accounts for abuse of the Service, as determined in our sole discretion." — why this category: contains "abuse", "sole discretion".
- [SILENT] fake-engagement / "artificially inflate" / "mass" / "spam" wording — searched in the full provided document; no hit.

### 4. Multiple accounts
- [EXPLICIT_PROHIBITION] §3.2 — "You may keep only one personal account. Creating or operating additional accounts to evade a suspension or a limit is not permitted." — why this category: contains "only one personal account", "additional accounts".
- [EXPLICIT_PROHIBITION] §3.3 — "You may not sell, rent or transfer your account to anyone else." — why this category: contains "sell, rent or transfer your account" (account transfer/sharing).
- [SILENT] registration / account creation by automated means — complete document provided; §5.2 and §5.3 cover automated access and actions, but no clause mentions registration by automated means specifically (searched "register", "create accounts", "sign-up"; §3.2 is the only "creating" hit).

### 5. API use
- [PERMITTED_OR_API_PATH] §5.2 — "except through the interfaces described in the Developer Terms;" — why this category: points to an interface/developer document ("interfaces", "Developer Terms").
- [NOT_CONFIRMED] conditions of that path (keys, approval, rate limits, allowed uses) — the Developer Terms were not provided, so nothing about them can be quoted.
- Related wording that bears on the path (quoted, not interpreted): §5.4 — "access the Service by any unauthorized means or through any interface not provided by ExampleChat;" ([CATCH_ALL]).

## Not confirmed

| What | Why it is open | What would close it |
|---|---|---|
| Developer Terms (API conditions, keys, rate limits, permitted bots) | Referenced in §5.2, not provided | Paste the Developer Terms in full, with their last-updated date |
| Whether the pasted English text is the governing-language version | Not stated whether it is original or translation | Say where it came from; supply the original-language text if it is a translation |
| Other published documents (community guidelines, API/robots policy, help-center rules) | Only the Terms of Service was provided; §5.4 refers to "any interface not provided by ExampleChat" without listing them | Paste any such documents, or confirm none exist |
| Future changes | §10 — "We may change these Terms at any time by posting an updated version." | Re-check the live page; the text here dates from your 2026-10-15 retrieval of a document updated September 1, 2026 |
| Meaning of "sole discretion" / "abuse" in §6 and "unreasonable load" in §5.5 | The text defines neither term | Ask the platform in writing, or consult a lawyer |

## Caveats

- Regional and translation caveat: terms vary by region and language; a translated text may differ from the governing version; this scan covers only the English US-region text you provided.
- Terms change: re-check against the live page, since the retrieved date (2026-10-15) will age.
- A clause being absent from this document does not mean it is absent from other documents the platform publishes (see the Developer Terms row above).
- This is not legal advice — see the disclaimer at the top. Deciding whether your project fits these terms is outside this Skill; consider asking the platform in writing or consulting a lawyer.

Use cases

• Checking a platform's Terms before building a scheduler, scraper or auto-poster
• Collecting the exact clauses to show a client or lawyer
• Telling "the Terms say nothing" apart from "I only have part of the Terms"
• Re-checking a platform after its Terms are updated

FAQ

Is this legal advice? No. It only locates and quotes clauses, and says so at the top of every output.

Will it tell me if I'm allowed to automate? No. It gives categories and quotes; the decision is yours or a lawyer's.

What if I only have a link? It asks you to paste the text. It will not guess from memory.

Does it cover every country? It covers only the text you give it. Terms differ by region and translation, and the Skill flags that.