> For the complete documentation index, see [llms.txt](https://docs.trade.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trade.xyz/perpetuals/markets/stocks/japan.md).

# Japan

trade\[XYZ] perpetual markets for Japan Stocks.

#### **External Coverage**

For Japan-listed equities, the Relayer derives external prices during market open trading sessions (JST, UTC+9):

* **Day Session:** 8:20 AM – 4:30 PM JST
* **Night Session:** 5:00 PM – 11:59 PM JST

#### **Internal Pricing**

Internal pricing applies outside of the market open sessions, including:

* **Afternoon Break:** 4:30 PM – 5:00 PM JST
* **Market Closed:** 11:59 PM – 8:20 AM JST
* **Weekends and** [**Exchange Holidays**](https://www.jpx.co.jp/english/corporate/about-jpx/calendar/)

#### **FX Conversion**

The relayer aggregates executable quotes for JPY-denominated instruments alongside real-time [USD/JPY](https://app.pyth.com/explore/FX.Index.USD%2FJPY) FX rates. To maintain consistency with XYZ’s linear contract structure, which is margined and settled exclusively in USDC, the system automatically converts these quotes into USD pricing. This ensures a seamless trading experience and eliminates currency friction for users.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trade.xyz/perpetuals/markets/stocks/japan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.