classification

Post Taxonomy Proposal

Accept a structured taxonomy proposal from the agent and persist it as an AgentFinding (finding_type='revenue_opportunity', domain='data_quality').

The proposal action + target + evidence land in the finding's evidence JSONB so the existing approval queue (and the agent's evaluate_peer_findings skill) reads them with the same machinery it uses for every other finding type. Proposals are always created pending — no auto-approval path; Gib reviews on the standard cadence (Tenet #31 — blast radius must be visible before approval).

post/api/v1/classification/taxonomy-proposal

Request

  • Base URL: https://app.goodleads.club (the document declares no server; this is the origin it was published from)
  • URL: https://app.goodleads.club/api/v1/classification/taxonomy-proposal
  • Auth: API key in header X-API-Key

Request body

agent_idstring required

Agent that authored the proposal

actionstring required

One of: ['add_keyword', 'add_sub', 'merge', 'split']

targetobject required

What the proposal is changing. Shape depends on action: {industry_id} for merge, {sector, name} for split/add_sub, {keyword, industry_id_or_industry_sub_id, tier} for add_keyword.

evidenceobject required

Supporting data: corpus_frequency, sample_records, blast_radius (records newly classified / rebucketed / confidence-tier shifted), source_findings.

titlestring required

One-line summary for the findings table

descriptionstring required

Full proposal narrative

statestring nullable
session_idstring nullable

Response

Successful Response

finding_idstring required
statusstring required

Changes

No recorded changes to this operation across all 1 revision of this API.