> ## Documentation Index
> Fetch the complete documentation index at: https://agents-docs.lightspark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Accounts

> Let your customers' AI agents get paid, pay people and spend, from an account the customer owns, under limits and approvals Grid enforces.

> [!NOTE]
>
> The Agents API must be enabled for your platform; until it is, agent endpoints answer `403`. To enable it, [book a demo](https://www.lightspark.com/contact) or reach out to your Lightspark contact.

Let your customers connect an AI agent to their account and hand it real financial work: getting paid, paying people and suppliers, buying online, and splitting revenue. This works for individuals and for businesses. A business can give each team member's agent its own budget on one shared balance, pay contractors who have no account, and pay a whole list of people in one approved run.

The customer keeps ownership of the account. Grid checks every agent action against the policy the customer set, and either runs it, refuses it, or holds it for the customer to approve. The agent can run in an AI app, on the customer's device, or in your own product. Grid does not run the agent - it provides the agent's credentials, policy checks, approvals and the audit trail.

## Two ways to offer agent accounts

> [card] [Add Lightspark to your AI app](https://agents-docs.lightspark.com/agent-accounts/ai-app-connector.md)
>
> For AI companies. List Lightspark as a connector in your app. Your users sign up, verify and approve payments with Lightspark, and your assistant calls Lightspark over MCP. You run no payments backend.

> [card] [Add agents to your Grid platform](https://agents-docs.lightspark.com/agent-accounts/implementation-overview.md)
>
> For Grid platforms. Your backend creates an agent for each of your customers, sets its policy, and shows approvals in your own app. Your customers keep their accounts with you.

Both paths give the agent the same capabilities. The rest of this tab documents the Agents API, the path for Grid platforms.

## What an agent can do

![](https://agents-docs.lightspark.com/images/icons/arrow-inbox.svg)

Add money and get paid

Receive stablecoins, Lightning payments and bank transfers from anyone into the customer's account details, and pull from the customer's own bank account with a recorded debit authorization or from their debit card.

![](https://agents-docs.lightspark.com/images/icons/paper-plane-top-right.svg)

Pay people

Pay someone by phone number or email even if they have no account, pay up to 50 people in one approved run, or send stablecoins, Lightning payments and payments directly to a bank account.

![](https://agents-docs.lightspark.com/images/icons/credit-card1.svg)

Buy online

Use its own virtual card, a single-use or recurring card for one merchant, or, with the customer's permission, one of the customer's saved cards.

![](https://agents-docs.lightspark.com/images/icons/coins.svg)

Split revenue automatically

Propose a standing rule that shares incoming payments with partners, collaborators or the customer's other accounts, active once the customer approves it.

## For businesses

A business customer can run its money through agents the same way an individual can, with controls built for a team:

* **Bank details to get paid.** Once verified, a business gets a US bank account and routing number: the `USD_ACCOUNT` entry in the `fundingPaymentInstructions` of its USD internal account. Anyone can pay it by ordinary bank transfer, such as a client or an employer.
* **Invoicing.** The [Lightspark connector](https://agents-docs.lightspark.com/agent-accounts/ai-app-connector.md) lets an agent send a client an invoice with its own payment page and matches the payment to the invoice. The Agents API has no invoice object; if you invoice from your own product, point payers at the bank details above.
* **An agent per person.** Each agent records which team member it acts for (`actingFor`), and that reference is copied onto every card it is issued.
* **Team budgets on one balance.** Put agents in a [spending pool](https://agents-docs.lightspark.com/agent-accounts/spending-limits.md) to cap what they spend together each week, each month or in total, and which kinds of payment they may make. Pools hold no money, so there is nothing to move between them.
* **Pay contractors and suppliers.** Pay someone by phone number or email with a [claimable payout](https://agents-docs.lightspark.com/agent-accounts/payments.md#pay-a-person-by-phone-or-email), one at a time or in a [payout run](https://agents-docs.lightspark.com/agent-accounts/payments.md#pay-many-people-at-once).
* **Share revenue.** [Settlement rules](https://agents-docs.lightspark.com/agent-accounts/payments.md#split-incoming-payments) split incoming payments by the shares the business approves.

## Key concepts

| Concept | What it is |
| - | - |
| **Customer** | The person or business whose money the agent spends. An agent belongs to exactly one customer and can only see and act on that customer's accounts. |
| **Agent** | A delegated actor with a name, a policy, and its own credential (`Agent:...`). Your backend creates it; the agent software connects by redeeming a one-time device code. |
| **Policy** | What the agent may do (permissions), how it executes (automatically or only with approval), how much it may spend (spending limits), which accounts it may use, and above what amount it must ask. |
| **Agent action** | Every money movement an agent asks for becomes an `AgentAction` (`AgentAction:...`). Grid executes it at once or holds it in `PENDING_APPROVAL` until your platform approves or rejects it. |
| **Spending pool** | A limit several of a customer's agents share, on top of each agent's own policy. A pool holds no money. |
| **Delegated key** | A Grid-custodied signing key the customer authorizes once, so Grid can sign the agent's approved sends from their Global Account without the customer signing each one. |
| **Cards** | Agents can be issued their own virtual cards, request single-use or recurring purchase cards, or use a card the customer already owns, which Grid stores encrypted so your platform never handles the card number. |

## Core capabilities

![](https://agents-docs.lightspark.com/images/icons/shield.svg)

Grid-enforced policy

Grid checks permissions, per-agent limits, shared team budgets and approval thresholds before any agent request runs, including card purchases.

![](https://agents-docs.lightspark.com/images/icons/receipt-check.svg)

Customer approvals

Requests over the threshold wait for the customer. Grid sends you the full request in a webhook so you can ask them in your own UI.

![](https://agents-docs.lightspark.com/images/icons/coins.svg)

Shared spending pools

Hold a customer's agents to one budget together, with its own payment types and approval threshold.

![](https://agents-docs.lightspark.com/images/icons/bell.svg)

Webhooks and audit

Every request and decision is an `AgentAction` you can list, and Grid sends a webhook at each step.

## How it fits with Global Accounts

An agent's sends and purchase cards are paid from the customer's [Global Account](https://agents-docs.lightspark.com/global-accounts.md), the self-custodial Embedded Wallet (`type: EMBEDDED_WALLET`) Grid provisions for them. Outbound payments from a Global Account normally need the customer's signature on every send. For an agent, the customer instead authorizes a delegated key for that agent and wallet once, and Grid signs only the sends its policy and the customer's approvals allow. The customer can pause the agent, revoke the key, or delete the agent at any time.

## Where to next

> [card] [Playground](https://agents-docs.lightspark.com/demo.md)
>
> Give an agent an account and watch the API calls behind each step.

> [card] [AI app connector](https://agents-docs.lightspark.com/agent-accounts/ai-app-connector.md)
>
> List Lightspark in your AI app so your users get an account inside your assistant.

> [card] [Agents API integration](https://agents-docs.lightspark.com/agent-accounts/implementation-overview.md)
>
> For Grid platforms: create an agent, connect it, fund the account, and handle approvals.

> [card] [Policies & permissions](https://agents-docs.lightspark.com/agent-accounts/policies-and-permissions.md)
>
> Decide what an agent may do, how much it may spend, and when it must ask.

> [card] [Approvals & audit](https://agents-docs.lightspark.com/agent-accounts/approvals-and-audit.md)
>
> Show approval requests to the customer and send their decision to Grid.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.