> For the complete documentation index, see [llms.txt](https://docs-integration.squake.earth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-integration.squake.earth/notable-changes/calculation-changes/train-rem-v2-4.md).

# Train: REM methodology v2.4 — docs & API

**What:** The **REM** (Rail Emission Model) train methodology is documented as the primary rail integration path. **`methodology: "REM"`** replaces **`"SQUAKE"`** in examples (legacy alias still accepted). Integration docs and OpenAPI train schemas now include **`departure_date`** (ISO `YYYY-MM-DD`), **`origin_country`** / **`destination_country`** (ISO 3166-1 alpha-2), **`energy_scope`** (`wtw` / `ttw`), optional **`route_coords`** for border-aware distance, and the **tiered factor resolver** (Tier 1 → Tier 3 → Tier 4 → Tier 5; Tier 2 is not used in production).

**Do now:** Use [Train: REM](/api-calculations-request-response/travel/train/train-rem.md) for field definitions and request shapes; prefer **`REM`** in new integrations.

**Reference:** REM factor bundle and loader notes are maintained alongside the calculation service; methodology narrative follows REM v2.4.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-integration.squake.earth/notable-changes/calculation-changes/train-rem-v2-4.md?ask=<question>
```

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.