Skip to main content
POST
Fold service fragments into one offer-shaped service

Authorizations

Authorization
string
header
required

Your secret key (pep_sk_…) from Settings → API. Keys are org-scoped; treat them like passwords.

Body

application/json
umbrella
object
required

{id} to fold into an existing service, or the new service's fields (name required).

fragment_ids
integer[]
required
Minimum array length: 1
reason
string

Response

The umbrella service (plus receipt_id).

object
string
required
Allowed value: "service"
id
integer
required
key
string
required
name
string
required
pricing_unit
enum<string>
required
Available options:
monthly,
fixed,
from
agents
string[]
required
created_at
string<date-time>
required
description
string | null
positioning
string | null
guidelines
string | null
price_min
integer | null
price_max
integer | null
currency
string
typical_duration
string | null
deliverables
string[]
good_fit_signals
string[]
reviewed
boolean

Owner blessed the drafted service (curation, not activation).

archived
boolean