AI agents

BoundlessPay gives AI agents useful access without giving them unchecked authority. Use a business-bound connection, grant only the scopes the agent needs, and keep value-moving work behind human approval.

Two connection models

• Scoped agent tools (MCP) let compatible agents discover BoundlessPay tools. Current tools include business context, permissions, balances, transactions, invoices, and invoice summaries.
• Delegated read access lets a person approve one business and a narrow set of read scopes through OAuth with PKCE. The initial delegated resources are business profile, balances, transactions, and invoices.

Permissions and approval

An access token is tied to one business. The platform checks its scopes and the person's live membership and role permissions. Removing membership, narrowing a role, disabling a client, revoking a grant, or letting it expire denies access.

Read tools may answer immediately when permitted. An agent can prepare controlled financial work, but anything that moves money or changes an important setting must enter the configured human approval flow. The agent does not approve its own proposal.

Audit and revocation

Every agent tool call is recorded with the connected business, credential, tool, permission scope, outcome, and time. A business can review and revoke delegated connections from Settings → Business OS → BOB Connections.

Start safely

1. Begin in sandbox and grant read-only scopes.
2. Confirm the agent can explain its granted permissions.
3. Test denied scopes and revoked access, not only successful reads.
4. Add approval policies before enabling any write-capable workflow.
5. Keep customer secrets and raw API keys out of prompts and agent memory.