# Synthex Forge Containment Register

> Synthex Forge Containment Register is a paid API for AI agents from x402.synthexforge.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-23).

Registers a signed containment policy and governance rules for an agent DID, including emergency contact, via a paid x402 endpoint on Base mainnet.

## Facts

- Endpoint: POST https://x402.synthexforge.com/v1/containment/register?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthex-forge-containment-register-e8d394b0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pje4vU4ZFVqgKeTQwROYy

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 synthex-forge-containment-register-e8d394b0 -d '<json body>'
```

Example prompt: Register a containment policy for agent DID did:example:agent123 with a notify rule on channel 'ops-alert' and throttle rule targeting did:example:target456, signed with my Ed25519 keys, and set did:example:emergency789 as the emergency contact.

## When to prefer this

Use this endpoint when you need to register cryptographically-attested containment policies and governance rules for an AI agent identified by a DID, particularly in contexts requiring Ed25519-signed artifacts and on-chain payment attestation via x402 on Base mainnet. Prefer this over generic policy storage when auditability, signed rule provenance, and DID-based agent identity are required.

## Known failure modes

- Invalid or malformed agent DID returns a 4xx validation error
- Missing or invalid Ed25519 rule signatures cause rejection
- Payment not provided or insufficient USDC results in HTTP 402 payment-required response
- Malformed rules array (missing required condition or action fields) causes a schema validation error
- Emergency contact DID not in valid DID format returns an error

## How this service works

Synthex Forge x402 Receive: 41 paid verification, attestation and governance endpoints (Ed25519 + SHA-256 signed artifacts) plus free verify/public-key/standard sibling routes. Paid routes answer HTTP 402 with an x402 v2 `payment-required` envelope (atomic USDC on Base mainnet, chain ID 8453). Free routes are declared with `security: []` per the x402scan discovery spec.

## Output

Returns a JSON object with an 'ok' boolean confirming that the containment policy and governance rules were successfully registered for the specified agent DID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rules": {
   "type": "array",
   "items": {
    "type": "object"
   },
   "description": "Signed rules: [{id?, condition, action:{type: notify|throttle, channel?, target?, detail?}}]"
  },
  "policy": {
   "type": [
    "object",
    "string",
    "null"
   ],
   "description": "Declared containment policy: {name?, version?, summary?, rules_ref?} or a summary string."
  },
  "agent_did": {
   "type": "string",
   "description": "The agent/custodian DID being covered (must be a DID)."
  },
  "rule_signatures": {
   "type": "object",
   "description": "Registrant Ed25519 signatures over each rule's canonical bytes: {rule_id: hex}."
  },
  "emergency_contact_did": {
   "type": "string",
   "description": "Emergency-contact DID to reach (must be a DID)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthex-forge-containment-register-e8d394b0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.synthexforge.com](https://www.zero.xyz/host/x402.synthexforge.com/llms.txt)