Feature

Agent Gateway

Ask an AI assistant about your own address book and travel plans, in plain language, and get an answer from your real apreet data rather than a guess.

Why is there a gateway instead of direct access?

So an assistant never gets your login or a raw backend credential. Every request passes through the Agent Gateway, which checks what you approved, narrows the response to a closed set of fields, and records the request.

Quick version. apreet already knows where you are going, from your calendar, and which of the people you know are in which cities, from your address book. The Agent Gateway lets an AI assistant you already use read that, so you can ask a question instead of opening an app and comparing lists yourself.

What you can ask

Two questions do most of the work, and both are ones people already ask themselves badly.

Who do I already know here?

You are in a city, or about to be. Somewhere in your address book are people whose home or work address is in that same city, and you have forgotten most of them. Asking is faster than remembering.

What is coming up, and who is there?

Ask what trips you have next week and get your real itinerary back, then ask who you already know in each destination. That is the whole loop apreet exists for, without opening apreet.

The answers come from the data you authorised: your itinerary, your address book, your matches. The assistant is reading your apreet account, not searching the internet and guessing.

Why a gateway, not a direct connection

apreet does not hand an assistant your login or a raw backend credential. Every request goes through the Agent Gateway, a layer built specifically to sit between an assistant and your account: it checks what you approved, narrows what comes back to a closed set of fields rather than everything the backend holds, and records the request. An assistant never talks to apreet's main systems directly, and there is no way to connect one that grants more than you explicitly approved.

The assistant talks to the gateway, and only the gateway, in both directions. It never reaches apreet's backend directly.

What it is not

It does not introduce you to strangers. It does not post anything anywhere. It does not write to your calendar or your address book. It is the same apreet, asked a different way.

An assistant connected this way can only read. There is nothing you can grant it that changes your apreet data.

How precise it is

Matching to a trip happens at the level of the city: a contact matches a destination when the city on their home or work address matches your stop. Asking about a place directly works differently, since apreet can measure real distance there, so a question like "who do I know near Zürich" returns an actual distance in kilometers, not just a city match. Either way, when a trip-based answer says a contact is in Munich, that means the city, not the street.

Before you connect

Four things worth knowing up front, because they decide whether this is for you.

  • Assistants. Claude and ChatGPT can connect today. Others are not supported yet.
  • Where. Setting it up happens on a computer, not from an AI app on your phone.
  • Effort. It is a one-time setup you do yourself, in the assistant.
  • Maturity. The Agent Gateway is new. Treat it as an early feature.

You decide what it can reach

Nothing is connected until you add apreet as a connector in your assistant and approve it on apreet's own screen. You approve what it may read, and you can revoke access at any time. Everything on that screen is a read permission. When you ask an assistant a question, the data you authorised is sent to that assistant, which is worth understanding before you start.

Read what an AI assistant can and cannot do, including where your data goes and how to switch it off. When you are ready, connect Claude or ChatGPT.