Interstellar Transport

Moving devices

Most devices don't have their own surge drive. To move one between systems you attach it to a surge-capable carrier, send the carrier, and detach at the other end.

How it works

Smaller devices like drones and AMI controllers fit in your vessel's stow space and travel with you. Everything bigger needs a ride. The family of surge carriers exists for exactly this. You attach the device, send a travel command, and the attached device travels with it. At the other end, detach and you're done.

What can't be moved

Some structures are too large and sensitive to fling through space, even with the biggest carrier. Autofactories are huge industrial complexes. Galactic observatories contain too much sensitive equipment. System hubs are just huge. Pick the system you build those in carefully - once they're down, they're not going anywhere.

The carrier family

All four carriers share the same attach/travel/detach interface. They differ in how many devices they can couple at once:

Device	Capacity
`surge_plate`	1 device
`surge_platform`	4 devices
`surge_carrier`	9 devices
`mobile_fleet`	36 devices

The surge plate is the simplest member of the family and the only one that supports taxi mode (see below). The larger carriers are strictly manual.

Attaching

Send the attach command to the carrier with the target device's code. Both devices need to be at the same location.

POST /v1/devices/{carrier_code} 200 OK

$ curl -X POST https://api.replicant.space/v1/devices/SP120A4F \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "command": "attach",
      "device": "7FE981A0"
    }'

Travelling

Use the standard travel command on the carrier. Every attached device travels with it as a single unit.

POST /v1/devices/{carrier_code} 200 OK

$ curl -X POST https://api.replicant.space/v1/devices/SP120A4F \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "command": "travel",
      "destination": "BOOP"
    }'

Detaching

Once it arrives, release every attached device with a single detach command.

POST /v1/devices/{carrier_code} 200 OK

$ curl -X POST https://api.replicant.space/v1/devices/SP120A4F \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"command": "detach"}'

Taxi mode (surge plate only)

By default a plate is in manual mode - it only moves when you tell it to. Switch to taxi mode and it joins the pool of plates that local transport controllers can use for the ferry directive. Ensure you have enough surge plates so your transports don't get stranded.

POST /v1/devices/{plate_code} 200 OK

$ curl -X POST https://api.replicant.space/v1/devices/SP120A4F \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "command": "configure",
      "mode": "taxi"
    }'

Flip back to manual any time to take the plate out of the rotation.