Separate page reading from tools

Agent 19
HTTP/2HTTP/2HTTP/2HTTP/2HTTP/2Users5 req/sPartner apps20 req/sWorker2 vCPU · 2 GBLLM API1 vCPU · 1 GBEmail servi…1 vCPU · 1 GBExternal API1 vCPU · 1 GB
HTTP/2HTTP/2HTTP/2HTTP/2HTTP/2Users5 req/sPartner ap…20 req/sWorkerLLM APIEmail serv…External A…

Fix the board. Turn every goal green.

Traffic
Tasks5 req/s · reads onlyPages20 req/s · reads only
Limit
Worker answers about 6,700 req/s
Bill
  • Worker8 USD/mo
  • LLM API4 USD/mo
  • Email service4 USD/mo
  • External API4 USD/mo
20 of 40 USD/mo

Goals

Not tested yet

99 of 100 requests finish faster than this.The share of requests that fail or get no answer.What the servers and services cost each month.

The support agent reads web pages and calls email and CRM tools. One page held hidden text with orders for the agent, and the agent obeyed them. Stop page text from steering tool calls. Keep task p99 below 4 s and errors below 1 percent. You may make 4 edits.

14:05. Right after it read a help page, the agent emailed 2,300 customer records to an outside address.

A reader with no tools stops page ordersTap or press Space to add or remove the reader

Separate reader · 0 of 100 attacks reach a tool

Parts you can add: Worker, API server, Web firewall, Approval step, Secret store. At most 2 parts. Budget: 40 USD/mo.

Tap a part to add it, or drag it onto a trace.Click a part to add it, or drag it onto a trace.