Taxonomies

Taxonomies power filters, search landing pages, structured fields, and consistent job data. Skills, categories, and markets are account-specific and writable. Remote permits and timezones are global canonical catalogs and read-only through the Operator API.

Discover taxonomy resources

123
async () => Object.keys(spec.paths).filter((path) =>
  path.startsWith('/taxonomies')
)

Use canonical values

Read the relevant resource before creating or updating a job. Reuse existing category, skill, and market slugs. For remote permits and timezones, send only values returned by their read-only catalog endpoints—you cannot create a missing remote permit or timezone through MCP.

Rename with care

A slug can be part of public URLs and existing job references. Renames add aliases, but the way a change propagates differs by taxonomy, so inspect the live operation and dependent records before approving it.

Deletion does not clean every reference automatically:

• Jobs may retain stale skill slugs after a skill is deleted.
• Companies may retain stale market slugs after a market is deleted.
• Deleting a category also deletes its direct child categories, but deeper grandchildren remain.

Preview affected records and obtain explicit approval before deleting taxonomy data. A deletion can also remove filters or landing pages from the board.