outcomes

Post Outcome

Record a customer-reported outcome event against a verdict.

Examples:

Customer filed: POST /v3/verdicts/v_abc/outcome {"event_type":"filed","event_at":"2026-05-12","classes":[9,42]}

Customer got a §2(d) Office Action citing senior mark XYZ: {"event_type":"office_action","event_subtype":"§2(d)", "counterparty":"XYZ Inc","resolution":"pending"}

Customer received C&D from senior holder: {"event_type":"cnd","counterparty":"Big Co Inc", "cost_usd_est":12500,"resolution":"settled","notes":"..."}

Customer rebranded away from the name (failure outcome): {"event_type":"rebranded","cost_usd_est":50000, "resolution":"rebranded","notes":"forced rebrand due to ..."}

Per the board moat memo, these reports are the FOUNDATIONAL data the competitor structurally cannot replicate. Customers who report are contributing to a calibration corpus that makes the engine better for everyone. Offer goodwill counsel-review credit ($500) in exchange for detailed reporting.

post/v3/verdicts/{verdict_id}/outcome

Request

  • Base URL: https://api.etymolt.com
  • URL: https://api.etymolt.com/v3/verdicts/{verdict_id}/outcome
  • Auth: none declared

Path parameters

verdict_idstring required

Request body

event_type'filed' | 'office_action' | 'published' | 'registered' | 'abandoned' | 'cnd' | 'ttab' | 'settled' | 'launched' | 'rebranded' | 'acquired' | 'shutdown' | 'traction_milestone' required
event_subtypestring nullable
event_atstring date nullable
counterpartystring nullable
classesinteger[] nullable
cost_usd_estnumber nullable
resolution'pending' | 'settled' | 'fought_and_won' | 'fought_and_lost' | 'rebranded' | 'withdrew' | 'co_existence' | 'unknown' nullable
notesstring nullable
payloadobject nullable

Response

Successful Response

unknown required

Changes

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