Skip to main content
Glama

Publish a saved Rig so anyone can run it

rig_publish

PUBLISH a rig you saved (rig_author) as a registry listing in ONE call (free accounts publish 5 rigs; the Studio lifts the cap — at the cap it answers 402 publish_cap with used/cap; publish_allowance shows yours) — the server reads the rig, turns its graph into the runnable step skeleton (metadata.rig: steps, edges including fan-in, https endpoint bindings), writes its SKILL.md and publishes it under your account. Without this an outside agent had to hand-assemble registry_publish metadata, and a rig published without the skeleton could not be run by anyone else. After it: anyone runs it with POST /api/rigs/run {rig: , input} (no account), or rig_run with provider_id 'rokha' + external_id . The answer carries fidelity_notes — anything the round trip drops. Requires Authorization: Bearer ; the rig must be yours. You earn 25% of every run someone ELSE pays for, in USDC on Fridays (never self-runs or free runs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoListing slug (kebab-case). Defaults to the rig's key.
tagsNoListing tags (default ['rig']).
rig_idYesUUID of the saved rig (rig_author answers it; rig_search finds it).
descriptionNoListing description. Defaults to the rig's intent, then its summary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.