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.

Amsterdam runs on live systems: the bike dock on the corner, a grid that swings with the wind, air that shifts with the corridor, and more on any given night than one app could hold. We wired each one into a Connector your AI reaches as easily as it reaches a file. Ask it where the canal air is cleanest, or when the wind turns the grid cheap, and Amsterdam answers back. What used to mean an app per system is one connection now, and that connection is yours to keep.

98

capabilities

17

Connectors

7

systems

921,402 residents

219 km²

4,207 per km²

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.

Seven systems, one connection. All seven are live today across 17 Connectors.

7 live
03

Environment

27 capabilities

The air over the canals shifts with the corridor and the wind. Two monitoring networks read it, street by street.

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.

The honest limits

What this page does not do

  • 01

    Can my AI control the city's systems?

    No. It reads them, and where a Connector writes (holding a booking, reserving a spot), it writes to that service, not to the city. Nothing here gives an agent control over public infrastructure.

  • 02

    Is every Amsterdam service available?

    Not every service, no. The seven systems on this page are wired and live — every Connector in the ledger works today. Services we cannot reach yet simply are not on the page; the ledger grows when they are.

  • 03

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

    There was. Weather, air, parking, events, each one meant its own app and its own login. Here they are Connectors the AI you already use calls directly, and the same Connectors are what you build your own apps on. One connection instead of a drawer full of them.

  • 04

    Do I need to write code to use these?

    No. Connect a Connector, ask in plain language, and your AI does the rest. It works in ChatGPT, Claude, Gemini and any client that speaks the same protocol.