Campus Micromobility Vehicle Positions API

Live positions of shared micromobility vehicles on and around campus as GeoJSON, served from veoride.geoservices.tamu.edu inside Texas A&M's own geoservices estate. Verified 200 on 2026-09-01 returning 3,300 Point features. The scooter fleet is a vendor's; the feed is published from a Texas A&M host. Every feature's properties object is empty, so no vehicle id, type, battery level or availability is exposed — that absence is recorded deliberately.

Operations 1

GET /api/vehicles/basic/geojson Current shared-vehicle positions as GeoJSON #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/campus-micromobility"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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

OpenAPI Specification

texas-a-m-university-campus-micromobility-openapi.yml Raw ↑
# x-method: derived
# Authored by API Evangelist from live probes and published documentation on 2026-09-01.
# The in-file `method:` records HOW the evidence was obtained (probed / derived);
# this line records WHO WROTE THE FILE, in the provenance manifest's vocabulary.
openapi: 3.2.0
x-provenance:
  generated: '2026-09-01'
  method: probed
  source: >-
    Discovered in the Aggie Map application bundle
    (https://aggiemap.tamu.edu/main.c63a5258155f6cb9.js, HTTP 200, 2026-09-01) and fetched
    anonymously at https://veoride.geoservices.tamu.edu/api/vehicles/basic/geojson, which returned
    HTTP 200, application/json, 342,203 bytes, a GeoJSON FeatureCollection of 3,300 Point features
    with empty properties objects. Schema read from the observed payload.
  x-operator: institution
info:
  title: Texas A&M Campus Micromobility Vehicle Positions API
  version: 1.0.0
  description: >-
    Live positions of shared micromobility vehicles on and around the Texas A&M University campus,
    served as GeoJSON from veoride.geoservices.tamu.edu — a host inside Texas A&M's own
    geoservices.tamu.edu estate. The scooter fleet itself is operated by the vendor Veo; the feed
    that Aggie Map consumes is published from a Texas A&M host and is therefore recorded as an
    institution-operated surface with a vendor data origin, not as a vendor contract.

    Undocumented, unauthenticated and unversioned by the university. The observed payload carries
    geometry only: every feature's properties object is empty, so vehicle id, type, battery level and
    availability are NOT exposed. Recording that absence is the point of this contract.
  contact:
    name: Texas A&M GeoServices
    url: https://geoservices.tamu.edu/Support/
servers:
- url: https://veoride.geoservices.tamu.edu
  description: Texas A&M GeoServices micromobility feed
tags:
- name: Micromobility
  description: Shared vehicle positions on campus.
paths:
  /api/vehicles/basic/geojson:
    get:
      tags:
      - Micromobility
      operationId: getVehiclePositionsGeoJson
      summary: Current shared-vehicle positions as GeoJSON
      description: >-
        Returns the current positions of shared micromobility vehicles as a GeoJSON
        FeatureCollection of Point features. Verified 200 on 2026-09-01 returning 3,300 features. The
        "basic" path segment is reflected in the payload: properties are empty on every feature.
      responses:
        '200':
          description: GeoJSON FeatureCollection of vehicle positions.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/VehicleFeatureCollection'
components:
  schemas:
    VehicleFeatureCollection:
      type: object
      required: [type, features]
      properties:
        type:
          type: string
          enum: [FeatureCollection]
        features:
          type: array
          items:
            $ref: '#/components/schemas/VehicleFeature'
    VehicleFeature:
      type: object
      required: [type, geometry, properties]
      properties:
        type:
          type: string
          enum: [Feature]
        geometry:
          $ref: '#/components/schemas/PointGeometry'
        properties:
          type: object
          description: >-
            Empty on every one of the 3,300 features observed on 2026-09-01. No vehicle identifier,
            type, battery level or reservation state is published on this route.
          additionalProperties: true
    PointGeometry:
      type: object
      required: [type, coordinates]
      properties:
        type:
          type: string
          enum: [Point]
        coordinates:
          type: array
          description: '[longitude, latitude] in WGS 84.'
          minItems: 2
          maxItems: 2
          items:
            type: number