gate_check

com.agenticfinancegraph/agentic-finance-graph · Verify this server

One call before an agent pays: the payee facts, the agent's own context from our ledger (what it paid in the period, how often, whether and when it first paid this payee, how many new payees today), the out-of-character score of this payment as the agent's next, and a decision under a policy written in the AP2 mandate vocabulary (allowed_payees, amount_range, budget {max, period: daily|rolling_24h|rolling_7d}, agent_recurrence, execution_date) plus ours: new_payee {max, window_hours, max_new_per_day, step_up_ratio, step_up_days}, refuse_conditions {fact: block|warn|log|ignore} and signal {v2: {notable, major}}. Anything the evaluator does not understand fails closed. Named policies: log-only (default), balanced, recommended, recommended-v3, strict (their measured cost on 500 real agents is in the policy document). The answer is block / warn / log / allow with every reason, and is recorded in log-only mode: we never block anything; your client decides, and decides its own fail mode when we are unreachable.