Connect an AI assistant to your driving journal
bino talks to AI assistants directly. Point your assistant at one address, approve the connection once, and it can read your trips and fill in what the Swedish Tax Agency asks for — purpose and who you visited — without you clicking through the rows yourself.
How to connect it
- Open your assistant's connector settings (MCP servers) and add
https://bino.se/api/mcp - The assistant sends you to bino, where you sign in and approve
- Done. It can now read and classify your trips.
There is no key to create and nothing to copy beyond the address above. The connection uses the same sign-in as the app, and you can remove the access at any time under Settings → Connected apps. The app then stops working immediately, even if it is still set up in the assistant.
Examples
The useful part is letting the assistant combine bino with something it already knows about you. Your calendar knows why you drove; bino knows that you drove.
Use my calendar to classify the trips in bino automatically.
What the assistant does
- 1.
list_tripsfetches the business trips missing a purpose or contact - 2.
(your calendar)reads what you had booked on those days and times - 3.
classify_tripfills in purpose and contact where they line up
Result: Trips read “Client meeting — Acme AB” instead of empty fields, and every change is marked with an AI badge in the journal.
Requires your assistant to be connected to your calendar as well. bino never reads your calendar — the assistant is the one that sees both.
Which business trips are missing a purpose? List them so I can fill them in.
What the assistant does
- 1.
list_tripswith the incomplete-business-trips filter
Result: Exactly the trips that would not survive an audit — the two fields required on every business trip.
How many business kilometres did I drive in July?
What the assistant does
- 1.
summarize_journalsums the month in the database
Result: Business and private kilometres per month. The total is computed in the database, so it covers the whole period rather than the most recent trips.
Every trip between home and the station on a weekday morning is a business trip. Classify them.
What the assistant does
- 1.
list_tripsfinds the trips matching the pattern - 2.
classify_tripsets classification and purpose on each one
Result: A recurring pattern classified in one go — but you see which trips it covered before you say yes, and you can undo in the app.
What the connection can do
- Read your trips — dates, addresses, distance, classification and purpose
- Summarise business and private kilometres per month
- Classify — set business/private, purpose and contact
It cannot delete trips, merge them or import new ones. Those change what the journal is rather than what it says, and those decisions belong with you in the app.
Before you approve
- The app can read everything you can read — the whole journal, which is what the tools above need. But it can only change a trip's classification, purpose and contact. It cannot delete trips, merge them, touch your settings or your Tesla connection — the database refuses every such write, not just the tool list. Still, only approve assistants you trust, and remove the access under Settings → Connected apps when you stop using it.
- You can see what was the AI. Trips a connected app has changed carry an AI badge in the journal, and changes that overwrite text you already wrote are saved to the trip's edit history.
- Check it before you file. An assistant infers from what it can see. It is your journal and your signature — read what it filled in.
- If you have end-to-end encryption enabled, the connection will not work. Your journal is unlocked in the browser with a key the server never has, so there is nothing for an assistant to read. That is encryption working, not a fault.
- The connection requires an active subscription, the same as exporting does.
Want to try bino first?
Try the demo — a made-up journal you can click around in without an account. Or read the help page on how import and export work.