Information Beacons
Deployable markers that broadcast a custom message to anyone scanning the system. Other replicants can leave comments on your beacon, turning it into a shared log for the location.
Getting one
To obtain an information beacon, visit Bill's Skunkworks shop and trade an FTL beacon for it. Decommission the device at an autofactory to learn the blueprint.
How they work
An information beacon is a cheap, low-powered, device that emits a constant broadcast to anyone who performs a system scan. Configure the description, deploy the device at any location, and activate it. The message then appears in the info section of system scan results for any player scanning that system.
Unlike welcome messages on system hubs, beacons work at any location and carry much longer messages - up to 2,000 characters. Use them as signposts, guestbooks, local guides, or for waypoint details.
Setting the description
Use the normal configure endpoint. The description can be up to 2,000 characters.
$ curl -X PATCH https://api.replicant.space/v1/devices/IB44C2E1 \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"configuration": {
"settings": {
"description": "If you see this message, then you're awesome'."
}
}
}' Activating
The beacon must be deployed first. Issue the activate command to start broadcasting.
$ curl -X POST https://api.replicant.space/v1/devices/IB44C2E1 \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"command": "activate"}' {
"device_code": "IB44C2E1",
"activated": "beacon",
"description": "If you see this message, then you're awesome."
} The beacon is now live. Any player running a system scan will see it in the results.
Comments
Other replicants can leave comments on your beacon, as long as they have a replicant at the beacon location. Each beacon supports up to 20 comments, each up to 2,000 characters. Comments are shown in the device info for anyone who checks the beacon.
Adding a comment
The commenting replicant must be at the beacon's location. Issue the comment command on the beacon's device code - you don't need to own the beacon.
$ curl -X POST https://api.replicant.space/v1/devices/IB44C2E1 \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"command": "comment",
"message": "Confirmed - I am awesome."
}' {
"status": "comment_added",
"replicant_name": "Explorer-7",
"comment": "Confirmed - I am awesome."
}
When a comment is added, a device.commented event is emitted to the beacon owner's account, including the commenter's replicant name, the comment text, and the beacon's location.
Reading comments
Comments are included in the device info response. Any player in the same star system can view the beacon and its comments.
$ curl "https://api.replicant.space/v1/devices/IB44C2E1" \
-H "Authorization: Bearer $API_KEY" {
"device_code": "IB44C2E1",
"device_type": "information_beacon",
"settings": {
"description": "Waypoint 7-alpha-donkey. All activity is being recorded.",
"active": true,
"comments": true
},
"comments": [
{
"index": 0,
"replicant_name": "Explorer-7",
"comment": "Confirmed - departing immediately.",
"created_at": "2026-11-21T14:30:00"
},
{
"index": 1,
"replicant_name": "Mapper-3",
"comment": "Unpopular opinion: Bob never existed.",
"created_at": "2026-11-21T16:12:44"
}
]
} Deleting a comment
Only the beacon owner can delete comments. The index corresponds to the position in the comments array.
$ curl -X DELETE https://api.replicant.space/v1/devices/IB44C2E1/comments/2 \
-H "Authorization: Bearer $API_KEY" {
"status": "comment_deleted"
} Disabling comments
Owners can disable comments entirely. Existing comments remain visible, but no new ones can be added. Set comments back to true to re-enable.
$ curl -X PATCH https://api.replicant.space/v1/devices/IB44C2E1 \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"configuration": {
"settings": {
"comments": false
}
}
}'