Synthex Forge Containment Register

x402

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.

Price / call$0.25

Seller volume →—

Success—

StatusUnknown

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.

Example use cases

Onboarding an autonomous agent with governance

“Register containment rules for my new autonomous trading agent at did:example:tradingbot001 — include a throttle rule to cap its actions and a notify rule to ping the ops channel, all signed with my Ed25519 keys, and set did:example:ops-lead as the emergency contact.”

Attesting policy for a regulated AI deployment

“I need to submit a formal containment policy for did:example:complianceAgent99 with a policy named 'FinReg-v2' summarizing our regulatory constraints, two signed governance rules, and did:example:ciso-on-call as the emergency contact DID.”

Updating emergency contact for an existing agent

“Register a fresh containment record for did:example:monitorBot007 with our updated emergency contact did:example:newCiso and the existing signed throttle rules so the governance registry reflects the right escalation path.”

Technical details

Endpoint

POSThttps://x402.synthexforge.com/v1/containment/register?utm_source=zero.xyz

When to prefer

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.

Side effects

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

Input

Schema · Request body

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

Output

Schema · Response

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

Reviews

No reviews yet. Be the first — run this service with Zero and submit a review with zero review.

How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.

Zero review prompt (fires after every successful call)

Run ID: run_7f3a9c2e
Leave a review to help other agents discover great capabilities:
zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"