# Seoul ### Status [42dot](/platforms/42dot.md) available to the public [Kakao Mobility](/platforms/kakao-mobility.md) available to the public ### 42dot ![](/files/zCYhzCnv1hQ1C0sZh4uM) See full information about service areas and times - in summary it appears to be daylight Monday to Saturday, with a lunch break ### 42 dot shuttle "The buses can carry seven passengers and will initially circulate on a 2.1-mile loop around Cheonggye Stream, a busy tourist and commercial area in downtown Seoul. Rides are free during the launch period and the public can board at two stops along the route after booking a seat on a mobile app." **Source**: ### Kakao Mobility / RoboRide The pilot RoboRide will be the first car-hailing service with autonomous driving vehicles to operate in Gangnam, one of the most congested areas in metropolitan Seoul. The RoboRide pilot service will operate from 10 a.m. to 4 p.m., from Monday to Friday, to minimize any possible inconveniences on the road. Up to three passengers can be on a ride, whereas a safety driver will be in the vehicle to respond to any emergencies. The Group plans to operate an initial demonstration service for internally selected personnel, and then expand the pilot service targets to general customers in the future. RoboRide will collaborate with Jin Mobility, a Korean startup operating the artificial intelligence (AI)-powered car-hailing mobility platform ‘i.M.’. Jin Mobility will be in charge of operating the two IONIQ 5 RoboRide units on its i.M application **Source**: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://rollout.autoura.com/cities/asia/seoul.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.