Skip to content
Eden Engine

Brisbane E-Mobility Trips: Monthly E-Scooter and E-Bike Numbers

brisbaneopendata/e-mobility-trips

Monthly e-scooter and e-bike trip numbers for Brisbane from Brisbane City Council: one row per month (YYYY-MM) with the number of e-scooter trips, e-bike trips and the e-mobility total, each sent as a text number. The dataset starts in December 2018. Page with limit (1 to 100) and offset; total_count says how many months exist. Contains data from Brisbane City Council, licensed CC BY 4.0, served by Omnial; not an official Brisbane City Council product.

activeper callv1

Price

$0.0026 per call

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $5.

Data source

Brisbane City Council

Contains data from Brisbane City Council, licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Served by Eden Engine; not an official Brisbane City Council product.

Use it

Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.

Connect once and your AI can find and run this tool, and any other it needs.

agent
// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "brisbaneopendata/e-mobility-trips" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "brisbaneopendata/e-mobility-trips" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "brisbaneopendata/e-mobility-trips", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "brisbaneopendata/e-mobility-trips", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

ChargePrice
Per call
$0.0026
Updated
Oct 20, 2026

Input and output schemas

Input schema
input_schema.json
{
  "type": "object",
  "required": [
    "limit"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "How many monthly rows to return, 1 to 100."
    },
    "offset": {
      "type": "integer",
      "maximum": 9900,
      "minimum": 0,
      "description": "How many rows to skip, for paging. Omit to start at the first row. The portal refuses an offset plus limit above 10000."
    }
  },
  "additionalProperties": false
}
Output schema
output_schema.json
{
  "type": "object",
  "required": [
    "total_count",
    "results"
  ],
  "properties": {
    "results": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "date": {
            "type": "string",
            "description": "The month the trips are for, YYYY-MM."
          },
          "trips_e_bikes": {
            "type": "string",
            "description": "Number of e-bike trips that month, as text."
          },
          "trips_e_mobility": {
            "type": "string",
            "description": "Total e-mobility trips that month, as text."
          },
          "trips_e_scooters": {
            "type": "string",
            "description": "Number of e-scooter trips that month, as text."
          }
        },
        "additionalProperties": true
      },
      "description": "The monthly rows returned."
    },
    "total_count": {
      "type": "integer",
      "description": "How many monthly rows the dataset holds in all, not how many were returned."
    }
  },
  "description": "The portal's records response.",
  "additionalProperties": true
}