Arbor
AgentPay is the authorization layer between an AI agent and real spending. You define the rules — spending caps, allowed merchants, time windows — and every purchase attempt the agent makes is checked against them in real time. Approved transactions go through. Anything outside the mandate is blocked and logged. No more babysitting every agent action. No more runaway charges.
README
Arbor
Give your AI agent a wallet with rules it can't break.
Arbor is the authorization layer between an AI agent and real spending. Install it into any MCP-compatible agent, define your rules once — spending caps, approved merchants, time windows — and every purchase the agent attempts is checked against them in real time. Approved transactions go through. Anything outside the mandate is blocked, logged, and surfaced to you.
Your agent runs autonomously. You stay in control.
How It Works
You install Arbor into your agent
↓
You set a spending mandate once
↓
Agent runs autonomously
↓
Before every purchase attempt:
agent calls authorize_purchase
↓ ↓
✅ Approved ❌ Denied
Agent proceeds Agent stops,
reports to you
Arbor sits between your agent's intent and the actual transaction — it doesn't move money itself, it decides whether the agent is allowed to.
Install Into Your Agent
First, grab your API key from agent-payment-eight.vercel.app.
Then pick your agent:
Hermes or OpenClaw (natural language)
Just paste this into your agent's chat — no CLI needed:
Install the AgentPay MCP server. My API key is <your-api-key>.
Your agent will handle the rest automatically.
Claude / Cursor / Windsurf (Smithery)
npx @smithery/cli install advaitgore/payguard --client claude
When prompted, paste your API key.
Any MCP-compatible agent (manual config)
{
"mcpServers": {
"agentpay": {
"url": "https://agentpayment-production.up.railway.app/mcp",
"headers": {
"Authorization": "Bearer <your-api-key>"
}
}
}
}
Once installed, tell your agent to set up a mandate:
"Set my spending limit to $50 per transaction. Approved merchants: Amazon, Vercel, GitHub."
That's it. Your agent now has spending rules it evaluates autonomously before every purchase.
Real-World Examples
Personal assistant agent
"You have $50 tonight. Uber and DoorDash only. Go."
{
"daily_limit": 50,
"allowed_merchants": ["uber.com", "doordash.com", "ubereats.com"]
}
Autonomous research agent
"$20 per run. API providers only."
{
"max_per_transaction": 20,
"allowed_merchants": ["openai.com", "serpapi.com", "anthropic.com"]
}
Company expense agent
"$500/week. Approved SaaS vendors only."
{
"weekly_limit": 500,
"allowed_merchants": ["notion.so", "vercel.com", "github.com", "figma.com"]
}
How the Agent Uses It
Once installed, your agent calls authorize_purchase before any spend:
{
"merchant": "openai.com",
"amount": 10.00,
"currency": "USD",
"description": "API credits for task execution"
}
Approved — within mandate:
{
"status": "approved",
"transaction_id": "txn_01j9k2m...",
"amount": 10.00,
"merchant": "openai.com",
"remaining_budget": 40.00,
"message": "Purchase approved within mandate limits"
}
Denied — merchant not on allowlist:
{
"status": "denied",
"reason": "merchant_not_allowed",
"message": "openai.com is not on the approved merchant list for this agent"
}
What the agent should do:
approved→ proceed.denied→ stop and surface thereasonto the user. Never retry without updated mandate permissions.
Available Tools
| Tool | What it does |
|---|---|
authorize_purchase |
Check a purchase against the agent's mandate — the core call |
get_mandate |
View current spending rules for this agent |
update_mandate |
Change limits or allowed merchants |
get_spending_summary |
Total spend by category and merchant |
get_audit_log |
Full history of every authorize/deny decision |
rotate_agent_key |
Rotate the agent's API key |
create_account |
Create a new user account + org |
create_agent |
Provision a new agent under an org |
create_mandate |
Set spending rules for a newly created agent |
REST API
Interactive docs: https://agentpayment-production.up.railway.app/docs
Self-Hosting
git clone https://github.com/advaitgore/agent_payment
cd agent_payment
pip install -r apps/api/requirements.txt
uvicorn apps.api.main:app --host 0.0.0.0 --port 8080
Required env vars:
DATABASE_URL=postgresql://...
JWT_SECRET=...
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.