Skip to main content
Who is signed in, credits, agent permissions and auto top-up. 5 operations. How to call them, and what the answers mean: Operations reference.
Generated from the operation catalog: src/lib/ops/public-catalog.json in publicsummerengine at 0d85f61e2b and the summer-engine npm package 4.0.0 for engine and local operations. If something here is wrong, the operation’s definition is wrong.

permissions

account.permissions: Read my agent permissions What the person lets their agents do without asking, in six groups (true: runs at once; false: answers needs_approval with a link). Reads change nothing and always run. Next: the op you want, or account.set_permissions. Inputs: No inputs.
Example: May I change prices without asking?

set_auto_top_up

account.set_auto_top_up: Change auto top-up Ask the person to turn auto top-up on or off or change its amounts: when credits fall below one amount, Summer adds another from their saved card, within a monthly limit. Always needs their yes in Studio. Next: jobs.wait. Inputs:
Example: Keep credits topped up.

set_permissions

account.set_permissions: Change my agent permissions Ask the person to turn agent permission groups on or off. Always needs their yes in Studio, even to turn one off. Returns an approval link; nothing changes until they approve. Next: jobs.wait. Inputs:
Example: Let the agent send invites without asking.

turn_off_auto_top_up

account.turn_off_auto_top_up: Turn off auto top-up Ask the person to turn off auto top-up, as Turn off on Studio Billing does: Summer stops adding credits from the saved card; the card stays for next time. Always needs their yes in Studio. Next: jobs.wait. Inputs:
Example: Stop automatic charges.

whoami

whoami: Show who is signed in Show the signed-in Summer account: user id, the agent app, plan, credits and whether generation is unlocked. Returns the account. Free. Next: games.list. Inputs: No inputs.
Example: Check the account and credits before generating.