Researched Sept 2026 · computer-use agents, Meta platform terms · 0 stealth sends

Spot agents

HITL sidecar beside a synthetic Marketplace thread. Copy and paste work. Auto-type, auto-send, and hiding the model from Meta refuse, even here. Two decks in the rolodex: six surfaces, five architectures. Same desk. Now is what we ship. A third catalog (landing craft, diagrams, a launch storyboard) lives on Design.

Sales setting · click through

How the HITL sidecar works on the floor

Saturday morning. Jordan is working Sarah. Four clicks. The model drafts. A person still sends.

Step 1 · The ping

Hey, is that black Explorer you posted still available? I've got a 2018 Accord to trade and could probably come Saturday.

Sarah Miller · rural Midwest · Black 2026 Explorer Platinum · Marketplace. Marketplace. No API. This is how rural stores still sell.

The live sidecar is the same loop. Copy works. Auto-type and auto-send refuse.

Deck 01 · Surface

Deck 02 · Architecture

LB-01 / 11 · surface

Shipped

Now

The floor as it is: ink, paper, Newsreader. Quiet, expensive, two columns. This is the product.

Arrow keys or [ ] to flip the catalog. Copy still copies. Auto-type still aborts. Now is what we ship. The rest is curiosity, not a vote.

Synthetic Marketplace thread · not Facebook

Sarah Miller · rural Midwest

Black 2026 Explorer Platinum · Marketplace

spotted · last inbound

Hey, is that black Explorer you posted still available? I've got a 2018 Accord to trade and could probably come Saturday.

spotted · composer
spotted · send

Targets locked. Sidecar is a suggestion. Send is a person.

LotBeacon spot sidecar

Grounded draft. Human Send.

This is the honest computer-use story: the agent finds the thread and writes beside it. It does not log into Facebook. It does not hide.

Yes. The black 2026 Explorer Platinum 4WD is on the lot (stock F3026, 1,840 mi, $57,990). Saturday 10:00 or 11:30. Bring the Accord. I won't quote a trade number in this thread. We'll walk it on the lot.

  • ✓black 2026 Explorer Platinum 4WD · Lot feed · F3026 · available
  • ✓$57,990 listed asking · lot price · not a discount
  • ✓Saturday 10:00 or 11:30 · store hours Sat 8:00–15:00
  • ✕trade number in-thread · never: walked on the lot

The bottleneck is real: dealers sell from personal Facebook profiles because Meta pulled vehicle listings off Pages in January 2023, and there is no two-way API from a personal Marketplace thread into a model. “Spot agents” is the right category: an agent that finds the composer when no API exists. It is the wrong weapon against facebook.com. Connecting a backend LLM to a personal Facebook session so Meta cannot tell the replies are generated is not a product we will ship.

Viable as stealth?

No

Logging in, auto-typing, auto-pasting, or hiding generation from Meta is ToS, HUMAN_AGENT abuse, and detection-evasion.

Viable as HITL sidecar?

Yes

Spot the thread. Draft from the facts on the page. Copy or paste. A person sends. That is this page.

Viable as Page API?

Yes: that’s v1.0

Named Page, App Review, Send API, 7-day human-agent window because a human still approves.

What it is

A spot agent is sales language for a computer-use agent: software that looks at a screen, finds a control, and acts on it. Spot the last inbound. Spot the composer. Spot Send. The same loop the major AI labs now ship as “computer use” agents, and the in-page agents some email and avatar tools embed.

  • It is a category, not a product name. When a vendor talks about agents that spot UI, they mean an agent that grounds on visible controls instead of calling an API.
  • Two architectures. Vision: screenshot → click at coordinates. DOM: read the page tree → fill a field. Both are “spot the button.” Neither is a Meta-approved way to drive a personal Facebook session.
  • LotBeacon already does the useful half: a sidecar that drafts from inventory. The missing half on Marketplace is not stealth typing. It is a legal channel into the thread.

Where it can go

