Skip to main content
The Agents API must be enabled for your platform; until it is, agent endpoints answer 403. To enable it, book a demo 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

Add Lightspark to your AI app

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.

Add agents to your Grid platform

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

​
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 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 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, one at a time or in a payout run.
  • Share revenue. Settlement rules split incoming payments by the shares the business approves.

​
Key concepts

​
Core capabilities

​
How it fits with Global Accounts

An agent’s sends and purchase cards are paid from the customer’s Global Account, 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

Playground

Give an agent an account and watch the API calls behind each step.

AI app connector

List Lightspark in your AI app so your users get an account inside your assistant.

Agents API integration

For Grid platforms: create an agent, connect it, fund the account, and handle approvals.

Policies & permissions

Decide what an agent may do, how much it may spend, and when it must ask.

Approvals & audit

Show approval requests to the customer and send their decision to Grid.