Back to Browse
Latitude 10 Agent Spend Guard
x402
Latitude 10 Agent Spend Guard is a paid API for AI agents from latitude10.tech, paid per call via x402, $39/call, status unknown (last checked 2026-10-11).
Delivers a TypeScript library and optional server that enforce per-payment caps, budgets, and approval flows so AI agents can make autonomous payments without overspending.
Price / call$39
Success—
StatusUnknown
How this service works
I help B2B software get onto the agent platforms: a fixed-price sprint that turns your API into a production MCP server and submits it to AWS Marketplace, the Claude directory, the official MCP Registry and the other directories where agents find tools.
Output
A downloadable TypeScript library kit (and optional server) containing spend enforcement middleware for x402, MPP, and L402 payment protocols. Includes per-payment caps, hourly/daily/monthly budget tracking with atomic reservation (SQLite/Postgres/memory), per-merchant and per-tool limits, human approval callbacks with Slack integration, velocity-based auto-freeze, a hash-chained audit log, a setup wizard, CLI, Docker/Fly.io configs, and an Agent Gateway paymaster. The kit is delivered as a signed, time-limited download URL.
Example use cases
Per-agent daily budget enforcement
“I want to set up my customer support agent so it can pay for third-party API calls on its own, but cap it at $20 per day and automatically freeze it if it hits the limit — can you get me the Agent Spend Guard library to set that up?”
Human approval gate for large payments
“My coding agent sometimes needs to buy compute or data, but I want any payment over $25 to pause and send me a Slack message for approval before it goes through — grab the Agent Spend Guard kit so I can wire that up.”
Multi-agent fleet spend governance
“I'm running a fleet of 10 research agents that each make x402 micropayments throughout the day — I need per-agent hourly budgets, a total fleet cap, and a hash-chained audit log I can reconcile later. Get me the Agent Spend Guard package for that.”
Technical details
Endpoint
GEThttps://latitude10.tech/api/agent-products/agent-spend-guard?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a production-ready, self-hostable spend control layer for AI agents making autonomous payments over x402, L402, or MPP protocols — especially when you need atomic budget reservations to prevent concurrent overspend, human-in-the-loop approval for large payments, or a tamper-evident audit log. Prefer this over rolling your own payment middleware when you need multi-protocol support (Base EVM, Solana, Lightning, Stripe via Shared Payment Tokens) and want server-mode key isolation so agent machines never hold signing keys.
Side effects
- Payment required (402) if the $39 USDC fee is not included in the request
- Expired download URL if contentExpiresAt has passed — must re-purchase
- Network mismatch if payment is sent on an unsupported EVM chain
- Invalid or malformed payment transaction hash causes delivery failure
- Download link is single-use or time-limited and cannot be reused after expiry
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| properties | string |
Output
Schema · Response
{
"type": "json",
"example": {
"payment": {
"network": "eip155:8453",
"transaction": "0x…"
},
"product": {
"name": "Latitude 10 Agent Spend Guard for Node.js",
"slug": "agent-spend-guard",
"content": "https://latitude10.tech/api/kit/download?t=…",
"version": "1.0.4",
"delivery": "kit",
"description": "For Node.js: let your agents pay for things without handing them your wallet: a TypeScript library and an optional server that sit in the payment path of x402 (Base and other EVM chains, Solana), MPP (Tempo, and Stripe cards via Shared Payment Tokens) and L402 (Lightning), over HTTP and MCP. Per-payment caps, hourly/daily/monthly budgets per agent and in total, per-merchant and per-tool limits, network, token and recipient lists; budgets reserved atomically before signing (memory, SQLite or Postgres), so concurrent payments never overspend; human approvals above a threshold (callback, or a queue with Slack links); a freeze switch and velocity auto-freeze; reconciliation of unknown outcomes from the chain; a hash-chained audit log. Server mode keeps keys off the agent’s machine (agents hold tokens). Local keys or your own KMS/MPC signer. Includes a setup wizard (node setup.mjs) with an overspend demo, a CLI, Docker and Fly.io files, and an Agent Gateway paymaster.",
"contentExpiresAt": "2026-10-02T12:00:00.000Z"
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"