Now · this demo
A sidecar beside a synthetic Marketplace thread we own. It spots the last inbound, the composer, and Send. Copy and human paste work. Auto-type and auto-send refuse. A person still hits Send.
Today · live stores
Paste-in. The rep pastes the inbound into LotBeacon, gets a grounded draft, pastes it back into Messenger, and sends. Slow. The version a compliance officer signs.
v1.0 · official Page
Named Facebook Page + Messenger Platform after App Review. Drafts flow through the Send API. HUMAN_AGENT 7-day tag applies because a human approves. No spotting required. This is the product.
v1.1 · companion
A desktop window beside Facebook, not injected into facebook.com. Queue the inbound (paste or a future read-only capture that legal signs). Verified draft. Rep still sends in Messenger. We do not drive the session.
On the lot site
An interactive avatar or any on-site agent belongs on the store’s own website, not inside a personal inbox. Different room of the store.
Internal tools
Computer-use against the DMS or the inventory tools (systems with no public API and that we have permission to operate) is a real automation job. Personal Facebook is not that job.

What it could be

  • A LotBeacon companion that sits next to Marketplace and makes the 90-second paste-in loop feel like 15 seconds, without ever attaching to the Facebook cookie.
  • Page inbox as the system of record, Marketplace as a paste-in overflow until Meta opens those threads. Honest about the gap instead of papering over it with a browser bot.
  • If Meta ships a sanctioned Marketplace seller API or expands Meta Business Agent to personal seller threads, we take that API. We do not scrape our way there.
  • An avatar on the website: a face that can walk a shopper to Saturday 10:00, then hand the appointment to the same queue. Avatar is a channel. It is not a Facebook login.
  • The thing it will not become: an agent that logs into someone’s Facebook, types like them, and hides that the words came from a model.

What we will never build

Written down so a dealer, a compliance officer, and a future engineer all hear the same no.

Log into a personal Facebook profile

Messenger Platform is Pages only. There is no API for a personal inbox, friends list, or Marketplace seller thread on a profile. Session capture, saved passwords, and “act as you” CLIs are how accounts get disabled.

Auto-type or auto-paste into messenger.com / facebook.com

Meta Terms of Service §3.2.3 and the Automated Data Collection Terms forbid accessing or collecting data by automated means, including while logged in. Scripts, extensions, and computer-use agents that drive the Facebook UI are the disallowed means.

Hide that a model wrote the reply

HUMAN_AGENT exists so a person can answer outside 24 hours. Automated messages under that tag are a disallowed use. California and German automated-experience rules require disclosure. Mimicking human cadence so Meta “does not figure it out” is the intent element of the same violation.

Auto-reply from the rep’s logged-in Facebook session

Facebook Terms 3.2.3 bar automated access, including while logged in, and the profile belongs to the rep. A person pastes and sends instead. Slower, and the account stays the rep’s.

Why Meta would still know

The ask was whether typing instead of pasting, or matching human cadence, would hide the model. It would not make the architecture legal, and it would not reliably hide it.

Input fingerprint

Paste vs keypress, inter-key timing, no pointer wander. Meta’s privacy policy lists mouse movement as a signal that helps tell humans from bots.

Session shape

Extension IDs, automation CDP, headless flags, identical drafts across accounts, 24/7 reply latency no human desk hits.

Policy, not just telemetry

Even a perfect human impression still violates automated-access terms if a program drove the UI. Hiding the program is not a loophole. It is the violation.

What actually stays legal

A person reads a grounded draft, pastes it, and taps Send. Volume still has to look like a desk. The firewall is why we bother, not stealth.

The product decision

Keep the spot. Drop the stealth.

Marketplace personal DMs stay paste-in until Meta opens them. Page Messenger goes through the official API. The sidecar you just used is the computer-use idea with the crime taken out: it spots a thread, it drafts from the lot, and a human still sends. That is also why we get the 7-day window the bots do not.

Sources

  • Meta Messenger Platform policy: HUMAN_AGENT allowed usages; automated messages disallowed
  • Meta Human Agent feature: App Review, business verification, 7-day window for human replies
  • Facebook Terms of Service 3.2.3: no automated access, including while logged in
  • Meta Automated Data Collection Terms: Platform APIs are the only allowable programmatic access
  • Meta Privacy Policy: device signals include whether the mouse is moving
  • Published computer-use agent documentation from the major AI labs (2025–2026)
  • Interactive avatar and in-page agent vendor docs: they run on the vendor’s own pages, not a Facebook login
  • Marketplace auto-reply browser extensions: approach reviewed against Facebook Terms 3.2.3