# Subscription agent tool definitions

`tools.json` contains the current tool definitions from the [example app](https://github.com/atomicfi/manage-agent-example). Each entry has `name`, `description`, and `schema`, matching the example's input schema. The top-level `formatVersion` describes this file format; `source.commit` records the example revision. The tool set is versioned, and names, inputs and the number of tools can change between versions.

Read the [Cancel Subscriptions guide](https://docs.atomicfi.com/paylink/guides/ai-agent-cancel) and [tool definitions page](https://docs.atomicfi.com/paylink/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 and conversation context, calls Atomic, stores task webhooks, and sends launch artifacts to the app. The model receives company and action IDs, but not credentials or public tokens. Cancellation and refresh are separate tasks; read account data after the refresh before confirming the plan's final state.

## Update the snapshot

In the public-docs repo, with a checkout of the example repo available:

```sh
node scripts/sync-manage-agent-tools.mjs /path/to/manage-agent-example COMMIT
node scripts/sync-manage-agent-tools.mjs /path/to/manage-agent-example COMMIT --check
```

This copies names, descriptions, and input schemas without importing handlers or opening the example's database. Review changes to handlers, the system prompt, and the guide at the same time. Update the pinned source link in the tool reference, run docs checks, and publish the snapshot with the guide.

Sandbox results use fixtures and do not prove that a live merchant subscription was cancelled.