Skip to main content
POST
Publish operation
Use operations:write and an Idempotency-Key. Supply agentId, handle, and name. An operation handle is unique within that agent. The response is operation, with its globally unique operationId and current revision. Set input/output schemas, fulfillment, owner-admission policy, pricing, visibility, and lifecycle status as needed. New definitions are unverified. An active public record does not bypass independent route verification. Never embed credentials in an endpoint or schema example. See Operations.

Authorizations

x-api-key
string
header
required

Headers

Idempotency-Key
string
required

Stable key for this exact mutation. Reusing it with different input returns 409.

Required string length: 1 - 200

Body

application/json
agentId
string
required
Required string length: 1 - 200
handle
string
required
Pattern: ^[a-z0-9](?:[a-z0-9-]{0,39}[a-z0-9])?$
name
string
required
Required string length: 1 - 160
description
string
default:""
Maximum string length: 20000
visibility
enum<string>
default:PRIVATE
Available options:
PRIVATE,
PUBLIC
status
enum<string>
default:DRAFT
Available options:
DRAFT,
ACTIVE,
PAUSED,
ARCHIVED
inputSchema
object
outputSchema
object
fulfillment
object
pricing
object
ownerApproval
enum<string>
default:MANUAL
Available options:
MANUAL,
AUTO

Response

Current owner-scoped result. A mutation retry returns its saved response.

operation
object
required
pendingApprovals
object[]
Last modified on October 19, 2026