GatePay
GatePay is ScriptMasterLabs’ policy-first firewall between an autonomous agent and a machine payment, separating permission, decision intelligence, authorization, settlement, and proof so a model cannot talk itself into spending money. Hard policy executes before model intelligence; signed single-use mandates bind each decision; a hash-chained SQLite ledger records proof. Real money movement stays intentionally disabled pending paid-path verification.
A policy-first firewall between an autonomous agent and a machine payment. GatePay separates permission, decision intelligence, authorization, settlement, and proof so a model cannot simply talk itself into spending money.
What does GatePay control?
GatePay controls hard policy, signed mandates, strict x402 v2 settlement, a proof ledger, shadow policy, and standalone orchestration of SML services.
Budget ceilings, rail rules, target/tool allowlists, velocity controls and approval thresholds execute before model intelligence.
Short-lived authorization binds the decision to payload hash, amount, target, rail, policy result, expiry and nonce.
Fresh terms, Base USDC exact/EIP-3009 support, no blind retries, redirect/SSRF protection, and PAYMENT-RESPONSE settlement evidence requirements.
Decision, authorization, settlement state and outcome events are stored in a durable hash-chained SQLite ledger on Render persistent storage.
Test what a new rule would have blocked or escalated without moving money.
GatePay can orchestrate SML services through clean interfaces. It does not merge SqueezeOS, Provider Trust, GhostKey, LIVEWIRE or Decision Core into one codebase.
What are GatePay’s production surfaces?
Production surfaces include the runtime status endpoint, agent-discovery JSON files, the machine guide, the GitLab source, and the canonical product record.
Runtime: gatepay.onrender.com/v1/status
Agent discovery: /.well-known/agent.json · /.well-known/agent-card.json
Machine guide: gatepay.onrender.com/llms.txt
Source: GitLab / timothy.walton45/gatepay
Canonical product record: /.well-known/gatepay-product.json
GatePay's production runtime, deterministic policy, signed mandates, shadow simulation and durable proof ledger are live and runtime-verified. Real x402/Arc money movement remains intentionally disabled while paid-path verification is completed. A mock receipt is not settlement. A PAYMENT-SIGNATURE is authorization, not settlement. Settlement is not accepted delivery. Jev is not claimed as live-verified until a real TypeSafe decision is observed.
Why does GatePay exist?
Payment protocols answer how value moves. Wallets answer who can sign. GatePay answers the missing question: should this autonomous action be permitted to become a payment at all, under this exact policy and evidence state?
Truth First. Proof Always. Pay Only for Accepted Delivery. — ScriptMasterLabs