Screwtape.ai
https://screwtape.ai/a2aIs this seller safe to pay? POST /v1/payment-check ($0.005) returns allow, review or block with reasons and a signed receipt, checked at the moment the agent pays. Screwtape.ai decides whether an AI agent is allowed to spend money, and keeps the proof. Before an agent pays an invoice or payment instruction, it sends it to Screwtape.ai first. POST /v1/duplicate (MCP tool check_duplicate_invoice) checks it against the invoices already recorded (unique, duplicate, possible_duplicate or replay), runs the rules you pass as checks (line items that must add up to the total, an expected amount, equals, regex, JSON schema, required fields) and judges it against your evidence, such as the purchase order. The answer is pass, fail, or retry with reasons, plus an Ed25519-signed verdict receipt anyone can check at POST /v1/receipts/verify. Pay only on pass. POST /v1/judge gives the same verdict on any agent output. POST /v1/consensus flags false consensus when several agents agree. POST /v1/budget tracks spend against a cap across a run ($0.002). POST /v1/receipt issues a signed action receipt ($0.003); send children (prior receipt ids) to close a whole run so any added, dropped or swapped step fails verification. Verify action receipts for free at GET /v1/receipt/verify or on /verify/. The receipt format is at /spec/receipts/. Framework guides are at /guides/ (CrewAI, LangGraph, AgentKit, OpenAI Agents). 3 free calls per UTC day with no key, or 10 with a free key from POST /v1/signup. A second check, outside your agent. Screwtape advises and records, does not hold funds, and relies on the agent to cooperate. Screwtape runs as a separate service from your agent, with its own prompt and checks, and it is not paid more when your agent passes. Every verdict comes with a signed receipt you can verify yourself. The receipt proves what was checked, when, and the verdict that was returned. REST/MCP products: Budget Ledger ($0.002), Action Receipts ($0.003, including whole-run receipts via children), Payment check ($0.005), 3 free calls per UTC day without a key plus 10/day with a free key, shared across HTTP/MCP (anonymous 3/minute and global 2000/day; private daily IP hash). Verify action receipts for free at GET https://screwtape.ai/v1/receipt/verify or https://screwtape.ai/verify/. Verdict receipts: POST https://screwtape.ai/v1/receipts/verify. Receipt format: https://screwtape.ai/spec/receipts/. Framework guides: https://screwtape.ai/guides/ (CrewAI, LangGraph, AgentKit, OpenAI Agents). Skills: payment_check, check_duplicate_invoice, judge, consensus, budget_ledger, action_receipt, get_api_key (free key, 10 calls per UTC day, proof of work), publish_receipt. A2A JSON-RPC message/send at https://screwtape.ai/a2a maps to judge (send a duplicate object in the data part to check an invoice). The same skills are on MCP (https://screwtape.ai/mcp) and REST (https://screwtape.ai/openapi.json). After the anonymous allowance, unpaid calls return x402 payment requirements ($0.005 USDC per call on Base or Solana, or the product price for budget, receipt and payment-check). After the 3/day anonymous allowance, a skill call needs either a Bearer API key (free: POST https://screwtape.ai/v1/signup, 10 calls per UTC day) or an x402 payment (scheme exact, amount 5000 = $0.005 USDC on Base eip155:8453 or Solana). A call with neither after anonymous access is exhausted returns HTTP 402 with the x402 requirements.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 24ms · p95 26msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 11/11/2026, 12:00:00 AM | 100% | 1 | 23ms |
| 11/13/2026, 12:00:00 AM | 100% | 2 | 24ms |
| 11/16/2026, 12:00:00 AM | 100% | 1 | 26ms |
| 11/18/2026, 12:00:00 AM | 100% | 1 | 10ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 61
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 10% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- —
- Networks
- —
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Cloudflare, Inc
- Domain registered
- 2026-07-11
- Hosting network
- CLOUDFLARENET
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
Response schema
{
"type": "object"
}