How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Metro Transit

Metro Transit Planner API

The Planner API from Metro Transit — 8 operation(s) for planner.

Documentation Provider Profile APIs.io OpenAPI GitHub

Metro Transit Planner API is one of 4 APIs that Metro Transit publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Planner. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 8 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://svc.metrotransit.org/nextripv2.

8 operations 8 paths 10 schemas 2 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://svc.metrotransit.org/nextripv2
Resource Areas
1

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 2 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Planner 8
GET
/tripplanner/findaddress/{magicKey}/{geolocator}
2 params → 200400500
POST
/tripplanner/moreinfo
1 param → 200400500
POST
/tripplanner/nearestlandmark
body → 200400500
POST
/tripplanner/nearestparkandrides
body → 200400500
POST
/tripplanner/plantrip
body → 200400500
POST
/tripplanner/routelandmarks
body → 200400500
POST
/tripplanner/servicenearby
body → 200400500
GET
/tripplanner/suggest/{text}/{location}
2 params → 200400500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are PlantripInput (8 properties), ProblemDetails (5 properties), FindAddressResponse (4 properties), PlannerLocation (3 properties). Each schema is shown below with its type and property counts.

RoutelandmarksInput
object
3 properties
FindAddressResponse
object
4 properties
NearestlandmarkInput
object
3 properties
NearestparkandrideInput
object
1 property
Point
object
2 properties
Suggestion
object
3 properties
ProblemDetails
object
5 properties
ServicenearbyInput
object
3 properties
PlannerLocation
object
3 properties
PlantripInput
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

metro-transit-planner-api-openapi.yml Raw ↑

Other APIs Metro Transit publishes across the network.

Metro Transit Alerts API
AE Profile APIs.io
Metro Transit NexTrip API
AE Profile APIs.io
Metro Transit Schedule API
AE Profile APIs.io
#Planner
← Back to M APIs
API Details
ID
metro-transit:metro-transit-planner-api
Base URL
https://svc.metrotransit.org/nextripv2
Docs
https://svc.metrotransit.org/swagger/index.html
Provider
Metro Transit
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=metro-transit-planner-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/metro-transit-planner-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Metro Transit Planner API, 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.