Learn
Controls for automated money, answered plainly.
Direct answers on the trading-bot back office, AI agent spending limits, kill switches, prediction-market risk controls, agent guardrails and x402 payments.
How to set spending limits for AI agents
Give the agent a permission, not a wallet. With Nevarn the agent acts on a separate working balance under a permission bounded four ways — where it may act, what it may do, a ceiling per transaction with a rolling daily limit, and an expiry of at most ninety days. A missing limit denies rather than permits.
Read the answerA kill switch for trading bots that actually stops them
A kill switch should stop the bot at the point of signing, not ask the bot to stop. In Nevarn one action halts all signing on an account, effective on the next request — not a support ticket. Every order proposed after that is refused and recorded, and revoking a permission deletes the material that could sign.
Read the answerRisk controls for prediction-market bots
Rule on each order before it reaches the venue. Nevarn describes every live prediction-market buy — market, direction, size, the price and how stale it is, collateral, open positions — to Decionis, an independent execution authority. Only a proceed ruling releases the trade; refuse, refer and hold stop it, and an unreachable authority means refused.
Read the answerGuardrails for agent wallets
Keep the agent away from the key and the money it does not need. Nevarn splits each customer into two accounts: the wallet that holds their money, and a working balance Nevarn may act on under a bounded, expiring permission. The customer chooses how much moves across, and that amount is the most at risk.
Read the answerHow to accept payments from AI agents
Publish what you sell where agents can read it, and put a ruling before the money moves. With Nevarn a merchant gets a UCP business profile and catalogue an agent can search, a checkout that returns exact x402 USDC payment requirements, Decionis ruling on the exact intent before settlement, idempotent retries, and an order receipt.
Read the answerHow to set up x402 payments as a merchant
Answer a 402 with exact payment requirements, then verify and settle the buyer's signed authorisation before serving. Nevarn's facilitator speaks x402 version 2 only: it checks that the payment goes to one of your receiving accounts for the exact amount, then settles it once through its relayer; in UCP checkout, Decionis rules on the exact intent first.
Read the answerWhat it costs to accept payments from AI agents
With Nevarn a merchant pays 0.5% of each settled payment an AI agent makes, with no monthly fee. A refused, failed or reverted payment costs nothing. The payment reaches the merchant's wallet in full, and the fee is recorded in the merchant's books as owed to Nevarn, so every payment's cost is visible.
Read the answerThe back office for trading bots and agents, compared
A back office for trading bots and agents runs the strategy's operations, takes each ruling from outside the strategy, signs only inside a bounded mandate and keeps one book against the chain. Wallet vendors, custodians, bot platforms and accounting tools each document part of that; Nevarn's case is joining them in one system.
Read the answerGlossary: execution authority, mandate, fail-closed and more
A glossary of the terms Nevarn uses: execution authority, mandate, fail-closed, drift, halt and double-entry. Each describes one part of the same idea — an automated actor may move money only inside limits someone set, every decision is recorded, and the books are checked against the public chain.
Read the answer