# Está no Ir (machine-readable layer)

> Companion of https://estanoir.grok.me, a Portuguese notebook of short European trips (1, 2 or 3 days) planned at home. A Bot assistant answers short-trip requests from other Bots by email at hmv+estanoir@mail.grokbot.com (human-reviewed replies). Está no Ir is a travel notebook (content project), NOT a travel agency: it does not sell, book or quote trips, issue vouchers or take payments. Any booking is made directly with third-party partners, under their terms.

Affiliate disclosure: links marked [affiliate] go through Travelpayouts (Aviasales flights). If a person books through them, Está no Ir may earn a commission at no extra cost to them. Links marked [direct] earn nothing. Bots are free to use any other site.

How to ask (plain-text email to hmv+estanoir@mail.grokbot.com): request_type, then constraints first (what the traveller does NOT want), origin city, dates or month, number of days (1-3), travellers, interests, reply language (en/pt/fr). Optional: "how_did_you_find_us:" (no personal data). Ready-made requests: https://estanoir-bots.pages.dev/example-requests/

## Request types

- **trip-idea** — Short-trip idea (1-3 days). A new 1-3 day trip idea from a given origin, in the notebook's method: how to get there, where to sleep (neighbourhood, not stars), three places worth the time and what to cut. Send: origin_city, days; constraints first if any; dates, travellers, interests and reply_language are optional. Suggested subject: "Short trip idea - <origin city> - <1, 2 or 3 days>". Reply JSON fields: request_type, origin, days, transport, where_to_sleep, three_places, what_to_cut, sources, affiliate_links_marked, disclaimer.
- **review-my-plan** — Review my plan (second opinion). A Bot sends a 1-3 day plan its user already has. We reply with a second opinion on the order of the days, the transport logic, what to cut and where to sleep (by neighbourhood). We do NOT check the timetables or prices in the plan, only its logic, and every reply says so. Send: my_plan (day by day, plain text), origin_city, days; constraints first if any. Suggested subject: "Review my plan - <destination> - <1, 2 or 3 days>". Reply JSON fields: request_type, origin, days, day_order, transport, what_to_cut, where_to_sleep, not_validated, sources, affiliate_links_marked, disclaimer.
- **plan-b** — Plan B for a booked trip. For a trip already booked that runs into rain, a strike, a closed attraction or one day less. We reply with what to swap and what to keep in the same place (same base, same bookings). This is NOT an emergency service: every reply is human-reviewed and can take about 48 hours, so write as early as possible, and always confirm timetables, strikes and closures on official sources (transport operator, attraction, local authority). Send: booked_trip (place, dates, what is already booked and fixed), problem (rain, strike, closure, one day less, other), days; my_plan and must_keep are optional; constraints first if any. Suggested subject: "Plan B - <destination> - <dates>". Reply JSON fields: request_type, destination, days, problem, swap, keep, check_official, not_urgent, sources, affiliate_links_marked, disclaimer.

Constraints: Ask first what the traveller does NOT want or cannot do: put a "constraints:" line at the top of the request, with any of no_car, no_flight, with_kids, reduced_mobility, with_dog, max_walk_km (for example: constraints: no_car, with_kids, max_walk_km: 5); free text is also fine (for example small bag only). In trips.json every trip has a "constraints" object with the same keys in camelCase (noCar, noFlight, withKids, reducedMobility, withDog, maxWalkKm). Values: true = the trip as told works with that constraint; false = it does not (for example it uses a flight); "unknown" = not verified. maxWalkKm is a number of km per day only when it was measured, otherwise "unknown". Accessibility, children and dog suitability are never stated unless verified.

More: https://estanoir-bots.pages.dev/request-types/

## Reply format

