Pricing
Pay per event
Unlock the power of the Explorium Business Data Hub via the MCP with real-time access to comprehensive company, contact, and market intelligence—automating data enrichment, company/person lookups, feature discovery, and web search capabilities from Explorium’s vast data universe.
0.0 (0)
Pricing
Pay per event
0
4
4
Last modified
22 days ago
The Standby mode is a new, lightweight method for using Actors. Instead of starting an Actor for each input and waiting for results, the Actor remains ready in the background to handle arbitrary HTTP requests, just like any web or API server.
Read moreSend a HTTP request to the this URL, and wait for the response. To call the Actor, you need to have an Apify account. Replace <YOUR_API_TOKEN> with your API token, which you can find under Settings > Integrations in Apify Console.Learn more.
To view the specific endpoint of this Actor, go to README.
https://agentify--explorium-mcp-server.apify.actor?token=<YOUR_API_TOKEN>maxRequestsPerActorRunnumber
The maximum number of concurrent HTTP requests a single standby Actor run can accept. If this limit is exceeded, the system starts a new Actor run to handle the request, which will take a few seconds.
Default value of this property is 200
desiredRequestsPerActorRunnumber
The desired number of concurrent HTTP requests a single standby Actor run can handle. If this limit is exceeded, the system preemptively starts a new Actor run to handle additional requests.
Default value of this property is 150
memoryMbytesnumber
The amount of memory (RAM) allocated for the Actor standby run, in megabytes. With more memory, the Actor can typically handle more requests in parallel, but the number of compute units consumed and the cost also grow.
Default value of this property is 2048
idleTimeoutSecsnumber
If a standby Actor run doesn’t receive any HTTP requests in this amount of time, the system will finish the run. When a new request comes, the system might need to start a new standby Actor run to handle it, which will take a few seconds. Higher idle timeout increases the responsiveness but increases the costs as the Actor needs to keep running longer.
Default value of this property is 300