Agent Marketplace API

A curated catalog of pre-built AI agents — customer support, lead qualification, appointment booking, FAQ, etc. Install one to your org with a single call; configure prompts and tools afterwards. Tenants can also submit their own templates back to the public catalog for moderator review. Base path: /api/v1/agents/marketplace Authentication: API key (X-API-Key) or session JWT.

Using the SDKs

import { Orbit } from "@devotel-orbit/node";

const orbit = new Orbit({ apiKey: process.env.ORBIT_API_KEY! });

const res = await orbit.marketplace.listListings();

Python (same call via the SDK’s escape hatch):

from orbit_sdk import OrbitClient

client = OrbitClient.from_env()  # reads ORBIT_API_KEY

res = client.request("GET", "/agents/marketplace")

The Python SDK is core-scope — it wraps the 8 core resources (messaging, voice, contacts, campaigns, verify, numbers) and reaches everything else through the generic client.request() escape hatch above. See the Python SDK. Returns the typed ApiResponse envelope. See the SDK index at SDK quickstart.

Browse and install

Method	Path	Purpose
`GET`	`/agents/marketplace`	Browse available templates
`GET`	`/agents/marketplace/{slug}`	Get a single template by slug
`POST`	`/agents/marketplace/{slug}/install`	Fork a template into your org

The list endpoint accepts the category, channel, search, featured, and limit query parameters. Templates are addressed by their slug (kebab/underscore-cased), not a numeric id. install forks the template into your org as a new, fully editable agent and requires the owner or admin role.

Browse the catalog

Filter the catalog with the category and channel query parameters:

curl "https://api.orbit.devotel.io/api/v1/agents/marketplace?category=customer_support&channel=whatsapp" \
  -H "X-API-Key: dv_live_sk_..."

{
  "data": {
    "templates": [
      {
        "id": "at_01JXK0M4Q2W8RPZ3N9V6TQHSBD",
        "slug": "wa-support-deflector",
        "name": "WhatsApp Support Deflector",
        "category": "customer_support",
        "description": "Answers tier-1 questions on WhatsApp and hands off unresolved threads to your team.",
        "channels": ["whatsapp"],
        "tags": ["support", "deflection"],
        "author": "orbit",
        "is_featured": true,
        "install_count": 1284,
        "status": "approved"
      },
      {
        "id": "at_01JXK1B8T5M4RPE2Y7W0VQANZC",
        "slug": "wa-order-status",
        "name": "WhatsApp Order Status",
        "category": "customer_support",
        "description": "Looks up order status and answers shipping questions over WhatsApp.",
        "channels": ["whatsapp", "sms"],
        "tags": ["support", "ecommerce"],
        "author": "orbit",
        "is_featured": false,
        "install_count": 312,
        "status": "approved"
      }
    ],
    "total": 2,
    "filters": { "category": "customer_support", "channel": "whatsapp", "search": null, "featured": null }
  },
  "meta": { "request_id": "req_9f3c2a", "timestamp": "2026-08-24T09:12:04.113Z" }
}

Only approved templates are listed. Each entry also carries system_prompt, model, temperature, tools_config, and conversation_starters — fetch the full row for one template with GET /agents/marketplace/{slug}.

Install a template

Fork a template into your org. The body is optional — pass name and description to override the template defaults:

curl -X POST https://api.orbit.devotel.io/api/v1/agents/marketplace/wa-support-deflector/install \
  -H "X-API-Key: dv_live_sk_..." \
  -H "Content-Type: application/json" \
  -d '{ "name": "Support Deflector — Acme" }'

Returns 201 with the forked agent’s id and full record:

{
  "data": {
    "agent_id": "agt_01JXK4F2HP7S8VW0N3QC5YRBZD",
    "template_slug": "wa-support-deflector",
    "template_name": "WhatsApp Support Deflector",
    "agent": { "id": "agt_01JXK4F2HP7S8VW0N3QC5YRBZD", "name": "Support Deflector — Acme" }
  },
  "meta": { "request_id": "req_4b7e1d", "timestamp": "2026-08-24T09:12:19.402Z" }
}

The forked agent is a normal agent in your org — edit its prompt, tools, and channels afterwards via the AI Agents API. Installing an unknown or unapproved slug returns 404.

Submit and moderate

Method	Path	Purpose
`POST`	`/agents/marketplace/publish`	Submit a new template for review
`GET`	`/agents/marketplace/pending`	View the moderation queue (platform moderator)
`POST`	`/agents/marketplace/{slug}/moderate`	Approve or reject a submission (platform moderator)
`GET`	`/admin/marketplace/pending`	Same queue via the admin console (cookie session)
`POST`	`/admin/marketplace/{slug}/moderate`	Same approve/reject via the admin console (cookie session)

The moderation queue and approve/reject actions are reachable under two prefixes that behave identically — pick whichever matches how you authenticate:

/agents/marketplace/* uses the standard API auth (X-API-Key or session JWT).
/admin/marketplace/* uses the admin-console cookie session.

Either way, moderation is platform-moderator only. A regular tenant owner cannot list or approve pending submissions on either prefix. POST /agents/marketplace/publish requires the owner or admin role and takes a flat template definition (no listing wrapper, no agent_id, no pricing):

curl -X POST https://api.orbit.devotel.io/api/v1/agents/marketplace/publish \
  -H "X-API-Key: dv_live_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "my-custom-agent",
    "name": "My Custom Agent",
    "category": "customer_support",
    "description": "A brief description of what this agent does",
    "system_prompt": "You are a helpful assistant for ...",
    "model": "claude-sonnet-4-6",
    "temperature": 0.7,
    "tools_config": ["crm_lookup", "order_status"],
    "conversation_starters": ["How can I help?"],
    "channels": ["whatsapp", "sms"],
    "tags": ["support"]
  }'

Returns 202 with the submission queued for moderation:

{
  "data": {
    "template_id": "at_01JXK9T4W2N8VQE5R0HDP3MCYB",
    "slug": "my-custom-agent",
    "status": "pending",
    "message": "Template submitted for moderation. You will be notified once it is approved."
  },
  "meta": { "request_id": "req_2ad8f0", "timestamp": "2026-08-24T09:13:47.910Z" }
}

Required fields are slug, name, category, and system_prompt; the rest default (description="", model="claude-sonnet-4-6", temperature=0.7, empty tools_config/conversation_starters/channels/tags). suggested_handoff is optional. Rejection paths: a duplicate slug returns 409 Conflict; a missing or invalid required field returns 422 with the failing field named in error.details.issues.

Submissions land with status: pending and are invisible to the public catalog until a platform moderator approves them. The moderation queue (GET .../marketplace/pending) and the approve/reject endpoint (POST .../marketplace/{slug}/moderate) are platform-moderator only. They are reachable under both the /agents/marketplace prefix (API-key or session JWT) and the /admin/marketplace prefix (admin-console cookie session), and behave identically — neither prefix lets a tenant owner moderate. Moderation sets status to approved (template becomes visible) or rejected (kept for audit) — notes are required when rejecting. There is no tenant self-publish: a tenant can submit, but only a moderator can approve.

API Reference

All Endpoints

Agent Marketplace API: browse, install, and submit agents

Agent Marketplace API

Using the SDKs

Browse and install

Browse the catalog

Install a template

Submit and moderate

See also

​Agent Marketplace API

​Using the SDKs

​Browse and install

​Browse the catalog

​Install a template

​Submit and moderate

​See also

Agent Marketplace API

Using the SDKs

Browse and install

Browse the catalog

Install a template

Submit and moderate

See also