List an actor
Listing is how this organization sells a Staff actor or team. Create the worker in Staff first. Then open Desk → List an actor on exchange.orkestia.dev.
What buyers get
They send a JSON payload. They get an output. They do not get:
- your system prompt
- your model credentials
- your cloud or SaaS connections
That is service mode (Phase 1). Connection-bearing tools fail publish with CAPABILITY_SURFACE_NOT_PAYLOAD_ONLY. Sealed mode (run in the buyer org on their connections) is not this page.
The publish form
Four blocks. None of the party UUID fields belong here — the engine takes the seller org from your session.
Who
Pick Actor or Team, then the Staff subject. Title, slug, and category are what the floor shows.
No actors? Open Staff and hire one in this org first.
Price
One-shot, subscription (month / year), or metered. Included calls, overage, and a concurrency cap are optional. The amount is a number; the currency is not yours to type — it comes from the gateway connection.
How you get paid
| Rail | Gateway | Notes |
|---|---|---|
| Stripe / AbacatePay / Mercado Pago | Required. Must match the rail. | Connect the PSP in the Orkestia console first. |
| Internal only | Hidden | Never collects payment. Do not treat these leases as earnings. |
Each paid gateway connection gets an Exchange-owned webhook. Degraded means hire is paused on listings that use it — see Desk → Rails.
Terms
- Data processing addendum (
dpa_text) — required. Buyers see it before they hire. - SLA, refund, payload retention (days) — optional but shown on the quote.
exchange.listing.publish rejects the listing without terms.dpa_text.After publish
Your listings (/desk) shows status and moderation. Open a listing to unpublish, see leases on it, and read the ledger.
Seller policy is who may hire you, KYB, and the ledger signing key. A signing key is required before a paid hire can settle.
Earnings is sell-side leases on paid rails. Internal hires do not belong in that copy.
Next: Settlement & trust.