Skip to content
nuntio
Menu
Open the app
DocsSet up an agent

DocsAI agents

Set up an agent

Templates, the agent's policy, its rule, and the mode it runs in.

  1. #Start from a template, or from blank

    On Agents, pick a template or start from a blank form. A template only fills in the purpose, the period and the kind of rule. It never guesses a limit.

    TemplateWhen it pays
    Weekly AI creditsA fixed amount to one service every Monday at 9:00
    Top up when lowWhen a balance you record falls below a line
    Pay onceA single payment at a date and time you choose
    Monthly subscriptionThe same amount to one service on the 1st of every month, at 9:00

    Times are in your own time zone.

    On Monad mainnet no template is offered: every one pays a merchant on a rule, and there are no outside merchants on mainnet yet. Agents cannot buy AI compute yet either. See What an agent can buy today.

  2. #Set its policy

    Give the agent a name and a purpose, then set its limits. They follow the same rules as a person's policy:

    • an allowance above $0, refilled daily, weekly or monthly (every 30 days)
    • a cap per payment, or blank for no cap, never more than the allowance
    • payments per period, from 1 to 1,000 (20 by default)
    • when access ends: 30, 90, 180 or 365 days (90 by default)
    • at least one approved service

    You read back exactly what will happen before you create it.

  3. #Create it

    Nuntio then:

    1. creates the agent's own Privy server wallet, with a narrow Privy policy from the start, then sets its full Privy policy
    2. saves the agent in its registry as a draft, which cannot spend
    3. grants its policy on the account and approves each service
    4. marks the agent active, in Observe mode

    Creating an agent never moves money. If setup stops part way, retry it: the same name finds the same agent and the same wallet, so you never get a second one.

  4. #Add a rule

    On the agent's page, add a rule. There are two kinds.

    Pay on a date. Choose the service, the amount, a date and time, and whether it repeats: once, every week or every month. Add a note if you like.

    Top up when low. Choose the service, the balance that should trigger a top-up, the top-up amount and how long to wait between top-ups (6 hours by default, up to 720). Then record the service's balance on the agent's page with Record a usage reading. If the reading is below your line, the agent proposes the top-up on the worker's next check.

    Nuntio refuses to save a rule the contract would always refuse:

    • the service must be approved for the agent
    • the amount must be within the agent's cap and its allowance
    • a due time must be at least a minute ahead, within the next year, and before the agent's access ends

    Rules are versioned. Saving a new rule makes it the one in force, and earlier versions are never edited.

  5. #Choose a mode

    Switch between Observe, Confirm and Autonomous on the agent's page. Switching to Autonomous asks you to confirm first. Changing the mode moves no money.

#How scheduled payments behave

  • Each due time is paid at most once. Editing the rule after a due time was paid does not pay it again.
  • Repeats keep the first time of day. A weekly payment comes back every 7 days. A monthly payment set for the 29th, 30th or 31st lands on the last day of a shorter month.
  • Late payments are skipped, not paid late. If the worker could not pay within 6 hours of a due time, for example because it was down, that due time is skipped. A repeating schedule still pays its next one.
  • In Confirm mode, a due payment waits for you for up to 24 hours, then expires unpaid.
  • In Observe mode, the due time is only recorded.

#How top-ups behave

  • A reading must be recent: one older than 10 minutes when the worker sees it is ignored.
  • An agent has at most one payment in progress at a time.
  • After a top-up, the agent waits the time you chose before it proposes another.
  • In Confirm mode, a proposed top-up waits for you for up to 1 hour, then expires unpaid.

#Confirming a payment

In Confirm mode, a payment waiting for you shows Confirm payment on the agent's page. Pressing it records your confirmation. The worker sends the payment on its next check, and the contract decides. Nothing has moved until then.

#Pausing or revoking an agent

An agent's policy is a spender's policy on the account, so you pause, resume or revoke it the same way as anyone's. The contract then refuses its payments whatever the worker does, and the worker follows the chain. A revoked agent is never run again.