Install Jentic One Beta

Connect the Transport for NSW Open Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Transport for NSW Open Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fopendata.transport.nsw.gov.au%2Fopendata-transport-nsw" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fopendata.transport.nsw.gov.au%2Fopendata-transport-nsw" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Transport for NSW Open Data API.

Plan a trip between two stops, points of interest, or coordinates

Return real-time departure information for a stop or platform

Search for stops by name or coordinates

Download the GTFS static schedule for buses

Stream GTFS-realtime feeds for buses and Sydney Trains

GET STARTED

Start building with Transport for NSW Open Data API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Transport for NSW Open Data API for, with concrete tasks.

★ AI Journey Planner Agent

An AI agent connected through Jentic answers travel questions by resolving place names to stops and planning a trip between them, so a user asking how to get from one suburb to another gets real journey options without the developer wiring the trip-planner parameters by hand. The agent runs the stop finder first, then the trip operation.

Find the stop ids for an origin and destination, then plan a trip between them and return the fastest option

Live Departure Board

A display or assistant shows upcoming services by requesting real-time departure information for a chosen stop or platform. Combined with the stop finder, a user types a place name and the product returns the next buses, trains, or ferries leaving nearby.

Resolve a stop by name and return its next real-time departures with times and line names

GTFS Data Pipeline

A transit-analytics tool ingests the GTFS static schedule for buses and the GTFS-realtime feeds for buses and Sydney Trains to track adherence and movement. The static schedule gives the planned timetable while the realtime feeds give live positions and updates for comparison.

Download the bus GTFS schedule and pull the Sydney Trains realtime feed to compare planned and actual service

Key Endpoints

6 endpoints — the transport for nsw open data api provides real-time and scheduled public transport data for new south wales, australia.

METHOD

PATH

DESCRIPTION

GET

/tp/trip

Plan a trip between two locations

GET

/tp/departure_mon

Get real-time departure information

GET

/tp/stop_finder

Search for stops by name or coordinates

GET

/gtfs/schedule/buses

Download the GTFS static schedule for buses

GET

/gtfs/realtime/buses

Get the GTFS-realtime feed for buses

GET

/gtfs/realtime/sydneytrains

Get the GTFS-realtime feed for Sydney Trains

GET

/tp/trip

Plan a trip between two locations

GET

/tp/departure_mon

Get real-time departure information

GET

/tp/stop_finder

Search for stops by name or coordinates

GET

/gtfs/schedule/buses

Download the GTFS static schedule for buses

GET

/gtfs/realtime/buses

Get the GTFS-realtime feed for buses

GET

/gtfs/realtime/sydneytrains

Get the GTFS-realtime feed for Sydney Trains

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Transport for NSW API by hand means registering for a key, passing it in the Authorization header, and learning its trip, departure, and GTFS feed parameters yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.

Permission scoping

The API is read-only, so a rule can keep your agent to just the trip-planning and departure operations and leave the bulk GTFS feeds out. You choose which operations it may call.

Credential isolation

Your Transport for NSW API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'plan a trip' or 'get the next departures', and Jentic returns the matching Transport for NSW operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Transport for NSW Open Data API through Jentic.

What authentication does the Transport for NSW Open Data API use?

The Transport for NSW Open Data API authenticates with an API key passed in the Authorization header, per its OpenAPI spec; you register for the key on the Open Data developer portal. Through Jentic the key is held encrypted by your own Jentic One instance and injected at call time.

Can I plan a trip with the Transport for NSW Open Data API?

Yes. The trip operation routes between an origin and destination given as a stop, point of interest, or coordinates and returns journey options. The stop finder resolves place names to stops first, and the departure operation gives real-time times for a chosen stop.

What are the rate limits for the Transport for NSW Open Data API?

The OpenAPI spec does not define rate limits for the Transport for NSW Open Data API. Transport for NSW sets per-key limits on its Open Data portal, documented at https://opendata.transport.nsw.gov.au, so check there before polling feeds frequently.

Can I limit what my agent is allowed to do with the Transport for NSW Open Data API?

Yes. Write a rule that allows only the trip-planning and departure operations, so the agent plans journeys and reads times while the bulk GTFS feed operations stay out unless you add them. The API is read-only, so there is no write path to expose, and every call is logged.

How do I plan a trip with the Transport for NSW Open Data API through Jentic?

Search by intent in Jentic with a query like 'plan a public transport trip', add the Transport for NSW Open Data API from the Jentic API Directory, and your agent resolves the stops then plans the trip between them. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Opendata Transport Nsw Transport for NSW Open Data API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyMaps GeolocationRouting DirectionsapiKey6 EndpointsREST

For Agents

Plan trips, get real-time departures, and find stops across New South Wales public transport, plus GTFS static and realtime feeds for buses and Sydney Trains.

Use for: Plan a trip from a station to an address in Sydney, Get the next departures from a bus stop, Search for a train station by name, Download the bus GTFS schedule

Not supported: Does not handle ticketing, fare payment, or vehicle booking. Use for New South Wales public transport trip planning and departure data only.

The Transport for NSW Open Data API provides real-time and scheduled public transport data for New South Wales, Australia. It plans trips between two locations, returns real-time departure information for a stop, searches for stops by name or coordinates, and serves GTFS static schedules and GTFS-realtime feeds for buses and Sydney Trains. Applications use it for journey planning and live departure boards.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

51%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Transport for NSW Open Data API to your agent

Capabilities

Start building with Transport for NSW Open Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Opendata Transport Nsw Transport for NSW Open Data API

Jentic AI Readiness Score

Transport for NSW Open Data API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness