# About the Interact API category

**URL:** <https://community.firecrawl.dev/t/about-the-interact-api-category/12>\
**Category:** Interact API\
**Created:** [June 5, 2026, 5:01pm UTC](https://community.firecrawl.dev/t/about-the-interact-api-category/12 "2026-06-05T17:01:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ericciarla](https://yyz2.discourse-cdn.com/flex012/user_avatar/community.firecrawl.dev/ericciarla/32/24_2.png) [@ericciarla](https://community.firecrawl.dev/u/ericciarla)\
**Post date:** [June 5, 2026, 5:01pm UTC](https://community.firecrawl.dev/t/about-the-interact-api-category/12/1 "2026-06-05T17:01:43Z")

</div>

Chat about the Firecrawl Interact APIs.

---

<div class="post-metadata">

**Author:** ![LegoGuy](https://yyz2.discourse-cdn.com/flex012/user_avatar/community.firecrawl.dev/legoguy/32/26_2.png) [@LegoGuy](https://community.firecrawl.dev/u/LegoGuy)\
**Post date:** [June 5, 2026, 7:08pm UTC](https://community.firecrawl.dev/t/about-the-interact-api-category/12/2 "2026-06-05T19:08:03Z")

</div>

I’ve been trying to make Firecrawl play [agar.io](http://agar.io) with the interact api but it’s very difficult to have any complex logic be passed through the prompt layer. Would there be a way to decipher user intent for a recurring action on the page and leave the instance running for a bit instead of cutting the scrape session?

---

<div class="post-metadata">

**Author:** ![Max](https://yyz2.discourse-cdn.com/flex012/user_avatar/community.firecrawl.dev/max/32/23_2.png) [@Max](https://community.firecrawl.dev/u/Max)\
**Post date:** [June 5, 2026, 7:37pm UTC](https://community.firecrawl.dev/t/about-the-interact-api-category/12/3 "2026-06-05T19:37:49Z")

</div>

LegoGuy, that is awesome! `/interact` is designed for prompts with a well-defined single, clear task. As long as you reuse the same `scrapeId` and don’t call `stop_interaction`, the browser stays open (default: ~10 min total, ~5 min inactivity). Each interact call runs one execution and returns; the session persists for the next call.

For complex or recurring logic like this, use `code mode`not prompts. Since you’re trying to manage real-time logic, Browser Sandbox is worth a look. This provides a standalone session, configurable TTL, and CDP for Playwright.

The documentation can be really helpful for dissecting issues like this and may even provide more explicit advice for your use case. Highly recommend having your agent take a look (you can use Firecrawl to do this!). Docs: [Interact | Firecrawl](https://docs.firecrawl.dev/features/interact)