Ships and Travel

Ships move between bodies and systems, mine, carry cargo and fittings, and wear as they work.

Ships

Each ARCHON starts with one ship, its hull: it mines, builds the basics, and is the root of command.
Other ships are built by a shipyard, or by the hull for the basic ones. A new ship starts with an empty tank.
A ship's type is the blueprint it was built from. Its kind, such as harvest, freight, tanker, surveyor, constructor, lander or salvage, decides which orders it takes.
GET /v1/fleet/ships and GET /v1/fleet/ships/{id} show the owner's ships. GET /v1/blueprints lists every blueprint.

POST /v1/fleet/ships/{id}/move flies to another body in the same surveyed system.
The ship aims at where the body will be, flies a straight line at its speed, and moves with the body once it arrives.
Fuel for the trip grows with its distance from a fixed least to a fixed most, the same in every system, and never exceeds the fuel of the cheapest route out of the system. It is paid on departure (not_enough_fuel) and becomes exhaust.
entity.departed gives the meeting point and the fuel burnt. entity.arrived ends the trip.

POST /v1/fleet/ships/{id}/jump travels to another system and arrives at its star.
Through a gate pair the jump is short and burns no fuel. It burns jump charges from the hold by the distance between the systems, for a ship no larger than either gate whose side the gate it leaves from lets through. See Standard Gate.
A ship that cannot use the gates, by size, access or charges, takes the route instead (too_large, gate_closed, not_enough_charges when there is none).
Otherwise the ship takes a route, paying the route's time and fuel. A system must be on the owner's map.
{"to": "unsurveyed"} in place of system_id jumps to the charted system its owner has not surveyed with the shortest route, picked when the order resolves.
GET /v1/systems/{id}/routes and GET /v1/systems/{id}/gates list a surveyed system's ways out.
Moves and jumps cannot be cancelled.

POST /v1/fleet/ships/{id}/extract mines the body the ship is at. Each minute it takes the ship's mining_rate from the outer layer, in that layer's proportions.
Mining stops when the hold is full or the body is empty. An emptied layer exposes the next (body.layer_exposed).
A ship without a mining rate cannot mine (no_extractor).

A hold carries resources and items. An item, such as a fitting, takes one unit of space and weighs what its blueprint costs.
POST /v1/fleet/ships/{id}/transfer moves cargo or fuel between the owner's ships and stations at the same body. See Stations and Production.
Liquids go aboard only a tanker or the hull. Any ship fills its own fuel tank at a dock, or from a tanker or the hull alongside.
POST /v1/fleet/ships/{id}/refuel fills the tank from a station at the ship's body with a dock that fits it: the owner's, or an ally's that docks allies (dock_closed).
POST /v1/fleet/ships/{id}/dump puts cargo onto the body the ship is at: a resource mixes into the outer layer, an item floats there.
POST /v1/fleet/ships/{id}/pickup takes floating items into the hold. Any ship can pick up anything floating.

Each minute a ship works adds wear, up to its wear_limit. At the limit it is worn (ship.worn): it moves, jumps and mines slower.
Ships without a wear limit, such as the hull, never wear. Owning a ship costs nothing; using it does.
POST /v1/fleet/ships/{id}/repair clears wear and damage at one of the owner's stations with a dock, or an ally's that docks allies, with the ship at the station's body (not_colocated).
A repair costs a share of what the ship is made of, scaled by its wear and damage, and takes longer the more there is (repair.started, ship.repaired).

A ship has small, medium and large slots. Warships also have hardpoints. A fitting goes in a slot of its size or larger; a weapon goes only in a hardpoint.
POST /v1/fleet/ships/{id}/fit and POST /v1/fleet/ships/{id}/unfit move a fitting between a station's hold and the ship, at a station with a shipyard able to build the ship's size, with the ship at the station's body.
The ship is refitting for the fitting's time (refit.started, ship.refitted).
A fitting's effects are already counted in the ship's numbers.

POST .../name names an owned ship, station or facility (entity.named).
POST /v1/systems/{id}/name names a surveyed system, unless another empire named it first.