Tools require an authenticated, active account and an approved connection. Your host discovers the full input schemas from the server. This guide describes the current contracts.
list_pending_imports- ReadInspect owned forwarded deliveries and unconfirmed drafts. Repeat the same since window from page one to discover late-bound deliveries; reread known IDs for processing changes. Missing deliveries are not proof of success.
review_import_placements- ReadDiscover recent imports and receive server-side trip candidates, match reasons, missing facts and conflicts. Apply one clear match and report it; ask only for needed decisions. Incomplete inventories and uncertain cancellation associations remain unresolved.
get_import_decision- ReadRecover an owned draft decision after interruption, including corrections, exclusion reason, revision and the trip where it was applied.
record_import_decision- WritePersist the agreed target, corrected facts or exclusion with a decision revision. Changes require traveller review. Exclusion does not remove saved legs or resolve saved cancellation effects.
apply_import_placement- WriteApply agreed drafts atomically to one trip using revision guards and a UUID retry key. Reuse the exact request after interruption. Saved cancellations require traveller correction in the web app.
get_import- ReadRecover saved delivery or draft facts and outcomes, including dismissed drafts. Available sender, subject and message-ID headers are retained for new shared deliveries; legacy rows and missing headers remain null. Draft-level duplicate/change/cancellation classification is conservative and a hint only; a null classification (older drafts) is unresolved; ask the traveller before applying it. Partial or unresolved facts need review. Read a forwarded delivery with bounded backoff until imported, duplicate, failed, unsupported or needs_information.
dismiss_import- WriteExclude a pending draft with a durable outcome. Retries are safe; confirmed drafts and trips are not changed.
get_connection_status- ReadCall first to check the active account, masked email_hint, registered client, approved grant and currently available tools. Tell the traveller which account you are saving to in one line. A connection approved before Potniq asked for one permission can read but not change trips; it returns pending_user_action: approve_write_access until the traveller reconnects and chooses Allow.
get_email_forwarding_status- ReadCheck flag-gated forwarding availability, the reported shared destination and verification status for one sender_address. Forwarding is opt-in. If the traveller asks for it, unverified senders need verify_forwarding_mailbox in Profile; the traveller enters the code themselves. No other mailboxes or verification internals are returned.
list_itineraries- ReadFind current and upcoming trips by default. Use past or all to include history; page through longer lists.
get_itinerary- ReadRead a trip by its exact ID, found with list_itineraries, and show its trip card. Returns the trip and leg updated_at values used to guard edits. The leave_by_estimate in each remaining transit leg with a calculated departure time carries calculated_at, estimate_age_minutes, estimate_basis (current = car route checked within 90 minutes of leave-by; forecast = traffic forecast for a car, a fixed walking estimate, or an approximate route estimate; timetable = public transport timetable without live delays) and estimate_stale. When estimate_stale is true, say the leave-by time is an estimate from the calculated_at date, not a current check.
get_trip_completion- ReadReturn a read-only completion receipt for one trip and up to 20 supplied delivery or draft IDs: trip link, trip_state, per-source dispositions, routing status, leave-by times only when every route calculated, and unresolved items. Each leave_by entry carries calculated_at, estimate_age_minutes, estimate_basis (current = car route checked within 90 minutes of leave-by; forecast = traffic forecast for a car, a fixed walking estimate, or an approximate route estimate; timetable = public transport timetable without live delays) and estimate_stale. When estimate_stale is true, say the leave-by time is an estimate from the calculated_at date, not a current check. Covers only the supplied sources; agreed_source_set_verified is always false. Source content is never returned.
analyze_itinerary- ReadAssess a trip by explicit ID using saved facts: timing conflicts, arrival buffers, incomplete routes, missing details and the next timed action. Ready means no detected stored-data issues, not a travel guarantee. When next_action is a transit leg it carries calculated_at, estimate_age_minutes, estimate_basis (current = car route checked within 90 minutes of leave-by; forecast = traffic forecast for a car, a fixed walking estimate, or an approximate route estimate; timetable = public transport timetable without live delays) and estimate_stale. When estimate_stale is true, say the leave-by time is an estimate from the calculated_at date, not a current check.
check_what_if- ReadTest a proposed extra stop by explicit trip ID without changing the trip. Give the stop from search_places, how long you will stay, and either the leg to start after or your current location. Checks arrival at the next fixed flight, train or timed appointment against your saved buffers and returns fits, slack, the latest time to leave the stop and an optimistic to pessimistic range. Uses paid route lookups and is rate limited. Nothing is saved; add_leg is called only after you confirm.
list_departure_reminders- ReadRead the next leave-by time in the next 48 hours for each current or upcoming trip, with any recent change to it, and the reason when a trip has none. Optional limit defaults to 20 (maximum 50). Items can be up to 48 hours ahead: judge urgency from minutes_until and leave_by_local, not from an item existing. A change is shown only when Potniq recorded the earlier leave-by (leave-by emails on). Each item carries calculated_at, estimate_age_minutes, estimate_basis (current = car route checked within 90 minutes of leave-by; forecast = traffic forecast for a car, a fixed walking estimate, or an approximate route estimate; timetable = public transport timetable without live delays) and estimate_stale. When estimate_stale is true, say the leave-by time is an estimate from the calculated_at date, not a current check. When leave-by emails are on and delivery is active, Potniq may check the car or public transport route to the next fixed departure again about an hour before leave-by, and for a car also checks current traffic; otherwise times come from the saved route estimate. Each item carries leave_by_summary (leave in X, by the clock time) and current_traffic (car only, at most 90 minutes old, else null). No live flight or train status. Items expire at departure. No notifications.
get_leave_by_email- ReadRead whether leave-by emails are on for your account, the lead time, the minimum notice (min_notice_minutes, default 30), the masked address they go to, the other verified addresses you could choose instead (recipients, with the one in use marked), and whether you registered interest in WhatsApp notifications (not available yet). Separate from list_departure_reminders, which any read-permitted assistant can poll. Leave-by emails go before fixed departures (flights, trains, timed appointments) and are rolling out gradually; delivery says whether they are active for your account. When emails are on and delivery is active, Potniq may check the car or public transport route to the next fixed departure again about an hour before leave-by; otherwise times come from the saved route estimate.
search_places- ReadResolve a location before writing, then pass its candidate_id (valid for 1 hour) and address in the leg location. Confirm ambiguous matches and preserve Google Maps and provider attributions. Requires configured place search.
create_itinerary- WriteCreate a trip from 1–30 ordered travel items. Include a dated item and a location that participates in transit. Supply a UUID idempotency_key and reuse it with identical input after a timeout. Potniq generates the connecting transit.
add_leg- WriteAdd one travel item to an explicit trip. Supply a UUID idempotency_key and reuse it with identical input after a timeout. Potniq assigns its ID and recalculates affected transit.
update_itinerary- WriteChange an existing trip title using its explicit ID and required expected_updated_at from the last read.
archive_itinerary- WriteArchive a trip: hidden from default lists, kept and read-only, and not given back to your balance. Requires expected_updated_at from the last read. Restore it with unarchive_itinerary.
unarchive_itinerary- WriteRestore an archived trip. Requires expected_updated_at from the last read.
update_leg- WriteReplace one existing user leg. Requires expected_updated_at from the trip and expected_leg_updated_at from that leg. Also echo editable_updated_at as expected_leg_editable_updated_at when present to tolerate derived location-name changes. Read first and preserve unrelated details. Generated transit cannot be edited through this tool.
delete_leg- WriteRemove one existing user leg after the traveller confirms. Requires expected_updated_at from the trip and expected_leg_updated_at from that leg (or expected_leg_editable_updated_at when present). Origin, destination and generated transit legs cannot be deleted; transit is recalculated for the remaining legs. Does not use up or give back a trip.
set_leave_by_email- WriteTurn leave-by emails on or off for your account, and/or set min_notice_minutes (10 to 120, default 30; no email is sent when less than that remains before leave-by), and/or record or withdraw interest in WhatsApp notifications with whatsapp_interest (true or false; nothing is sent and no phone number is taken), and/or choose where the emails go with recipient_id ("sign_in" or an id from the recipients list; the assistant cannot add an address, you verify mailboxes in Profile). The assistant should ask you first. Turning it off cancels any queued emails. Leave-by emails go before fixed departures and are rolling out gradually. When emails are on and delivery is active, Potniq may check the car or public transport route to the next fixed departure again about an hour before leave-by; otherwise times come from the saved route estimate.
Writes need explicit trip IDs where applicable. Timed items need timestamps with offsets. Potniq assigns IDs and ordering; do not submit generated transit items. For create_itinerary and add_leg, generate one UUID idempotency_key per new operation and retain it with the input. After a timeout, retry the same key and input. Results identify the original saved trip or leg; use get_itinerary for current details. Edit tools still require rereading before retrying.