# Delegated Spend Policy

> Delegated Spend Policy is a paid API for AI agents from phion.systems, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-20).

Enforces delegated spending mandates by failing closed on inactive mandates and blocking per-transaction or remaining-budget violations

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/delegated-spend-policy?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delegated-spend-policy-7517d041
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A9asdB2DFetKBbxHYHhEb

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability delegated-spend-policy-7517d041 -d '<json body>'
```

Example prompt: Before the agent spends $45 on my behalf, check that its delegated mandate is still active and that this transaction doesn't exceed its per-transaction limit or remaining budget — fail the whole thing if any rule is violated.

## When to prefer this

Choose this endpoint when an AI agent is operating under a delegated spend authority and you need a hard, fail-closed policy check before any payment executes. It is specifically designed for agentic payment contexts where mandate lifecycle (active vs. revoked), per-transaction caps, and cumulative budget limits must all be enforced in a single policy call. Prefer it over generic authorization checks when the spend is delegated (one agent acting for another principal) and you want an explicit denial with a machine-readable violation reason rather than a soft advisory signal.

## Known failure modes

- Mandate not found or unrecognizable — returns denial with unknown-mandate error
- Mandate is inactive or revoked — hard fail with inactive-mandate violation
- Transaction amount exceeds per-transaction limit — denial with per-transaction-violation reason
- Remaining budget insufficient for requested spend — denial with budget-exhausted reason
- Malformed or missing input fields — returns validation error
- Service unavailable — defaults to fail-closed denial to avoid unsafe fallthrough

## How this service works

Fail closed on inactive mandates and per-transaction or remaining-budget violations

## Output

A policy decision indicating whether the delegated spend is permitted or denied, including the specific violation reason if the mandate is inactive, the per-transaction limit is exceeded, or the remaining budget would be breached. The response fails closed — any policy violation results in an explicit denial rather than a default allow.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delegated-spend-policy-7517d041/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)