Add HTTP Access to Scripted Agent Detection
xxADSxx Resident
I am requesting a feature enhancement to provide HTTP or LSL-based access to the scripted agent detection system available in estate management tools. This would enable landowners and parcel managers to programmatically integrate and extend scripted agent management capabilities for more effective region security.
Use Case:
Currently, estate managers can block scripted agents via the estate tools. However, there is no direct way to access this detection via HTTP or LSL.
This feature would allow landowners or third-party systems to identify and respond to scripted agents dynamically.
For instance, landowners could integrate this detection with custom HTTP-based tracking systems to automatically manage and secure their parcels.
Proposed Solution:
Provide a new LSL function or HTTP endpoint that exposes the estate's "Scripted Agent" detection status for an avatar. Example:
llGetScriptedAgentStatus(key agent_id): Returns TRUE or FALSE based on whether the estate recognizes the agent as a scripted agent.
An HTTP-based system that allows secure querying of the detection system, requiring estate-level permissions.
Benefits:
Extends functionality to individual land parcels.
Enhances security and user experience by automating the detection and management of bots.
Reduces manual work for estate and parcel owners.
Impact: This feature would significantly improve the ability of estate and parcel managers to maintain control over their regions, without relying entirely on manual management or third-party tools that currently lack estate-level data.
Priority:
Medium to High (depending on Linden Lab's development priorities).
Log In
Peter Stindberg
I'm not sure I can follow...
The "scripted agent" status is global, and gets set in the web backend. You can't be scripted on one estate, and not be scripted on another.
The scripted agent status can already now be read via script: https://wiki.secondlife.com/wiki/AGENT_AUTOMATED
In conclusion, nothing prevents you to read the status for any visitor of your region(s) and expose it to http and deal with it as you wish. My products do this extensively sisincecne the introduction of that flag. It works (almost) flawlessly (there were some users that had the flag set unbeknownst to them and erroneously).
Nelson Jenkins
Peter Stindberg Seconded, AGENT_AUTOMATED does precisely this via LSL and any HTTP API endpoint to do the same thing would be relatively pointless.
Timothy McGregor
Peter Stindberg I think the problem here might be that the person was, like me, unaware that the flag was available. Historically it hadn't been, and had evidently been quietly added early last year. Thank you for pointing this out.
Peter Stindberg
Timothy McGregor The flag was introduced in April 2023 and rolled out gridwide in May. It was widely discussed in the forums, on JIRA, and during the user group meetings. Indeed the server release notes don't show it (I just checked), which is unusual. But the flag was introduced on the wiki shortly after the Lab announced the revamped scripted agent policy.