NEAR testnet

Spending limits and coverage for money your AI agents hold.

One vault per client. Agents can only send where and as much as the client allows. Contracts that can change under them are flagged, and coverage can pay out if they do.

Free check: can this contract still change under your agent?

Paste a NEAR account. Some contracts change with no transaction touching them, and most monitors miss it.

Examples (testnet, one per class)

No wallet needed. Read from public chain data.

Each agent gets one key. The vault checks every call.

Before any money moves, the vault checks the call against the client's limits and the contract's risk. Every amount sent is recorded on-chain.

Example

budi.testnetclient, owneryield-agent keyfunction-call keyvaultvault-budi.aruna.testnetslippagedaily capmutabilityvault.testnetCan't changedex.testnetUpgradeable by ownerrouter.testnetCan change silentlybridge.testnetUnknown, not coverable: refusedcoverage poolunderwriter capital

Four risk classes, read from public chain data

Anyone can rerun the three checks and get the same answer. What cannot be proved is written as unknown and never gets a price.

  • immutable_verified

    Can't change

    Code by hash, no full-access key, and none of the scanned imports in the WASM.

    Evidence
    No detected upgrade path, and sticky
    Price
    Lowest premium
  • local_upgradeable

    Upgradeable by owner

    The account's own code, or an upgrade path that cannot be ruled out.

    Evidence
    Detected
    Price
    Base premium
  • global_by_account

    Can change silently

    References a global contract another account can redeploy.

    Evidence
    Detected through a separate channel
    Price
    Highest premium
  • unknown

    Unknown, not coverable

    Cannot be determined from the available data.

    Evidence
    Not known
    Price
    Cannot be covered

A change most monitors miss. With global_by_account, the owner redeploys and the target's view_account.code_hash stays the same. Only view_code shows it. Aruna watches both, plus the owner's account.

Built for companies that run agents for clients

One vault per client. The client holds the funds and sets the ceiling, and the company runs the agents and cannot take the money. One URL shows the client what is enforced.

  • Client

    Owns the vault, sets the ceiling, withdraws, and can remove the operator at any time.

    • Set the ceiling
    • Withdraw funds
    • Remove the operator
  • Operator

    Adds agents within the ceiling, pauses and tightens. It cannot loosen limits or withdraw.

    • Add agents, pause, tighten
    • Loosen a limit
    • Resume an agent
    • Withdraw funds
  • Anyone checking

    Reads what an agent cannot do with no login, then verifies it with one command.

    • Send NEAR
    • Add a key

    No login needed.

  • Underwriter, on testnet

    Watches how much of a pool rests on one implementation, before real capital is at risk.

    • Read pool concentration
    • Watch each implementation