Public Transport Victoria
Public Transport Victoria (PTV) is the Victorian Government public transport authority in Australia, covering metropolitan and regional train, tram and bus services. It publishes the PTV Timetable API (Version 3, documented in Swagger), which provides scheduled timetable, route and stop data for all Victorian train, tram and bus services including Night Network, real-time data for metropolitan services where available, disruption information, stop facility information and myki ticket outlet data. Access requires a developer ID and key; the dataset is listed on DataVic under the Department of Transport. ptv.vic.gov.au now redirects to transport.vic.gov.au.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Public Transport Victoria the way a machine reads it — 21 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Public Transport Victoria scores 36.1/100 (thin), with a separate agent-readiness read of 28/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Public Transport Victoria's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/public-transport-victoria/"
title="Public Transport Victoria on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/public-transport-victoria.svg"
alt="Public Transport Victoria Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/public-transport-victoria/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/public-transport-victoria/"
title="Public Transport Victoria on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/public-transport-victoria/card.svg"
alt="Public Transport Victoria Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Public Transport Victoria
Each block below is one kind of artifact we hold for Public Transport Victoria. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Public Transport Victoria Departures API
The Departures API from Public Transport Victoria — 2 operation(s) for departures.
Public Transport Victoria Directions API
The Directions API from Public Transport Victoria — 3 operation(s) for directions.
Public Transport Victoria Disruptions API
The Disruptions API from Public Transport Victoria — 6 operation(s) for disruptions.
Public Transport Victoria Fare Estimate API
The FareEstimate API from Public Transport Victoria — 1 operation(s) for fareestimate.
Public Transport Victoria Outlets API
The Outlets API from Public Transport Victoria — 2 operation(s) for outlets.
Public Transport Victoria Patterns API
The Patterns API from Public Transport Victoria — 1 operation(s) for patterns.
Public Transport Victoria Routes API
The Routes API from Public Transport Victoria — 2 operation(s) for routes.
Public Transport Victoria Route Types API
The RouteTypes API from Public Transport Victoria — 1 operation(s) for routetypes.
Public Transport Victoria Runs API
The Runs API from Public Transport Victoria — 4 operation(s) for runs.
Public Transport Victoria Search API
The Search API from Public Transport Victoria — 1 operation(s) for search.
Public Transport Victoria Stops API
The Stops API from Public Transport Victoria — 3 operation(s) for stops.
Scroll within the panel for all 11 ·
Agent Skills 4
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
public-transport-victoria-check-disruptions
AGENT SKILLpublic-transport-victoria-plan-ticketing
AGENT SKILLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Public Transport Victoria Rate Limits
RATE LIMITSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Public Transport Victoria API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Public Transport Victoria — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/public-transport-victoria · machine-readable index on apis.io
This is an independent, third-party profile of Public Transport Victoria, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.