# Cubic Corporation

> Cubic Corporation is a San Diego defense and public-transportation technology company. Its two
> segments are Cubic Transportation Systems (fare collection, the Umo mobility platform,
> GRIDSMART and Trafficware traffic management) and Cubic Defense (training and mission systems).
> Cubic sells systems under agency and government contracts, not as a self-serve developer
> product, and it operates no developer portal.

Generated by API Evangelist on 2026-09-19. Cubic publishes no llms.txt of its own; probed
https://developer.cubic.com/llms.txt (301 to a coming-soon page), https://www.cubic.com/llms.txt
(404), https://umoiq.com/llms.txt and https://retro.umoiq.com/llms.txt (HTTP 200 returning an
HTML shell, not a document). This file is our description of Cubic's public API surface, not
Cubic's.

## The one public API

Cubic has exactly one API with public documentation: the **Umo IQ Public Feed**, formerly the
NextBus Public XML Feed, served by Cubic Transportation Systems.

- Base URL: https://retro.umoiq.com/service
- Documentation: https://retro.umoiq.com/xmlFeedDocs/NextBusXMLFeed.pdf (PDF, revision 1.24, 18 May 2021)
- Authentication: none. Anonymous, read-only, free to use.
- Formats: /publicXMLFeed (text/xml) and /publicJSONFeed (application/json)
- Shape: one GET endpoint per format, with a required `command` query parameter selecting the operation.

Commands: `agencyList`, `routeList`, `routeConfig`, `predictions`, `predictionsForMultiStops`,
`schedule`, `messages`, `vehicleLocations`, `vehicleLocation`.

What it returns: the transit agencies Cubic serves, their routes, stops, directions and map
polylines; live arrival and departure predictions; published timetables; active service messages;
and live GPS vehicle positions.

## Things an agent must know before calling it

- **Every response is HTTP 200, including errors.** Failure arrives as an `Error` element with a
  `shouldRetry` attribute: `true` means the agency server was initialising, wait 10 seconds and
  retry; `false` means the request is wrong.
- **Do not use the documentation's example agency.** The PDF uses `sf-muni`, which no longer
  resolves. Call `agencyList` first. Seventeen agencies were live on 2026-09-19, including
  `ttc`, `omnitrans`, `stl`, `ccrta` and `ucb`.
- **Poll at most once every 10 seconds.** Published limits: 2 MB per 20 seconds per IP, 100
  routes per `routeConfig`, 150 stops per route for `predictionsForMultiStops`, 5 predictions per
  stop, 5-minute span for `vehicleLocations`. No rate-limit headers are returned, so a client
  cannot observe its budget and must self-police.
- **All values are strings** in both formats, including coordinates and booleans.
- **In JSON, one element is an object and several are an array** (`route`, `vehicle`,
  `predictions`, `Error`). Handle both.
- Send `Accept-Encoding: gzip, deflate`; the provider documents a 50-85% size reduction.
- `Access-Control-Allow-Origin: *` is returned, so the feed is callable from a browser.

## Repository artifacts

- openapi/cubic-umo-iq-public-feed-openapi.yml — OpenAPI 3.1 written by API Evangelist from the provider's PDF and checked command-by-command against the live host
- examples/cubic-umo-iq-public-feed-examples.yml — real captured request/response pairs
- conventions/cubic-conventions.yml — dispatch, error envelope, polling, typing traps
- errors/cubic-problem-types.yml — the four error conditions and the shouldRetry contract
- rate-limits/cubic-rate-limits.yml — the five published limits and the absence of headers
- lifecycle/cubic-lifecycle.yml — stability policy, the absent deprecation policy, host lineage
- changelog/cubic-changelog.yml — the PDF revision history, 2009 to 2021
- data-model/cubic-data-model.yml — agency/route/stop/vehicle entity graph
- conformance/cubic-conformance.yml — measured non-conformance to GTFS, GTFS-Realtime, SIRI, OGC API
- authentication/cubic-authentication.yml — why there is nothing to authenticate with
- skills/ — two agent skills: next arrivals at a stop, track a bus
- mcp/cubic-mcp.yml — a DERIVED candidate tool list; Cubic ships no MCP server
- packages/cubic-packages.yml — Cubic ships no SDK; third-party NextBus clients listed for context
- well-known/cubic-well-known.yml — 104 probed paths across 8 hosts, zero real documents

## Surfaces that exist but are not public

- **Umo IQ agency portal** (https://rider.umoiq.com/) — agency-facing, behind a login.
- **GRIDSMART API** — documented at support.gridsmart.com, which redirects to a login.
- **Trafficware support** — support.trafficware.com, same posture.
- **developer.cubic.com** — resolves, but every path 301s to www.cubic.com/coming-soon and the
  host sits behind an Imperva bot challenge. There is no Cubic developer portal today.

## Company

- Website: https://www.cubic.com
- Newsroom: https://www.cubic.com/news-events
- Leadership: https://www.cubic.com/about/people/all
- Privacy policy: https://www.cubic.com/privacy-policy
- Support: https://www.cubic.com/support
- Feed support contact: umoiq.support@cubic.com