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

Rio de Janeiro Smart City, live in ChatGPT, Claude, and any other AI

Ask if the beach is safe to swim at, when the next bus to Copacabana leaves, and whether the evening grid is running clean.

We turned every system Rio de Janeiro runs on (the beach forecast, the hydro on the evening grid, the air along the avenues) 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.

6,747,815

residents

1,200

km²

5,623

per km²

Ask AI about Rio de Janeiro

How it works

Rio, reached in three steps.

One connection instead of a separate app for the bikes, the air, the grid and the listings. Your assistant reads every one.

  • 01

    The city is already live

    The beach forecast, the hydro on the evening grid, the air along the avenues: seven, connected and live.

  • 02

    Connect your AI once

    One connection, and all of Rio is readable in ChatGPT and Cursor, in Claude and Gemini, and everywhere else the wire reaches.

  • 03

    Ask, then build on it

    Questions in ordinary words, answers from the city, and the same wiring available for your own apps.

Rio de Janeiro

Everything your AI can reach in Rio de Janeiro.

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

8 live
01

Mobility

The BRT, the bike lanes along the orla and the Uber home from the samba — Rio's movement, live.

02

Energy

The grid that powers Rio, read against ANEEL's own sector records and the national mix.

03

Environment

INMET watches the weather over the hills; the monitors watch the air over the avenues between them.

04

Public services

IBGE's census, BrasilAPI's registries, the transparency portal and the health regulator — Brazil's records, open.

05

Culture

What is on in Rio tonight, from the Brasileirão table to the Sympla queue for the samba.

06

Geography

The ground Rio sits on: places, routes, distances, and which side of the mountain you are on.

07

Commerce

The businesses and money moving through Rio, from the Pix transfer to the Selic behind the loan.

08

Safety

INPE's satellite eyes on fires and slopes, flood forecasts for the Baixada, and two alert feeds over the city.

FAQ

Everything you'd ask before connecting.

  • 01

    What do I get by connecting Rio de Janeiro?

    Rio de Janeiro'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. Rio de Janeiro is already wired: you build on live infrastructure instead of stitching a dozen APIs together.