Request access

Payment agents that spend only what your company approved.

Employees request an agent for a defined job. It starts with an empty wallet. Funding is a separate request under your TOFA, with an amount and a period. When either runs out, the agent stops and the need comes back for review.

Request accessTest payments against a scope
Growth research agentApproved
Remaining of approved budget476.40 USDC
720.00 of 1,196.40 used · 23 days left
PurposeResearch tools
OwnerGrowth team
Payment patternRecurring, monthly
Period60 days
CardConnected
EntityRampi Labs FZ-LLC
Sample agent. When an agent is shared, each payment still records the employee who started it.

From request to retirement, in seven steps.

Request and create

An employee describes the agent's task, whether it serves a department or one person, and who is responsible. Only after the purpose is approved does Rampi create the profile and its separate empty wallet. Creation gives no funds and no ability to spend.

Who actsEmployee requests; a user with creation approval reviews the purpose
RecordedTask, owner, department or employee, intended users
Event nameagent.created

Three ways to fund an agent. The requester never chooses one.

A user your company authorised to move funds picks the source and route for each approved request. Route, conversion, fees and timing are shown before anything is committed.

SourceCompany bank accountConnected banking source
ConvertOn-ramp to stablecoinRate, fees and timing shown first
DestinationAgent walletApproved amount only

The on-ramp converts the approved bank funds through connected services, then delivers the stablecoin to the agent wallet.

Try a scope and watch which payments it allows.

Set the scope on the left. The payments on the right are checked against it in order, and the remaining budget falls as each one is approved.

Budget type
For a known purchase. The amount and period are set up front.
Approved amount
Allowed categories
Blocked merchants
Attempted paymentResult
Fieldnote ResearchMonthly plan · SoftwareWithin scope. Recorded with the initiating employee.
36.00 USDCApproved
Model API usage, SeptemberUsage-based · AI model usageWithin scope. Recorded with the initiating employee.
240.00 USDCApproved
Lumen MarketplaceReseller · SoftwareMerchant is blocked for this agent.
90.00 USDCBlocked
Harbor AirFlight · TravelCategory is outside this agent's scope: travel.
410.00 USDCBlocked
DatawellDataset licence · DataWithin scope. Recorded with the initiating employee.
520.00 USDCApproved
Model API usage, OctoberUsage-based · AI model usageWithin scope. Recorded with the initiating employee.
380.00 USDCApproved
Remaining after checks24.00 USDC

A second opinion before a tool gets funded.

If your company turns it on, a research agent reviews the requested tool: what it does, the stated need, plans, prices, trials and alternatives. It may suggest a short monthly start before an annual plan, or the reverse when usage justifies it.

It advises. A negative recommendation does not block the request. Your approvers can proceed, choose another option, ask for clarification or reject.

Research noteAdvisory
RequestedFieldnote Research, annual plan · 360.00 USDC
Stated needInterview synthesis for one 8-week study
Suggests the monthly plan for two monthsTwo months at 36.00 is 72.00 USDC against 360.00 for the year. A 14-day trial is available first. If the study repeats, the annual plan is cheaper from month 11.
Sample note. Tool name and prices are illustrative.

Authority comes from what your company grants, not from job titles.

One person can hold several of these permissions if your company decides so. Employees who only request agents never see company balances or funding sources.

Company admin and finance usersConfigure entities, funding sources, authority settings, departments, Chart of Accounts and workspace access.
Departments and employeesGet a simpler interface to request and use agents. They state the purpose and ask for funding when needed.
Authorised funding usersReview requests, choose the funding source and route, and release funds under the permissions granted.
Payment agentsAct only within the capability, period and spending conditions given to them. They can be temporary or shared.
Connected providersHold funds and execute cards, wallet transactions, swaps, conversions and transfers where supported.

Each agent has its own wallet. Cards connect to it where supported.

Virtual cards, agent wallets, stablecoin payments and swaps all exist elsewhere. What Rampi adds is how they work together for your employees and your finance team.

One wallet per agentEvery payment agent has its own separately controlled wallet, which is part of its spending boundary.
Cards draw on the walletWhere a connected card arrangement supports it, the agent's approved stablecoin balance funds card spending. The balance alone does not issue a card.
No reach across agentsAn agent cannot grant itself more funding, widen its own permissions or reach another agent's budget.
Limits hold at the provider tooControls are enforced in Rampi's workflow and with the wallet or card partner. They reduce exposure if an agent is compromised; they cannot promise zero loss.

Start with one department and one agent.

Set your approval rule, connect a funding source, and let the first request come back for review when its period ends.

Request access