Skip to main content
POST
Publish a tool's draft
  • Business accounts only, with tools:build. Pomerado doesn’t check the draft’s code, so only an Owner or Admin signed in to the Dashboard publishes it, never an API key or an agent.
  • Send the digest of the draft you saw. It publishes once a run of the draft passed on the live version, for free, and the draft is then gone.
  • The draft’s files replace the live version’s, a repair’s included, with the inputs and outputs its run read. A public tool’s code is read only, so publishing its draft is forbidden.
  • Callers: an API key, an MCP OAuth token or a Dashboard session.
  • Permission: tools:build.
  • Effect: Creates or changes something.
  • Errors: business_account_required, not_found, draft_changed, draft_not_run, draft_not_publishable, and the errors any request can get.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

a tool ID: tool_ and 32 lowercase hex digits

Example:

"tool_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190"

Body

application/json
digest
string
required

The draft's digest, as code.get answered it

Pattern: ^[0-9a-f]{64}$

Response

The tool's code, with the draft live

integration
object
required
tool
object
required
versions
object[]
required

The tool's versions, newest first, at most 100

files
object[]
required

The live version's files, by path

draft
object | null
required

Your team's draft of the tool, shared by every member, or null when it has none