> 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/fx.md).

# FX

trade\[XYZ] perpetual markets for foreign exchange.

### **External Coverage**

For FX, the relayer sources executable quotes from institutional liquidity providers for market open sessions. Trading continues during most US holidays.

| Instrument | Week Start (ET) | Week End (ET)  |
| ---------- | --------------- | -------------- |
| EUR / USD  | Sunday 5:00 PM  | Friday 5:00 PM |
| USD / JPY  | Sunday 5:00 PM  | Friday 5:00 PM |

### **Internal Coverage**

Internal pricing is used from Friday 5:00 PM to Sunday 5:00 PM ET, or at any time there is a gap of more than 30 seconds between external oracle datapoints. This ensures continuous pricing coverage across all sessions, including after-hours. You can read more about the internal pricing mechanism [here](/perpetuals/mechanics/oracle-price.md#internal-pricing).

### **Data Source**

See the [Specification Index](/perpetuals/specifications-and-schedules/specification-index.md) page for pricing referencing sources.


---

# 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/fx.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.