Request API access

Agents, wallets and cards with limits checked on every payment.

An agent is a scoped object: a purpose, an owner, a wallet and spend conditions. It cannot raise its own budget, widen its permissions or reach another agent's funds. Every attempt is checked and recorded.

Request API accessTest payments against a scope
agt_growth_researchApproved
{
  "id": "agt_growth_research",
  "purpose": "research_tools",
  "owner": "team_growth",
  "entity": "rampi_labs_ae",
  "wallet": {
    "asset": "USDC",
    "approved": "1196.40",
    "used": "720.00",
    "remaining": "476.40"
  },
  "scope": {
    "period_days": 60,
    "days_left": 23,
    "pattern": "recurring_monthly",
    "categories": [
      "software",
      "ai_model_usage",
      "data"
    ]
  },
  "card": {
    "status": "connected",
    "funded_from": "wallet"
  },
  "controls": {
    "self_fund": false,
    "widen_permissions": false,
    "cross_agent_access": false
  }
}
Sample agent. When an agent is shared, each payment still records the employee who started it.

Seven states, each with its own event.

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
Eventagent.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.

Every payment attempt returns a result and a reason.

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 · Softwarereason: approved
36.00 USDCApproved
Model API usage, SeptemberUsage-based · AI model usagereason: approved
240.00 USDCApproved
Lumen MarketplaceReseller · Softwarereason: merchant_blocked
90.00 USDCBlocked
Harbor AirFlight · Travelreason: category_not_allowed
410.00 USDCBlocked
DatawellDataset licence · Datareason: approved
520.00 USDCApproved
Model API usage, OctoberUsage-based · AI model usagereason: approved
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.

role: adminCompany admin and finance usersConfigure entities, funding sources, authority settings, departments, Chart of Accounts and workspace access.
role: requesterDepartments and employeesGet a simpler interface to request and use agents. They state the purpose and ask for funding when needed.
role: funderAuthorised funding usersReview requests, choose the funding source and route, and release funds under the permissions granted.
role: agentPayment agentsAct only within the capability, period and spending conditions given to them. They can be temporary or shared.
role: providerConnected 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.

Create a test agent and push payments at its limits.

Scopes, results and reasons behave the same in testing as they will with real funds.

Request API access