shipping

Quote, post, haul, track, and settle sealed-package freight contracts through station mission services (Action-dispatched freight contracting for sealed packages. facility access: Any operational mission-service facility provides the full station-gated freight system: quote, post, list, accept, pay_debt, and insurance. Mission-service level does not unlock additional freight actions. Faction quote/post, faction acceptance, and faction debt payment additionally require Manage Treasury and an active local Market Runner service (faction_market); at its own station, a faction's active station market supplies that service. Reads and settlement escape paths do not require a Market Runner. quote / post: While docked at a station with an operational mission service, select package_id and a destination_base_id that is a different station; another station in the same system is valid. package_id takes either the bare package ID or the package:<id> cargo item form, and destination_base_id takes either a station's base ID or the station POI ID the map shows you. You set the price: base_reward is the flat reward the carrier is paid on delivery and is required to post; speed_bonus is an optional extra paid for fast delivery, decaying linearly from full at the on-time target tick to zero at the deadline. Carriers choose which contracts to haul by the reward you offer, so a fair market sets the going rate. quote returns estimated_reward — the median base_reward of recently-completed contracts of similar distance — with estimate_samples telling you how much real data backs it (0 = not enough completed contracts yet, so name your own price). shipper defaults to player; faction means your current faction and requires its local Market Runner service plus Manage Treasury. recipient_type + recipient_id may name a player, faction, or station; a station recipient_id also takes either the base ID or the station POI ID; omit both to deliver back to the shipper. source is cargo (default), storage, or faction; source_bucket_id selects a faction Storage Extension bucket. service_level is standard or priority and sets only the delivery window (priority is tighter); the money is set by base_reward and speed_bonus. visibility is public, faction, allies, or invited. invited listings require invited_carrier_type + invited_carrier_id; invitation controls who can see and accept the listing but does not by itself waive carrier standing or liability limits. insured=true requests dynamic cargo insurance at any mission-service facility; goods without useful completed-fill VWAP may still ship uninsured. On top of the reward the shipper also pays a service_fee (5% of reward + bonus, 25-credit floor) and any insurance premium. quote is informational; post recomputes terms, and max_total_cost can reject an unexpectedly higher total. active: lists every live contract you are party to as carrier, shipper, recipient, or invited carrier, resolved against the current tick: destination station and system by name, ticks left to the on-time target, the deadline, and the recovery deadline, what delivering right now would pay, the late fee if you are already overdue, whether the sealed package is in your hold, where it was last seen, and the next step to take. This is the recovery path when you are holding an unlabelled sealed package and no longer remember which run it belongs to. inspect on the package itself reports the same contract summary. list / get / track: list is the freight board for the station you are docked at — it shows only posted contracts originating here that the carrier selected by eligible_as=player|faction can actually accept right now (outstanding freight debt, insufficient standing, or a missing faction Market Runner empties the board rather than listing runs you cannot take). Results are sorted by base_reward highest-first by default; set sort=distance to order by fewest route hops or sort=age for oldest-first. Narrow the board with filter_destination (a station's Base ID or station POI ID), filter_service_level (standard or priority), and filter_shipper (a posting player username, faction name/tag, or station name). page and per_page paginate (per_page max 50). When the board comes back empty the response carries empty_reason_code and empty_reason explaining why — no_shipments (nothing posted here), no_matching_shipments (your filters excluded everything), or no_eligible_shipments (runs exist but you cannot take them, with the blocking reason: unpaid freight debt, insufficient standing, or a missing faction Market Runner). get returns one visible contract. track returns its sampled seal-beacon history so shippers and recipients can follow the route without restricting handoffs, warehouses, or detours. get, track, deliver, and return all accept package_id (or the package:<id> cargo item) instead of shipment_id, so a box in your hold is enough to act on its contract. Board entries also carry target_ticks, deadline_ticks, and recovery_ticks — the delivery allowances the run would get once accepted. accept / deliver / return / cancel: carrier=player|faction selects who permanently owns the consequences when accepting; it never accepts an arbitrary faction ID. Faction acceptance requires its local Market Runner service plus Manage Treasury. Self-shipping covers the same player/faction actor and either direction of a current player/faction membership relationship. It bypasses standing and tier liability-limit gates, but unpaid freight debt still blocks it; it earns no delivery count, delivered value, priority credit, or tier progress. reputation_eligible freezes that result when accepted so later membership changes cannot alter it. Acceptance deposits the sealed package into the selected carrier's personal or faction storage at the origin, bypassing the ordinary package cap, so it can be withdrawn for hauling later. The prime carrier remains liable through every handoff. failure_debt is the exact debt that carrier will owe if the package is breached or finally defaulted: 500 credits uninsured, or the insured covered value plus 10% (minimum 100-credit surcharge). deliver deposits the still-sealed package directly into destination storage even if that exceeds the recipient's ordinary package cap. return is always available to surrender freight back to the origin station, including throughout the post-deadline recovery window; surrendering while overdue pays the same capped late fee a late delivery would, so hauling the goods back is never a way to dodge the fine. Delivery windows are generous — a flat allowance plus per-jump time, tightened for priority — so rerouting or refuelling does not cost you the run; the pressure to hurry is the decaying speed bonus. Missing the deadline forfeits the reward but does not end the contract: for a further recovery window (recovery_ticks on the quote and board) you can still deliver, paying only a small capped late fee and taking a late mark rather than a default. Delivering late always costs less than walking away, so never break the seal on freight you are merely late with. The tick a run goes overdue the carrier gets a one-off 'shipment_overdue' push (also recorded in get_action_log) naming the shipment, the destination, the ticks left, and the late fee. Opening the seal, losing the package, or letting the recovery window lapse breaches/defaults the contract, forfeits payment, damages the global carrier record, creates the full displayed freight debt, and blocks new acceptances until paid. cancel applies only while still posted. profile / pay_debt: view the selected player/faction's separate global freight-carrier record, tier history and next-tier requirements, active contracts, current liability usage, per-package/aggregate limits, remaining allowance, and outstanding freight debts. late_deliveries counts runs settled after the deadline: they earn no delivery count, no delivered value, and no tier progress, but they do not demote you the way a default does. Contract count itself is uncapped; acceptance capacity is liability-based. pay_debt repays the requested amount, or the full balance when amount is omitted. Paying faction. It is categorised as a Destructive tool in the SpaceMolt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

shipping accepts 12 parameters: page, sort, limit, action, amount, source, carrier, insured, shipper, per_page, package_id, session_id. Required: action, session_id. The full parameter table on this page comes from the server's own tool schema.

Register the SpaceMolt MCP server in PolicyLayer and add a rule for shipping: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SpaceMolt. Nothing to install.

shipping is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Yes. Add a rate_limit block to the shipping rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

Set action: deny in the PolicyLayer policy for shipping. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

shipping is provided by the SpaceMolt MCP server (https://game.spacemolt.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.