extro✳
No-account agent workflow

Create a guest trip plan with the Extro MCP

Let an AI agent create a shareable Extro trip plan from structured events and places without requiring the traveler to authenticate first.

An agent can turn its confirmed recommendations into one polished Extro plan and return the link in the same conversation, even when the traveler has never used Extro.

Use create_guest_plan

Send a stable random clientSessionId, a retry-safe requestId, plan details, and up to 20 complete structured events or places. Do not put a name, email address, IP address, or other personal information in the session ID.

Extro creates or reuses the recommendations, builds the list, and returns a claim-enabled listUrl, a public preview URL, an expiration time, item counts, and the remaining conversation allowance.

Guest plan example
{
  "requestId": "nyc-weekend-001",
  "clientSessionId": "random-conversation-id-7f2f41d1",
  "plan": {
    "title": "A Food and Jazz Weekend in New York",
    "listType": "weekend",
    "city": "New York",
    "startDate": "2026-11-06",
    "endDate": "2026-11-08"
  },
  "recommendations": [
    {
      "type": "event",
      "name": "Friday Night Jazz",
      "startDateTime": "2026-11-06T20:00:00-05:00",
      "venueName": "Example Hall",
      "city": "New York",
      "url": "https://example.com/jazz"
    },
    {
      "type": "place",
      "name": "Example Bistro",
      "city": "New York",
      "website": "https://example.com/bistro",
      "whyRecommended": "A relaxed dinner near the evening venue."
    }
  ]
}

Seven days to keep the plan

The claim-enabled link opens the finished plan and explains when it expires. If the traveler signs in from that link, Extro transfers the list to their account, saves its events and places, and removes the expiration. Unclaimed guest lists stop resolving after seven days. Recommendation records remain available so Extro can reuse verified places and avoid duplicates.

Limits and safe retries

  • Up to 20 structured recommendations per guest plan.
  • Three guest plans per traveler conversation per day by default.
  • The same request ID and payload return the same plan instead of creating a duplicate.
  • A changed payload needs a new request ID.
  • Network, provider, and total service budgets protect Extro without treating a shared AI-provider address as one traveler.

When authentication is still useful

Guest creation intentionally accepts complete structured JSON and retains source URLs, but it does not run anonymous social-link extraction. Use the connected workflow when the traveler wants Extro to extract supported links, edit existing private lists, or access saved items.

Frequently asked questions

Can an AI agent create an Extro list without authentication?

Yes. The create_guest_plan tool creates a temporary shareable plan from complete structured events and places. The traveler can claim it by signing in within seven days.

Does Extro rate-limit every traveler behind the same AI provider IP together?

No. Hosted agents commonly share provider egress addresses. Extro uses a random conversation identifier for the small traveler allowance and keeps much broader provider and network safeguards for abuse control.