SNCF Open Data (BYOK)

SNCF Open Data (BYOK) — connector documentation

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

What SNCF Open Data (BYOK) is for

SNCF Open Data (BYOK) lets an AI assistant read your own SNCF Open Data data through the SNCF Open Data API with a key you supply (SNCF Open Data portal API key). Read-only: 7 tools (list_datasets, get_dataset, query_records, get_record, get_dataset_facets, get_catalog_facets, list_dataset_attachments). 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 data.sncf.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SNCF Open Data. SNCF Open 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 datasets about train stations does the SNCF Open Data portal have?"
• "What fields does the train stations dataset have?"
• "Show the first 20 records of the train stations dataset"
• "Show a single record of the train stations dataset by its id"
• "Which categories appear in the train stations dataset and how many records each?"
• "Which themes do the datasets of the SNCF Open Data portal use?"

What it does

• list_datasets: List and search the datasets of the portal catalog with ODSQL filters, facet refinements, ordering and paging. Each entry carries its id, metadata and field definitions.
• get_dataset: Get one dataset's metadata and the definition of its fields (name, label, type, description).
• query_records: Query the records of a dataset with ODSQL: select fields, filter with where/refine/exclude, group and aggregate, order and page. Field names depend on the dataset (see get_dataset).
• get_record: Read one record of a dataset by its record id.
• get_dataset_facets: Enumerate the values of a dataset's facet fields with their record counts, optionally narrowed by a filter.
• get_catalog_facets: Enumerate the values of the catalog's dataset facets (themes, publishers, keywords and similar) with counts.
• list_dataset_attachments: List the files attached to a dataset (documentation, PDFs, archives) with their titles and URLs.

BYOK key

You bring your own SNCF Open Data SNCF Open Data portal API key (https://data.sncf.com/account/). 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 data.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://help.opendatasoft.com/apis/ods-explore-v2/ (the API this connector calls, with a BYOK key)

Live from the SNCF Open Data API (data.sncf.com) with a BYOK key; documentation: https://help.opendatasoft.com/apis/ods-explore-v2/. 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 Open Data. SNCF Open 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 Open Data account.

Built for: Worldwide. Languages: English.

SNCF Open Data (BYOK) — Privacy Policy

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

What SNCF Open Data (BYOK) is. SNCF Open Data (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own SNCF Open Data data: Browse and query the open datasets of the SNCF open data portal (Opendatasoft Explore API) with your own portal API key. You bring your own SNCF Open Data SNCF Open Data portal API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one SNCF Open 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 data.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 Open 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 Open Data receives. The request we make on your behalf, including the key and the arguments, under SNCF Open Data's own terms and privacy policy. SNCF Open 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 Open 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 Open 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 Open 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 Open Data at any time to end all access.

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

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

SNCF Open Data (BYOK) — Terms of Service

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

1. The Service. SNCF Open Data (BYOK) provides: Browse and query the open datasets of the SNCF open data portal (Opendatasoft Explore API) with your own portal API key. 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 Open Data credentials and only access data you are allowed to access. SNCF Open Data's terms apply to your use of SNCF Open 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 Open Data. SNCF Open 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 Open Data returns, lightly trimmed; it may be incomplete, delayed or changed by SNCF Open Data. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your SNCF Open 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 Open 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 Open 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 Open 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 Open 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-sncfopendata

SNCF Open Data (BYOK) support

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

• MCP endpoint: https://byok-sncfopendata.connectorbay.com/mcp
• REST API: https://byok-sncfopendata.connectorbay.com/openapi.json
• Live status: https://byok-sncfopendata.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 Open Data (BYOK) never asks for them.