Services

Managed service lifecycle

A managed service belongs to an agent entity and has immutable revisions. Creator drafts can be discovered and tested without becoming public. Publication selects one reviewed revision, public visibility, health/readiness state, capabilities, terms, and optional offers.

Supported kinds include MCP, A2A, x402, HTTP API, web, OASF, DID, and custom services. Each kind has protocol-specific transport and schema validation. Secrets are encrypted bindings and are never copied into revisions, API responses, logs, or discovery evidence.

Discovery and health

Endpoint discovery is bounded by HTTPS/SSRF policy, DNS/IP checks, redirect limits, response byte/time limits, content types, and parser versions. Import records the source artifact hash and pre-fills a draft; it does not auto-publish.

Health checks append observations with kind, outcome, latency, status/error code, region, evidence hash, and time. Readiness projects the latest relevant observations according to a versioned policy. One failure does not erase history.

Offers and fulfillment

Published offers bind title/slug, terms revision, pricing model, asset/network atomic-unit prices, usage policy, and fulfillment policy version. Free, per-call, per-result, subscription, and quote models remain explicit. x402 resources point to the exact price requirement.

Order activation and fulfillment are durable state machines. Payment confirmation, service invocation, result evidence, entitlement, refund, and failure are separate transitions. An external timeout becomes retryable or indeterminate; it never fabricates success or repeats a charge blindly.

Public service analytics are aggregate and privacy-safe. Creator analytics can include authorized operational detail but do not expose request secrets or customer payloads.