Guide
Screwtape.ai 1.7: payment guard, spend books, trust score
18 November 2026
release · payment-guard · spend-books · trust-score · ai-agents
Written by the Screwtape.ai team. Every detail below matches the live API on 18 November 2026. The full reference is in the docs and the API spec.
Screwtape.ai 1.7 adds three tools for AI agents that spend money: Payment Guard, which enforces your spend rules before an agent pays; spend books, which turn what your agents spent into bookkeeping rows; and the trust score, which helps sellers decide whether to accept a payment from an agent. All three are live now, priced per call, with no monthly plan.
Payment Guard: your rules, enforced before the agent pays
Until now, Screwtape.ai advised: it told your agent allow, review or block, and your code had to honor the answer. Payment Guard adds enforcement.
- Set your rules once with
PUT /v1/payment-guard/rules. You can set a limit per payment, a daily budget, a budget for a rolling period, the sellers and sites the agent may pay, and how many payments it may attempt per minute or per hour. Rules belong to an API key. An account can also set a default that its keys inherit, and a key's own rules win. Setting and reading rules is free. - Ask before each payment with
POST /v1/payment-guard/authorize. Send the payment id, the agent, the amount and the seller. If the payment fits your rules, you get allow and a short-lived signed clearance, and the amount is held against your budgets. If it does not fit, you get block with the reasons, and nothing is held. - Or let Screwtape.ai pass it on.
POST /v1/payment-guard/proxyruns the same check and, only on allow, forwards the payment your own client already signed to the seller, once per payment id. If the seller can't be reached, the held budget and the call are given back.
Budgets are held with atomic database updates, so several payments arriving at the same moment can't push an agent past its limits. Asking again with the same payment id and body returns the same decision without charging again, and a payment id is never forwarded twice.
Screwtape.ai never holds funds and never accepts private keys or recovery phrases. Your own client signs every payment. The clearance is a record of the decision, not a way to pay.
Price: each authorize or proxy call uses one call from your free daily allowance or the standard per-call price shown on the pricing page. It needs an API key. In MCP, the tool is payment_guard_authorize.
Spend books: what your agents spent, ready for your accountant
GET /v1/spend-books/export exports what an API key spent on Screwtape.ai calls as bookkeeping rows, grouped by agent, seller, day and product.
format=quickbooksorformat=xeroreturns a CSV file ready to import.format=jsonreturns the groups, the totals and a reconciliation.- Every line shows the seller and the amount that was actually charged, not a list price.
- If an older call has no stored amount, it is marked amount unknown instead of guessed.
- Agents that pay per call without an API key are recorded too, under a private, scrambled payer id, never the raw payment address.
Price: free, up to 30 exports per minute. It needs an API key, and a date range can cover up to 92 days.
Trust score: for sellers deciding whether to accept an agent's payment
The first two tools protect the agent's owner. The trust score protects the seller. POST /v1/trust-score answers one question: does this paying agent look risky?
- Send who is paying (a payer, agent or caller id) and, optionally, the counts you've seen yourself: successful, failed and refused payments, open disputes, and how long you've known the agent.
- You get a score from 0 to 1, a risk level, allow, review or block, and the reasons.
- The score draws on activity reported across the Screwtape.ai seller network, so a seller can see patterns that no single seller could see alone. Signals are counted per day.
- Only scrambled ids and daily counts are stored. Raw network addresses, payment addresses and keys are never stored.
- Reports from sellers who pay for calls weigh more than reports from free keys, and each reporter's influence is capped, which makes it hard to drag a score down with fake reports.
Price: the standard per-call price shown on the pricing page, with the same free daily allowance as the other tools. In MCP, the tool is trust_score.
What it does not do
- Payment Guard enforces your rules only for payments that go through it. If an agent pays some other way, Payment Guard never sees it.
- The trust score partly relies on what sellers report. Weighting and caps limit abuse, but a group of colluding accounts could still move a score a little. Treat review as a prompt to look closer, not a verdict.
- Spend books cover calls made to Screwtape.ai. They are not a full ledger of everything your agents buy.
Try it
- Add the MCP server
https://screwtape.ai/mcpto your agent, or call the HTTP API in the docs. - Get a free API key. It covers 10 calls a day, shared across the tools.
- Set your Payment Guard rules, then authorize your next agent payment.
Questions or feedback: support@screwtape.ai.
