PCLAS Agent fleets · load forecast · x402 $0.05 USDC / forecast

Move the work before the agent tips over.

PCLAS is a workload forecast and task-reassignment engine for agent fleets. It projects each agent's load over the next few periods and, while there is still room somewhere else, shifts tasks off the agents who are about to exceed capacity. The verdict is the worst case in the fleet, not the average.

STABLE · nobody exceeds capacity REASSIGN · a plan clears every peak CRITICAL · still over after the pass

How it works

  1. You send the fleet. Each agent has an id, a capacity, a current load, and optionally a short history. Tasks name their owner, a weight, and a priority from 1 (keep it if you can) to 5 (move it first).
  2. An agent with history gets Holt's linear forecast, alpha 0.5 and beta 0.3. The first periods are blended toward the load you declared, so the near term does not jump away from the number you just measured. An agent with no history is marked synthetic: a deterministic daily sine, phased from the agent id, plus a drift from how full they already are. Same id, same path, every time.
  3. Any period where projected load exceeds capacity is an overload. Risk from 0 to 100 scores how far over, how many periods, and how soon the first breach hits. Under capacity scores 0, even at 99%.
  4. One pass. Overloaded agents, worst risk first, give up their lowest-priority, heaviest tasks. A task moves only onto an agent whose recomputed forecast still fits under capacity on every period. The receiver with the most minimum headroom wins. History is not rewritten.

What you get back

forecast

Per agent, the horizon of projected load, the peak, when it hits, the risk, and whether the path was synthesized.

reassignments

Each move: task, from, to, and a reason that names the peak and the headroom that won.

after plan

Peak and headroom once the moves are applied. Negative headroom means the pass was not enough.

Price

$0.05

USDC per forecast. x402 on Base L2. Unpaid machine calls get HTTP 402 with the payment terms. A body that fails validation is a free 422 — garbage is not charged. This page is free.

POST

https://agentpaystore.com/pclas/api/forecast

Call it

curl -s -X POST https://agentpaystore.com/pclas/api/forecast -H 'Content-Type: application/json' -d '{"agents":[{"id":"agent-1","capacity":100,"load":96,"history":[90,92,94,96]},{"id":"agent-2","capacity":100,"load":30,"history":[40,36,32,30]},{"id":"agent-3","capacity":80,"load":44}],"tasks":[{"id":"task-9","agent_id":"agent-1","weight":18,"priority":5},{"id":"task-2","agent_id":"agent-1","weight":12,"priority":1}],"horizon":8,"volatility":0.3}'

With no payment header the response is 402. Retry with the x402 PAYMENT-SIGNATURE (or X-PAYMENT) header. The form below is the human path: this site is on the gate's allow-list, so the browser call is not charged.

Try it



  
What this will not tell you

  
The forecast is a screen, not a guarantee. Holt extrapolates the recent slope and will happily march an agent through the ceiling if the last few points were climbing. A synthetic path is a deterministic simulation seeded from the id — useful so a missing history still produces a stable answer, useless as evidence that the agent actually works that way. The reassignment pass looks only at capacity. It does not know skills, travel time, or deadlines, and it does not search for a globally optimal assignment. One agent still over after the pass is CRITICAL for the whole fleet. Treat the verdict as something you run before you staff the next hour, not as a promise about it.