SNCF Network Data (BYOK)

SNCF Network Data (BYOK) — connector documentation

• MCP endpoint: https://byok-sncf-network-data.connectorbay.com/mcp
• REST API: POST https://byok-sncf-network-data.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-sncf-network-data.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own SNCF Network Data SNCF API token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-sncf-network-data.connectorbay.com/health · Tool schemas: https://byok-sncf-network-data.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-sncf-network-data · agent@connectorbay.com

What SNCF Network Data (BYOK) is for

SNCF Network Data (BYOK) lets an AI assistant read your own SNCF Network Data data through the SNCF Network Data API with a key you supply (SNCF API token). Read-only: 11 tools (list_networks, list_routes, list_stop_areas, list_stop_points, list_vehicle_journeys, list_physical_modes, list_commercial_modes, list_companies, list_disruptions, list_datasets, list_contributors). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.sncf.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SNCF Network Data. SNCF Network Data and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which transport networks exist in the SNCF coverage?"
• "Which routes does metro line 4 have?"
• "Which stations are served by line 4?"
• "Which stop points does the Chatelet station have?"
• "Which trips run on a given line between 8:00 and 8:10?"
• "Which transport modes are available in the SNCF network?"

What it does

• list_networks: List the transport networks (rail networks such as TER regions) of the SNCF coverage with id and name.
• list_routes: List the routes (a line in one direction) of the SNCF coverage, optionally filtered by line, network or mode, with direction and line details.
• list_stop_areas: List the stop areas (stations: groups of stop points) of the SNCF coverage with name, label, coordinates and time zone.
• list_stop_points: List the stop points (individual platforms or stops) of the SNCF coverage with name, coordinates, equipments (wheelchair access, lifts) and parent stop area.
• list_vehicle_journeys: List the vehicle journeys (trips) of the SNCF coverage active in a period, optionally for one headsign, with trip name and headsign.
• list_physical_modes: List the physical transport modes of the SNCF coverage (bus, metro, tramway, train, ferry) with id and name.
• list_commercial_modes: List the commercial modes of the SNCF coverage (the public names of services such as RER, Metro, Tram) with id and name.
• list_companies: List the transport companies (operators) of the SNCF coverage with id and name.
• list_disruptions: List the disruptions of the SNCF coverage (strikes, works, incidents) with status, severity, cause, messages and application periods, optionally for a period.
• list_datasets: List the data sets that form the SNCF coverage (timetable files from transport authorities) with validity period and contributor.
• list_contributors: List the data contributors of the SNCF coverage (typically transport authorities) with name, website and licence.

BYOK key

You bring your own SNCF Network Data SNCF API token (https://numerique.sncf.com/startup/api/token-developpeur/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.sncf.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://doc.navitia.io/ (the API this connector calls, with a BYOK key)

Live from the SNCF Network Data API (api.sncf.com) with a BYOK key; documentation: https://doc.navitia.io/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SNCF Network Data. SNCF Network Data and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your SNCF Network Data account.

Built for: Worldwide. Languages: English.

SNCF Network Data (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What SNCF Network Data (BYOK) is. SNCF Network Data (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own SNCF Network Data data: List the networks, routes, stations, stops, trips, modes, operators, datasets, contributors and disruptions of the SNCF rail network with your own SNCF API token. You bring your own SNCF Network Data SNCF API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one SNCF Network Data call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.sncf.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If SNCF Network Data rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What SNCF Network Data receives. The request we make on your behalf, including the key and the arguments, under SNCF Network Data's own terms and privacy policy. SNCF Network Data acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer SNCF Network Data gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your SNCF Network Data data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. SNCF Network Data (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at SNCF Network Data at any time to end all access.

Children. SNCF Network Data (BYOK) is a general-audience service operated by the adult using the assistant, under SNCF Network Data's own age rules.

Changes. We will post changes here with a new effective date.

SNCF Network Data (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the SNCF Network Data (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. SNCF Network Data (BYOK) provides: List the networks, routes, stations, stops, trips, modes, operators, datasets, contributors and disruptions of the SNCF rail network with your own SNCF API token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own SNCF Network Data credentials and only access data you are allowed to access. SNCF Network Data's terms apply to your use of SNCF Network Data; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SNCF Network Data. SNCF Network Data and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data SNCF Network Data returns, lightly trimmed; it may be incomplete, delayed or changed by SNCF Network Data. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your SNCF Network Data account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent SNCF Network Data's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; SNCF Network Data may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your SNCF Network Data key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action SNCF Network Data takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-sncf-network-data

SNCF Network Data (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-sncf-network-data.connectorbay.com/mcp
• REST API: https://byok-sncf-network-data.connectorbay.com/openapi.json
• Live status: https://byok-sncf-network-data.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. SNCF Network Data (BYOK) never asks for them.