API Credits & Cloud Spend Agents
Let agents buy API credits, cloud add-ons, and developer services with isolated spend and intent-linked audit trails.
The Problem
Infrastructure spend is fragmented: API credits, hosting add-ons, domains, and SaaS upgrades. Teams often share a corporate card, which creates reconciliation pain and a huge blast radius if an agent misbehaves.
The Solution
Issue dedicated cards per vendor or workflow, require purchase intents, and enforce velocity caps to prevent retry-loop overspend. Store evidence logs so every charge is explainable.
Key Features
Vendor-locked cards
Lock a card to a specific merchant (e.g., OpenAI, AWS, Vercel). The card won’t work elsewhere.
Intent-based approvals
Agents declare purpose + expected amount. Policies auto-approve small purchases and escalate larger ones.
Velocity caps
Stop retry loops and duplicate charges with rate limits per merchant and per card.
Evidence logs
Link every transaction to an intentId and store receipts/metadata for reconciliation.
How It Works
Agent declares intent
Agent requests purchase of credits/add-ons with an expected amount and merchant.
Policy evaluates
System checks approval thresholds, merchant locks, and velocity constraints.
Card unlock window
A dedicated card is issued/unlocked for the billing window or one-time checkout.
Verify + log
Transaction is verified against intent and stored as an evidence record.
Code Example
// Create a vendor-locked card for API credits
const card = await signets.cards.create({
agent_id: "infra-agent",
spending_limit: 5000, // $50.00
merchant_lock: "openai.com",
recurring: false,
});
// Purchase intent + verification flow
const intent = await signets.intents.create({
purpose: "Buy $20 of API credits",
expectedAmount: 2000,
expectedMerchant: "openai.com",
});
// After checkout:
const txns = await signets.transactions.list_for_card({ cardId: card.id });Ready to get started?
Issue your first card and start building.