---
title: "describe_domain"
method: POST
path: "/describe_domain"
tags: ["domain"]
---

# describe_domain

`POST /describe_domain`

## Request

- Base URL: `https://app.podmule.com/api/v1`
- URL: `https://app.podmule.com/api/v1/describe_domain`
- Auth: HTTP bearer

Return the PodMule operating ontology: entity catalog (workspace, show, episode, contact, contact_group, interview_booking, clip, email_template, email_campaign, article, knowledge_page, media_asset, prompt, workflow), relationships, id prefixes, status machines, read/write capability contracts, context-record compatibility, operation context requirements, affordances, common intents, the global (routing/meta/analytics) capability list, and the bulk-capability list. Every callable capability is either mapped to an entity or listed in global_capabilities. Call this once at session start so you can pick the right capability for a question without trial and error. Public metadata — no tenant data, no PII; safe to cache.

## Request body

- unknown

## Response `200`

Capability output wrapped in `{ data }`.

- object
  - `data` unknown, required

## Other responses

- `400`: Invalid input — Zod validation failed.
- `401`: Missing, malformed, or audience-mismatched bearer token.
- `403`: Token is valid but lacks the required scope.
- `404`: Capability not registered, or referenced resource not found.
- `429`: Rate limit exceeded. Retry after the period in `Retry-After`.
- `500`: Internal error.

---

[API](https://skmtc.dev/podmule/apis/podmule-api.md) · [All operations](https://skmtc.dev/podmule/apis/podmule-api/llms.txt) · [OpenAPI document](https://skmtc.dev/podmule/apis/podmule-api/revisions/844ae61495fa?raw)