# CYRE Guardian Spend Policy Token

> CYRE Guardian Spend Policy Token is a paid API for AI agents from cyre.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Generates a signed policy token that seals max spend limits, allowed/denied hosts, networks, and a risk ceiling into a portable enforcement artifact for agent middleware.

## Facts

- Endpoint: GET https://cyre.dev/api/policy
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cyre-guardian-spend-policy-token-6816b2b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9Z-r7o1mhMO3j0gRxdpVE

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 cyre-guardian-spend-policy-token-6816b2b8
```

Example prompt: Create a signed CYRE Guardian spend policy for actor 0xAbc123 with a max spend of 5000000 atomic units, so my downstream middleware can enforce it.

## When to prefer this

Use this endpoint when you need a portable, signed enforcement artifact that downstream middleware or agent orchestrators can consume to gate payments — specifically when you want to encode spend ceilings, host patterns, and risk ceilings into a single token rather than enforcing rules ad hoc in your agent logic. Prefer this over runtime risk checks when you want pre-committed, tamper-evident spend policies that travel with the agent context.

## Known failure modes

- Missing required 'actor' query parameter returns an error
- Invalid or unrecognized actor address format causes rejection
- Payment of 0.002 USDC not received results in HTTP 402 and no token issued
- Malformed maxSpendAtomic value (non-numeric string) may cause parsing error
- Network timeout or service unavailability returns 5xx error

## How this service works

Guardian Spend Policy — seal max spend, allow/deny hosts, networks, and risk ceiling into a signed policy token other agent middleware can enforce. Patterns, not verdicts. Agent guide: https://cyre.dev/SKILL.md

## Output

A signed policy token encoding the actor's max spend (in atomic units), host allow/deny patterns, permitted networks, and risk ceiling. This token is consumed by downstream agent middleware as an enforcement artifact — it carries patterns, not verdicts, so middleware makes the final call.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "actor"
     ],
     "properties": {
      "actor": {
       "type": "string"
      },
      "maxSpendAtomic": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cyre-guardian-spend-policy-token-6816b2b8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cyre.dev](https://www.zero.xyz/host/cyre.dev/llms.txt)