sweetai-agent-firewall
v0.1.5
Published
Pre-transaction trust firewall for AI agents: should-i-pay decisions, sybil forensics, liveness SLA (SweetAI x402 / ERC-8004). $0.01 per decision via x402 USDC.
Maintainers
Readme
sweetai-agent-firewall
Pre-transaction trust firewall for AI agents. Before your agent sends USDC to another agent, get PAY / CAUTION / SKIP plus expected_loss_usd. One decision costs 0.01 USDC through x402; no API key or subscription.
Complete 402 → settle → retry → PAY flow
import { SweetAIFirewall } from "sweetai-agent-firewall";
const fw = new SweetAIFirewall();
// Use the target you actually have: agentId, solanaAsset, sellerUrl or payTo.
const request = { agentId: 2290, amountUsd: 25 };
// const request = { sellerUrl: "https://api.example.com/x402", amountUsd: 0.05 };
// const request = { payTo: "0x...", amountUsd: 0.05 };
// 1. The unpaid first call must return payment requirements.
const first = await fw.shouldIPay(request);
if (!first.paymentRequired) {
throw new Error("Expected x402 payment requirements; transfer blocked");
}
// 2. HOST-SPECIFIC HOOK: settle first.raw with your own x402 wallet/client.
// This function is supplied by the host application, not by this SDK.
// It must return the exact X-PAYMENT value for the retry.
const paymentHeader = await settleWithHostWallet(first.raw);
// 3. Retry with X-PAYMENT. Only a settled PAY verdict resolves.
// CAUTION, SKIP, unpaid 402, HTTP errors and malformed responses reject.
const decision = await fw.approveTransfer({ ...request, paymentHeader });
// 4. Only here may the host application send USDC to the target agent.
console.log(decision.action, decision.confidence, decision.expectedLossUsd);The SDK never asks for private keys and never settles either the SweetAI check or the target transfer. settleWithHostWallet is intentionally host-specific: use your existing x402 payer, such as AgentKit or another wallet-owning agent runtime.
For a lower-level integration, pass the same value directly to shouldIPay({ ...request, paymentHeader }). The paymentHeader argument was added in 0.1.5; earlier releases could read the initial 402 but silently ignored the retry header.
Decision fields
action:PAYafterapproveTransfersucceedsconfidence:0.0–1.0expectedLossUsd: expected loss sized to your transfer amountraw: complete paid response
For sellerUrl / payTo, the verdict uses Bazaar demand (payers, calls,
calls/payer, trend). wallet_flow.status=not_available means demand data does
not see seller→payer round trips.
Payments use USDC on Base, Polygon, Arbitrum or Solana. Utility methods status() and pricing() read current service status and server-side prices.
Docs: https://sweetai.tiamatcrypto.com/llms.txt · Manifest: https://sweetai.tiamatcrypto.com/.well-known/x402
