Agents can bring recommendations from any research workflow and use Extro as the organized, human-friendly destination for the result.
Three accepted input modes
- Link only: send one supported URL and let Extro extract the available event or place details.
- Structured JSON: send confirmed fields directly when the source platform is unsupported or the agent already has reliable data.
- Mixed: combine link-only sources, structured events, and structured places in the same list request.
{
"requestId": "nyc-weekend-001",
"list": {
"title": "New York Weekend",
"listType": "weekend",
"city": "New York",
"startDate": "2026-11-06",
"endDate": "2026-11-08"
},
"recommendations": [
{ "url": "https://www.instagram.com/reel/example/" },
{
"type": "event",
"name": "Friday Night Jazz",
"startDateTime": "2026-11-06T20:00:00-05:00",
"venueName": "Example Hall",
"city": "New York",
"url": "https://example.com/event"
}
]
}Supported link platforms
Instagram, TikTok, Facebook, Partiful, Posh, Eventbrite, Luma, DICE, Google Maps, Apple Maps, Yelp, TripAdvisor, Resy, and OpenTable. Call get_capabilities for the live list. For other sources, send structured JSON.
What happens after creation
create_list_from_recommendations returns the list URL immediately. Extro processes up to three independent sources concurrently, deduplicates retries, preserves each source URL, and reports ready, needs-review, or failed status per item. A request can contain up to 50 recommendations, including up to 30 links that require extraction. Call get_list_build_status until processing finishes, then get_list to read the final list.
Structured event fields
Use name, startDateTime, endDateTime, venueName, address, city, description, imageUrl, ticketUrl, and url. Dates use ISO 8601 with an explicit offset.
Structured place fields
Use name, address, city, description, placeType, website, phone, imageUrl, and url. The optional whyRecommended field becomes a note on the list item.