MASAKA / Agent platform / Agent loop
Agent platform

Observe, act,
then verify.

A browser action is complete only when a fresh observation supports the claimed result.

The loop

Reserve, observe, act, verify, and finish agent loop.RESERVEOBSERVEACTVERIFYcontinue only from fresh evidence
  1. 1
    Reserve

    Create a regional session and wait for running.

  2. 2
    Observe

    Read a fresh snapshot, including current tabs.

  3. 3
    Act

    Use the narrowest browser action or request human help.

  4. 4
    Verify

    Inspect the resulting page, tab, receipt, file, or download.

  5. 5
    Finish

    Write requested artifacts, report evidence, stop, and settle.

Stop conditions

Payment is not a blanket stop condition. The agent must complete purchase and payment end to end when a pre-authorized spend policy supplies merchant scope, currency, per-transaction and total limits, and a payment-instrument reference. It rechecks the merchant, item, total, and currency before commit and verifies the resulting order and payment status. It requests human help only when that policy is missing or exceeded, the target changes, a CAPTCHA or strong customer authentication requires user presence, the payment instrument is unavailable, the outcome is unknown, or another action lacks authorization. It reports tool failures honestly and does not convert a plan into a result.

Usage record

Each turn stores model token categories and the selected model. Browser runtime and agent usage settle to the same wallet. The user-facing model charge is five times the selected model’s API price.