Telraam (BYOK)

Telraam (BYOK) — connector documentation

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

What Telraam (BYOK) is for

Telraam (BYOK) lets an AI assistant read your own Telraam data through the Telraam API with a key you supply (Telraam API key). Read-only: 7 tools (check_api_status, list_cameras, get_camera, list_cameras_for_segment, get_segment, get_hourly_traffic, get_access_details). 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 telraam-api.net. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Telraam. Telraam 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:

• "Is my Telraam API key working?"
• "Which of my Telraam cameras are active?"
• "What is the status of Telraam camera instance 9000001?"
• "Which Telraam cameras count traffic on segment 9000001463?"
• "When did Telraam segment 9000001463 last report data?"
• "How many cars and bikes passed Telraam segment 9000001463 yesterday afternoon?"

What it does

• check_api_status: Check that the Telraam API key is valid and the API server is running.
• list_cameras: List the Telraam traffic-counting cameras (instances) of the account with status, hardware version, calibration state and last data time. Owner ids and device addresses are left out.
• get_camera: Get one Telraam camera instance by id: status, hardware version, calibration and data times.
• list_cameras_for_segment: List the camera instances installed on one street segment.
• get_segment: Get the properties of one street segment: first and last data time, timezone and its camera instance ids. Geometry is left out.
• get_hourly_traffic: Get hourly traffic counts (heavy vehicles, cars, bikes, pedestrians, uptime, 85th-percentile speed) for a street segment or one camera over a time range of at most 3 months.
• get_access_details: Show which segments, cameras and devices the key can see with the Advanced API (needs access to the Advanced data).

BYOK key

You bring your own Telraam Telraam API key (https://telraam.net/en/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 telraam-api.net 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.

Notices

Telraam data are published under CC BY-NC 4.0: attribute Telraam and use the data for non-commercial purposes unless agreed otherwise.

Data sources

• https://telraam-api.net (the API this connector calls, with a BYOK key)

Live from the Telraam API (telraam-api.net) with a BYOK key; documentation: https://telraam-api.net. 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 Telraam. Telraam 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 Telraam account.

Built for: Worldwide. Languages: English.

Telraam (BYOK) — Privacy Policy

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

What Telraam (BYOK) is. Telraam (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Telraam data: Read your Telraam traffic-counting cameras and street segment traffic statistics (cars, bikes, pedestrians, heavy vehicles) with your own API key. You bring your own Telraam Telraam API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Telraam 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 telraam-api.net, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Telraam 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 Telraam receives. The request we make on your behalf, including the key and the arguments, under Telraam's own terms and privacy policy. Telraam acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Telraam 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 Telraam 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. Telraam (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 Telraam at any time to end all access.

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

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

Telraam (BYOK) — Terms of Service

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

1. The Service. Telraam (BYOK) provides: Read your Telraam traffic-counting cameras and street segment traffic statistics (cars, bikes, pedestrians, heavy vehicles) with your own 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 Telraam credentials and only access data you are allowed to access. Telraam's terms apply to your use of Telraam; 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 Telraam. Telraam 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 Telraam returns, lightly trimmed; it may be incomplete, delayed or changed by Telraam. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Telraam 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 Telraam'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; Telraam 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 Telraam 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 Telraam 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-telraam

Telraam (BYOK) support

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

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