# SafeAgent Execution Guard — Claim Endpoint

> SafeAgent Execution Guard — Claim Endpoint is a paid API for AI agents from safeagent-production.up.railway.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Issues an exactly-once execution claim for an AI agent before it performs an action, preventing duplicate or concurrent executions.

## Facts

- Endpoint: POST https://safeagent-production.up.railway.app/claim
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/safeagent-execution-guard-claim-endpoint-2d10c9d6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OYn06YrH3ZyV2M0-dfBcs

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 safeagent-execution-guard-claim-endpoint-2d10c9d6 -d '<json body>'
```

Example prompt: Before my AI agent executes the next task, use SafeAgent's execution guard to claim a lock for agent 0x2Dc36fb02357aDa6E210Cb4b0EA783EA5153EAa8 on request ID evt-abc123 so it doesn't run more than once.

## When to prefer this

Use this endpoint when you need exactly-once execution guarantees for AI agent actions — especially in distributed or multi-agent environments where the same task could be triggered more than once. Prefer this over ad-hoc deduplication logic when the cost of a duplicate action (e.g. double payment, duplicate message) is high.

## Known failure modes

- Claim already exists for this request_id — agent should halt and not duplicate execution
- Missing or invalid agent_id — returns error rejecting the claim
- Payment failure (x402) — insufficient USDC balance blocks the claim
- Network timeout — agent should retry with caution to avoid double-claiming
- Invalid request_id format — claim rejected with validation error

## How this service works

Execution Guard for AI Agents — exactly-once claim before execute.

## Output

Returns a JSON object with a status field (e.g. 'PROCEED'), the agent_id that claimed the execution, and a request_id confirming the unique claim. If the claim is already taken, the agent should not proceed.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "status",
      "request_id"
     ],
     "properties": {
      "status": {
       "type": "string"
      },
      "agent_id": {
       "type": "string"
      },
      "request_id": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "PROCEED",
  "agent_id": "0x2Dc36fb02357aDa6E210Cb4b0EA783EA5153EAa8",
  "request_id": "evt-abc123"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/safeagent-execution-guard-claim-endpoint-2d10c9d6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from safeagent-production.up.railway.app](https://www.zero.xyz/host/safeagent-production.up.railway.app/llms.txt)