The streets, the grid, the air — the city wired to Vinkius AI Cities

Amsterdam Smart City inside your ChatGPT, Claude, and any other AI

Ask where the nearest free bike is, whether the air is clean along the canal, and when the last metro runs. Your AI answers with live city data.

We turned every system Amsterdam runs on (the bike docks, the wind on the grid, the air over the canals) into live Connectors. Connect once, and the assistant you already have open reads the whole city, live. The same wiring is yours to build on.

921,402

residents

219

km²

4,207

per km²

Ask AI about Amsterdam

How it works

Three steps, and Amsterdam answers.

Skip the app-per-service dance: the city arrives as a single connection your assistant reads natively.

  • 01

    Read the city

    seven are already wired as Connectors. Nothing to install, nothing to map. Open the page and they are there.

  • 02

    Connect once

    One link, and every client that speaks the protocol reads the same Amsterdam: ChatGPT, Claude, Gemini, Cursor, the rest.

  • 03

    Ask, or build

    Answers come in plain language, and the Connector behind an answer is exactly what your own app builds on.

Amsterdam

Everything your AI can reach in Amsterdam.

Eight systems, one connection. All eight are live today across 40 Connectors.

8 live
01

Mobility

Canals, trams and the densest bike network in the world — Amsterdam's movement reads street by street.

02

Energy

The Dutch grid feeding Amsterdam, and how green the hour is when the North Sea wind is up.

03

Environment

What the air over the grachten is doing, and the trees, waste and water systems that hold the city together.

04

Public services

The city's own records: addresses, monuments, incidents and the open-data catalogue behind them.

05

Culture

From the Rijksmuseum's galleries to tonight's gigs in the Jordaan — Amsterdam's evening, addressable.

06

Geography

The ground Amsterdam is built on: places, routes, distances, and how far the ring really is.

07

Commerce

The businesses and money moving through Amsterdam, from the canal-side studio to the trading floor.

08

Safety

The city's own outage and road-work map beside the delta's flood forecasts — when to cycle and when to wait.

A day in Amsterdam

One connection, from the first pedal to the last train.

The same wiring, hour by hour. Nothing here an app couldn't do, except you would need eight of them, and eight logins.

07:20

Before the rain arrives

The forecast puts a band over the city by nine, so the ride moves to the dock nearest the office instead of the scenic one.

Will it rain between 8 and 10 in Amsterdam? Find me a bike near the office.

09:15

The cleanest hour to run it

Wind is carrying the grid. Your AI names the hour to run the heavy job, and nothing runs outside it.

When is the grid cleanest in Amsterdam today? I have a heavy job to run.

12:40

Air, before the lunch loop

The corridor by the ring is running high, so the walk goes along the water instead of guessing which way is cleaner.

Is the air safe for a walk near the Amstel right now?

16:05

Parking, without the lap

Live availability at the facilities near the venue, and the route to the one with space rather than the queue.

Find parking with availability near the venue before 6, and route me there.

19:30

Tonight, decided

What is on, where, and the ticket page in the conversation. The evening sorted before you leave the table.

What is on in Amsterdam tonight? Send me the ticket page for two.

22:50

The last way home

The dock by the hotel has bikes at this hour. Your AI checks before it sends you to an empty one.

Is there a bike at the station near my hotel right now?

Build on the city

The same wiring is yours.

Reading Amsterdam is the demo. Building on it is the point: every system on this page is a Connector you can call from your own code.

  • 01

    One endpoint

    Every system, one connection

    No per-service auth, no per-system SDK. The same Connectors your AI reads are the ones your app calls.

  • 02

    Every client

    Works where you already work

    ChatGPT, Claude, Gemini, Cursor, Windsurf. Anything MCP-compatible reads the same Amsterdam, with no porting.

  • 03

    Your own apps

    Read the city, then write the app

    The layer every city page sits on is public. Build the local app that should have existed, on wiring that is already live.

FAQ

Everything you'd ask before connecting.

  • 01

    What do I get by connecting Amsterdam?

    Amsterdam's live systems (transit, bike share, parking, air quality, energy, events) become Connectors your AI calls directly. Ask in plain language and get a live answer in the assistant you already use. No new app, no login per service.

  • 02

    Which AI assistants does this work in?

    ChatGPT, Claude, Gemini, Cursor and any client that speaks MCP, the open protocol for connecting AI to tools. Connect once and every assistant you use reads the same city: nothing to reinstall when you switch.

  • 03

    Is the data really live?

    Yes. Every answer reads the source the moment you ask: the transit feed, the bike docks, the monitoring stations, the grid. Nothing pre-cached, nothing your AI invents. And the page shows only the systems that are wired and working today.

  • 04

    Isn't there already an app for each of these?

    There was. That was the problem. A download and a login for every question. Here one connection covers every system, in the assistant already open on your screen, and the same Connectors are the building blocks for whatever you make next.

  • 05

    Is it safe? Can my AI act on the city?

    Your AI reads the city; it never controls it. Where a Connector can act (holding a booking, reserving a spot) it acts on that service, never on public infrastructure. Everything runs on Vinkius: sealed, isolated connections, every action logged and visible, one switch that stops every agent.

  • 06

    Can I build on it?

    Yes. The same Connectors your assistant calls are open to you through one integration: a visitor concierge, a delivery router, a civic tool. Amsterdam is already wired: you build on live infrastructure instead of stitching a dozen APIs together.