# Deposit agent tool definitions

`tools.json` is the source for these tool definitions. The [example app](https://github.com/atomicfi/deposit-agent-example) loads it at startup and supplies a handler for each tool. Each entry has `name`, `description`, and an input `schema`. The top-level `formatVersion` describes this file format, and `version` is the date the definitions last changed. Names, inputs and the number of tools can change between versions, so compare `version` with the one you built against before you update.

Read the [Switch Direct Deposit guide](https://docs.atomicfi.com/guides/ai-agent-deposit) and [tool definitions page](https://docs.atomicfi.com/reference/agent-tools) before wiring handlers. The example's tools and system prompt belong together. The download contains no executable backend or provider adapter.

Your server supplies the user context, the destination account and the identity details CoAuth uses, calls Atomic, stores `task-status-updated` webhooks, and sends the Transact launch config to the app as an artifact. It also mirrors your bank's Fractional Deposits settings, which Atomic's API doesn't return. The model receives company and connector IDs, but not credentials, public tokens, bank account details or identity details.

Sandbox results use simulated webhooks and do not prove that a live direct deposit was switched.