1
Check the skill
Open the skills catalog. Review its dependency status, runtime compatibility and requested scopes. AP invoice reading, the Treasury skill and Payroll cosigner have blocked dependencies. See Skills catalog.
2
Review access and policy
Choose the eligible entity or explicitly provisioned agent vault through the available setup flow. Personal accounts do not automatically receive treasury vaults.Review the grant scopes, spending caps, chain and counterparty allowlists, and step-up threshold. The Trip budget package includes card-management permission; a balance query does not test that permission.
3
Connect the runtime
Follow the integration’s authentication instructions. Use Supported runtimes to check compatibility and the MCP tool reference for endpoints and schemas.
4
Make a read-only call
If the integration exposes
accounts.balance and your grant includes accounts:read, request the authorized vault’s balance. Check the response and account identity before continuing.A connection error, unavailable dependency or empty result does not prove the integration is ready for payments.5
Review activity and approvals
Review the available activity records. Confirm how approval requests are completed before enabling writes. The current agent audit page and URL-mode approval page are not fully connected; do not treat their display as a completed audit or approval.
Check a policy without sending funds
Wherepayments.simulate is available, use a request above the configured cap or outside the destination allowlist. Inspect the returned verdict. A simulation does not submit a payment or establish that a later payment will settle.