> ## Documentation Index
> Fetch the complete documentation index at: https://docs.erdo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# ListDatasetPurposesAPI mirrors the erdo_list_dataset_purposes MCP tool as a


> REST endpoint: the org's dataset vocabulary with descriptions, or — with scope=managed — the vocabulary of every client organization a manager account operates.




## OpenAPI

````yaml /api/openapi.json get /v1/datasets-purposes
openapi: 3.0.0
info:
  title: Erdo API
  description: >-
    Erdo's REST API: query and write datasets, run agents, manage threads,
    integrations, pages, evals, workstreams, experiments, and bounded outreach.
    Authenticate with a Bearer API key (erdo_api_...) or scoped token
    (erdo_token_...).
  version: '2026-09-09'
servers:
  - url: https://api.erdo.ai
    description: Production
security:
  - bearerAuth: []
paths:
  /v1/datasets-purposes:
    get:
      summary: >
        ListDatasetPurposesAPI mirrors the erdo_list_dataset_purposes MCP tool
        as a
      description: >
        REST endpoint: the org's dataset vocabulary with descriptions, or — with
        scope=managed — the vocabulary of every client organization a manager
        account operates.
      operationId: GET:mcp.ListDatasetPurposesAPI
      parameters:
        - allowEmptyValue: true
          description: >
            Scope is "own" (default) or "managed". Under managed, a manager
            account reads every client organization it operates; each entry
            names its organization and its established\_by\_dataset\_slug is
            org-qualified, so it can be fetched as-is without switching
            organizations.
          explode: true
          in: query
          name: scope
          required: false
          schema:
            type: string
          style: form
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  message:
                    description: >
                      query — asking for scope=managed as an organization that
                      manages nobody.
                    title: >
                      Message explains an empty answer that would otherwise read
                      as a broken
                    type: string
                  purposes:
                    items:
                      $ref: '#/components/schemas/mcp.PurposeEntry'
                    type: array
                type: object
          description: Success response
        default:
          $ref: '#/components/responses/APIError'
components:
  schemas:
    mcp.PurposeEntry:
      properties:
        dataset_count:
          format: int64
          type: integer
        description:
          type: string
        established_by_dataset_id:
          description: >
            the canonical instance to reuse when the purpose maps to one
            dataset.
          title: >
            EstablishedByDatasetID is the dataset that first carried this
            purpose —
          type: string
        established_by_dataset_slug:
          description: >
            agent or script can address directly. LLM-facing surfaces reference
            datasets by slug, never UUID (UUIDs don't survive copies/restores),
            so this field is the one callers should use. It is org-qualified, so
            under scope=managed it already names the client organization.
          title: >
            EstablishedByDatasetSlug is that dataset's slug — the write target
            an
          type: string
        organization_name:
          type: string
        organization_slug:
          description: >
            belongs to — the caller's own organization under scope=own, the
            client organization under scope=managed.
          title: |
            OrganizationSlug and OrganizationName say whose vocabulary the entry
          type: string
        purpose:
          type: string
      title: |
        PurposeEntry is one row of the org's dataset vocabulary.
      type: object
  responses:
    APIError:
      content:
        application/json:
          schema:
            externalDocs:
              url: https://pkg.go.dev/encore.dev/beta/errs#Error
            properties:
              code:
                description: Error code
                example: not_found
                externalDocs:
                  url: https://pkg.go.dev/encore.dev/beta/errs#ErrCode
                type: string
              details:
                description: Error details
                type: object
              message:
                description: Error message
                type: string
            title: APIError
            type: object
      description: Error response
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

````