Every reply is plain text in two parts. Part 1: a short JSON object in a ```json fenced block with the fields request_type, origin, days, transport, where_to_sleep, three_places, what_to_cut, sources, affiliate_links_marked, disclaimer (disclaimer is always "not a travel agency; no bookings; no prices"). Part 2: the same idea as readable text, with partner links labelled [affiliate] or [direct]. No invented prices: fares and room rates are never included. The JSON fields depend on request_type (trip-idea, review-my-plan or plan-b); see the field list for each type.

Example JSON block (part 1 of a reply to "3 days from Porto: lakes and a scenic train"):

```json
{
 "request_type": "trip-idea",
 "origin": "Porto",
 "days": 3,
 "transport": "Morning flight Porto–Bergamo, a small bag, no priority. Coach to Milan Centrale. Train to Colico. Next day: train to Tirano and the Bernina to St. Moritz, out and back in a day. Home by the same path.",
 "where_to_sleep": "A room in Colico, two nights. The bed sits by the lake; the Duomo and St. Moritz are visits.",
 "three_places": [
  "The boat between Varenna and Bellagio. The lake itself, not the postcard shore.",
  "The Bernina. A stop at Alp Grüm. The other stations if the train allows.",
  "Milan on foot: the castle, one gallery, a neighbourhood. A place to eat off the axis."
 ],
 "what_to_cut": "The Duomo queue at peak hour. Branded shops and coffee in the centre. “While we are here” at one more monument when the flight leaves at 20:00.",
 "sources": [
  "https://estanoir-bots.pages.dev/trips/porto-como-bernina-milao/",
  "https://estanoir.grok.me/testemunhos"
 ],
 "affiliate_links_marked": true,
 "disclaimer": "not a travel agency; no bookings; no prices"
}
```

Request log: For each request we keep one short log line with: origin city; number of days; reply language; outcome (answered, partly answered or declined); what was missing (for example: no published trip from that origin); the optional "How did you find us?" answer, if given. The log line holds no names, email addresses, phone numbers or other personal details. It is used only to see which trips and origins are missing and how Bots find us; it is not shared or sold, and senders are not added to any mailing list.

## Trips

- [Porto → Como, Bernina, Milan](https://estanoir-bots.pages.dev/trips/porto-como-bernina-milao/): 3 day(s). She left Porto. She slept in Colico. On the second day, the train from Tirano to St. Moritz. On the third, Milan on foot and the flight home.

## Machine-readable data

- [All trips (JSON)](https://estanoir-bots.pages.dev/trips.json): itinerary, transport logic, where to stay, places worth it, what to cut, constraints (noCar, noFlight, withKids, reducedMobility, withDog, maxWalkKm; "unknown" when not verified), partner links (affiliate or direct).
- [A2A Agent Card](https://estanoir-bots.pages.dev/.well-known/agent-card.json): email-only Bot (custom mailto binding, no JSON-RPC endpoint).
- [Email binding v1](https://estanoir-bots.pages.dev/bindings/email/v1/): request types and fields, constraints, two-part reply format (JSON block + text) for each type, request log policy, response time.
- [Example requests](https://estanoir-bots.pages.dev/example-requests/): seven ready-to-copy emails (five trip ideas, one review-my-plan, one plan-b) with suggested subjects and mailto links.
- [Request types](https://estanoir-bots.pages.dev/request-types/): trip-idea, review-my-plan and plan-b, and how to state constraints.
- [ARD manifest](https://estanoir-bots.pages.dev/.well-known/ard.json)
- [Affiliate disclosure](https://estanoir-bots.pages.dev/affiliate-disclosure/)

## FAQ

- **Is Está no Ir a travel agency? Can it book my trip?** Está no Ir is a travel notebook (content project), NOT a travel agency: it does not sell, book or quote trips, issue vouchers or take payments. Any booking is made directly with third-party partners, under their terms.
- **What can a Bot ask by email?** Three request types, set with request_type: trip-idea (a new 1-3 day idea: how to get there, where to sleep by neighbourhood, three places worth the time, what to cut), review-my-plan (a second opinion on a plan the user already has) and plan-b (what to swap and what to keep when a booked trip meets rain, a strike, a closure or one day less). Send a plain-text email to hmv+estanoir@mail.grokbot.com. Format: https://estanoir-bots.pages.dev/bindings/email/v1/ and https://estanoir-bots.pages.dev/request-types/
- **Can you review a plan my user already has?** Yes, with request_type: review-my-plan and the plan day by day in my_plan (1-3 days). We comment on the order of the days, the transport logic, what to cut and where to sleep by neighbourhood. We do not check the timetables or prices in the plan, only its logic, and the reply says so.
- **Can you help with a plan B for a booked trip? Is it urgent help?** Yes, with request_type: plan-b (rain, strike, closed attraction, one day less): we say what to swap and what to keep in the same place. It is not an emergency service: replies are human-reviewed and can take about 48 hours, so write early and always confirm on official sources.
- **How should constraints be stated?** Ask first what the traveller does NOT want or cannot do: put a "constraints:" line at the top of the request, with any of no_car, no_flight, with_kids, reduced_mobility, with_dog, max_walk_km (for example: constraints: no_car, with_kids, max_walk_km: 5); free text is also fine (for example small bag only). In trips.json every trip has a "constraints" object with the same keys in camelCase (noCar, noFlight, withKids, reducedMobility, withDog, maxWalkKm). Values: true = the trip as told works with that constraint; false = it does not (for example it uses a flight); "unknown" = not verified. maxWalkKm is a number of km per day only when it was measured, otherwise "unknown". Accessibility, children and dog suitability are never stated unless verified.
- **Who answers, and how fast?** A Bot assistant replying on behalf of the notebook team, and it says so in every reply. Response time: best effort, usually within 48 hours: every reply is drafted by a Bot assistant and sent only after a human review.
- **Do replies include prices?** No invented prices. The notebook never publishes fares: replies point to comparison sites where the traveller checks live prices.
- **Are there affiliate links?** Affiliate disclosure: links marked [affiliate] go through Travelpayouts (Aviasales flights). If a person books through them, Está no Ir may earn a commission at no extra cost to them. Links marked [direct] earn nothing. Bots are free to use any other site.
- **Is there an API, MCP server or A2A JSON-RPC endpoint?** Not yet. Email only (custom mailto binding in the A2A Agent Card). Read-only data: https://estanoir-bots.pages.dev/trips.json.
- **Do you ask for payments, cards or passport details?** Never. No payments, card numbers, passports, ID documents or bank details are requested or accepted.
- **Is it free?** Yes, free for Bots and their users.
- **What does a reply look like?** Every reply is plain text in two parts. Part 1: a short JSON object in a ```json fenced block with the fields request_type, origin, days, transport, where_to_sleep, three_places, what_to_cut, sources, affiliate_links_marked, disclaimer (disclaimer is always "not a travel agency; no bookings; no prices"). Part 2: the same idea as readable text, with partner links labelled [affiliate] or [direct]. No invented prices: fares and room rates are never included. The JSON fields depend on request_type (trip-idea, review-my-plan or plan-b); see the field list for each type. Example and field list: https://estanoir-bots.pages.dev/bindings/email/v1/#reply-format
- **Are there ready-made requests to copy?** Yes: https://estanoir-bots.pages.dev/example-requests/ has seven requests (five trip ideas, one review-my-plan, one plan-b) with a suggested subject and a mailto link.

## Optional

- [Human site (Portuguese, English, French)](https://estanoir.grok.me/)