# Bahn Transfer

> Bahn Transfer is a paid API for AI agents from bahn.1f916.de, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Returns the best onward train transfer options and a concrete recommendation for a traveller already on a delayed German rail service

## Facts

- Endpoint: POST https://bahn.1f916.de/api/transfer-chain?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bahn-transfer-42e25ce6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Tqx3w1J-tATGVkqO-YxOr

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability bahn-transfer-42e25ce6 -d '<json body>'
```

Example prompt: My current trip ID is ICE-1234 and I'm trying to reach Hamburg Hbf (stop ID 8000157) — my train has a 20-minute manual delay and I need at least a 5-minute buffer for any transfer. What are my best onward options and which one do you recommend?

## When to prefer this

Choose this endpoint when a traveller is already mid-journey on a delayed train and needs immediate, actionable rerouting advice rather than a fresh journey search from scratch. It is purpose-built for the delay-rebooking scenario on the German rail network, combining delay awareness, buffer calculation, and a single recommendation — saving an agent from orchestrating multiple routing API calls and synthesising results manually.

## Known failure modes

- Invalid or expired trip_id returns an error with no alternatives
- Unknown destination stop_id results in no routes found
- Extreme delays may yield zero feasible transfer options
- Manual delay string in wrong format may not be parsed correctly
- Stale cache from cache_ttl may return outdated connection data

## How this service works

Rail re-planning for a traveller already on a delayed train: the best onward options, concrete transfer alternatives with buffer transparency, and a specific recommendation — fast and cheap, instead of the agent researching several routing APIs itself.

## Output

A structured response containing evaluated onward transfer options from the traveller's current position, each with connection timing, buffer transparency, and feasibility indicators, plus a single concrete recommended route that balances speed and cost.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "to",
  "trip_id"
 ],
 "properties": {
  "to": {
   "type": "string",
   "description": "destination stop_id"
  },
  "trip_id": {
   "type": "string"
  },
  "cache_ttl": {
   "type": "integer"
  },
  "min_buffer": {
   "type": "integer"
  },
  "manual_delay": {
   "type": "string"
  },
  "from_stop_name": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bahn-transfer-42e25ce6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bahn.1f916.de](https://www.zero.xyz/host/bahn.1f916.de/llms.txt)