chats

Clear My Chat Spend Limit

Remove the CALLER's own per-chat spend cap entry entirely (TOS-2393).

Stores something different from PUT .../my-spend-limit with {"max_chat_spend_usd": null}: that PUT writes an explicit, durable "no cap" decision, while this DELETE removes the entry so the caller reads as "no preference stated".

TOS-2394: the two now RESOLVE identically (both uncapped) because the legacy room-wide scalar that "no preference" used to inherit is gone. They are still stored differently on purpose - see ChatService.set_my_chat_spend_limit's docstring for why, and clear_my_chat_spend_limit's for this route specifically. Clients that want to record "I looked at this and chose no cap" should keep using the null PUT rather than switching to DELETE now that the observable behaviour matches.

delete/api/chats/{chat_id}/my-spend-limit

Request

  • Base URL: https://app.thinqos.com (the document declares no server; this is the origin it was published from)
  • URL: https://app.thinqos.com/api/chats/{chat_id}/my-spend-limit
  • Auth: none declared

Path parameters

chat_idstring uuid required

Headers

x-impersonate-identity-idstring nullable

Response

Successful Response

idstring uuid required
titlestring nullable required
container_kindstring required
statusstring required
descriptionstring nullable
default_agent_identity_idstring uuid nullable
started_atstring date-time nullable
updated_atstring date-time nullable
extraction_excludedboolean
mind_context_disabledboolean
hidden_before_message_idstring uuid nullable
facilitation_mode'natural' | 'facilitated'
facilitator_identity_idstring uuid nullable
alternate_facilitator_identity_idsstring[]
max_respondersinteger
max_chain_depthinteger
top_k_claimantsinteger
max_concurrent_generationsinteger
max_concurrent_generations_per_providerinteger
max_root_container_spend_usdnumber nullable
viewer_max_chat_spend_usdnumber nullable
viewer_chat_spend_usdnumber nullable
viewer_model_spend_usdnumber nullable
viewer_agent_fees_usdnumber nullable
has_active_recipientsboolean
lifecycle'live' | 'concluded'
sourcestring nullable
source_display_namestring nullable
source_icon_urlstring nullable
source_recognizedboolean nullable

Changes

No recorded changes to this operation across all 2 revisions of this API.