TuCloudAPI aichat - Revision history

Maintenance script: TuCloudAPI reference (generated from func=help): aichat history bounds

2026-11-02T10:55:38Z

TuCloudAPI reference (generated from func=help): aichat history bounds

← Older revision		Revision as of 10:55, 2 November 2026
Line 18:		Line 18:
	\| <code>message</code> \|\| string \|\| Yes \|\| — \|\| The user's message (POST body).		\| <code>message</code> \|\| string \|\| Yes \|\| — \|\| The user's message (POST body).
	\|-		\|-
	\| <code>history</code> \|\| string \|\| No \|\| — \|\| JSON array of prior turns [{role,content}] (the client keeps state).		\| <code>history</code> \|\| string \|\| No \|\| — \|\| JSON array of prior turns [{role,content}] (the client keeps state). Only role user\|assistant with string content is taken; anything else is skipped. The newest 40 turns, each cut at 8000 characters, 100000 characters in all (oldest dropped first). The turns kept are the ones echoed back in history.
	\|-		\|-
	\| <code>confirm</code> \|\| string \|\| No \|\| — \|\| JSON {tool,args[,summary]} of a proposed write the user has confirmed.		\| <code>confirm</code> \|\| string \|\| No \|\| — \|\| JSON {tool,args[,summary]} of a proposed write the user has confirmed.

Maintenance script: TuCloudAPI reference (generated from func=help)

2026-10-31T16:15:35Z

TuCloudAPI reference (generated from func=help)

← Older revision		Revision as of 16:15, 31 October 2026
Line 4:		Line 4:

	== Description ==		== Description ==
	AI assistant for this PBX (Spanish). Agentic loop over DeepSeek ~~that uses~~ a ~~curated subset of~~ this API's ~~own endpoints as tools (each executed through~~ the ~~(ukey~~,~~pbx) tenant binding). READ tools auto-run; create/edit/delete are PROPOSED~~ (needs_confirmation) and ~~executed~~ only on a confirm={tool,args} re-post. A portal session is offered only the ~~tools~~ its ~~PBX pin and section gate allow, and~~ the prompt names who is talking ~~and their sections~~. Widgets: simflow, entity, list, chart (bar/line/donut/columns), page ~~(a button to a portal page)~~, audio_target. v1 non-streaming. POST the message (+ optional history/confirm).		AI assistant for this PBX (Spanish). Agentic loop over DeepSeek whose tools are SKILLS (business-term operations run by a server-side runner), never this API's functions; the runner resolves names to ids, applies the session's PBX pin and section gate, proposes every write (needs_confirmation) and executes it only on a confirm={tool,args} re-post, pre-fills updates from the current record and shapes every result. A portal session is offered only the skills of its sections; the prompt names who is talking. Widgets: simflow, entity, list, chart (bar/line/donut/columns), page, audio_target. v1 non-streaming. POST the message (+ optional history/confirm).

	== Call ==		== Call ==
Line 20:		Line 20:
	\| <code>history</code> \|\| string \|\| No \|\| — \|\| JSON array of prior turns [{role,content}] (the client keeps state).		\| <code>history</code> \|\| string \|\| No \|\| — \|\| JSON array of prior turns [{role,content}] (the client keeps state).
	\|-		\|-
	\| <code>confirm</code> \|\| string \|\| No \|\| — \|\| JSON {tool,args} of a proposed write the user has confirmed.		\| <code>confirm</code> \|\| string \|\| No \|\| — \|\| JSON {tool,args[,summary]} of a proposed write the user has confirmed.
	\|}		\|}
	== Example ==		== Example ==
Line 26:		Line 26:

	== Response ==		== Response ==
	{ok, text, tools_used:[{tool,ok~~,error?~~}], widgets:[{type:"simflow",~~data:{...simulatecall~~...}}], needs_confirmation:{tool,args,summary}\|null, history:[...]}.		{ok, text, tools_used:[{tool,ok}], widgets:[{type:"simflow"\|"entity"\|"list"\|"chart"\|"page"\|"audio_target",...}], needs_confirmation:{tool,args,summary}\|null, history:[...]}.

	== Errors ==		== Errors ==

Maintenance script: TuCloudAPI reference (generated from func=help)

2026-10-31T15:09:07Z

TuCloudAPI reference (generated from func=help)

← Older revision		Revision as of 15:09, 31 October 2026
Line 4:		Line 4:

	== Description ==		== Description ==
	AI assistant for this PBX (Spanish). Agentic loop over DeepSeek that uses a curated subset of this API's own endpoints as tools (each executed through the (ukey,pbx) tenant binding). READ tools auto-run; create/edit/delete are PROPOSED (needs_confirmation) and executed only on a confirm={tool,args} re-post. v1 non-streaming. POST the message (+ optional history/confirm).		AI assistant for this PBX (Spanish). Agentic loop over DeepSeek that uses a curated subset of this API's own endpoints as tools (each executed through the (ukey,pbx) tenant binding). READ tools auto-run; create/edit/delete are PROPOSED (needs_confirmation) and executed only on a confirm={tool,args} re-post. A portal session is offered only the tools its PBX pin and section gate allow, and the prompt names who is talking and their sections. Widgets: simflow, entity, list, chart (bar/line/donut/columns), page (a button to a portal page), audio_target. v1 non-streaming. POST the message (+ optional history/confirm).

	== Call ==		== Call ==

Maintenance script: TuCloudAPI reference regenerated from func=help: tenancy rule, pbx notes on every PBX-scoped function, error codes

2026-10-08T21:16:25Z

TuCloudAPI reference regenerated from func=help: tenancy rule, pbx notes on every PBX-scoped function, error codes

← Older revision		Revision as of 21:16, 8 October 2026
Line 1:		Line 1:
	''TuCloudAPI function to manage FuturePBX (the cloud PBX). Available to: '''SuperRoot, Operator, Client'''.''		''TuCloudAPI function to manage FuturePBX (the cloud PBX). Available to: '''SuperRoot, Operator, Client'''.''

			{{Note\|1=Requires the <code>pbx</code> parameter (the PBX '''name''', e.g. <code>tucall</code>). The server verifies that your <code>ukey</code>'s own account owns that PBX, whatever its role; otherwise, and also for a PBX that does not exist, it returns <code>{"ok":false,"code":"forbidden"}</code>.}}

	== Description ==		== Description ==
Line 5:		Line 7:

	== Call ==		== Call ==
	~~GET~~ https://tucloudapi.7kas.com:9087/tucloud?func=aichat&ukey=YOUR_KEY		https://tucloudapi.7kas.com:9087/tucloud?func=aichat&ukey=YOUR_KEY&pbx=PBX_NAME
	Requires the <code>ukey</code> parameter.		GET, or POST with the parameters form-urlencoded in the body. Requires the <code>ukey</code> parameter. Always HTTP 200; the response is a JSON envelope.

	== Parameters ==		== Parameters ==
Line 25:		Line 27:
	== Response ==		== Response ==
	{ok, text, tools_used:[{tool,ok,error?}], widgets:[{type:"simflow",data:{...simulatecall...}}], needs_confirmation:{tool,args,summary}\|null, history:[...]}.		{ok, text, tools_used:[{tool,ok,error?}], widgets:[{type:"simflow",data:{...simulatecall...}}], needs_confirmation:{tool,args,summary}\|null, history:[...]}.

			== Errors ==
			Always HTTP 200. On failure the body is <code>{"ok":false,"code":"...","message":"..."}</code>. Common codes: <code>missing_pbx</code>, <code>forbidden</code>, <code>invalid_param</code>, <code>not_found</code>, <code>conflict</code>, <code>in_use</code>, <code>db_error</code>, <code>server_busy</code>; the Response section above lists any specific to this function.

	----		----
	Back to [[TuCloudAPI]]		Back to [[TuCloudAPI]]
	[[Category:TuCloudAPI SuperRoot]][[Category:TuCloudAPI Operator]][[Category:TuCloudAPI Client]][[Category:TuCloudAPI]]		[[Category:TuCloudAPI SuperRoot]][[Category:TuCloudAPI Operator]][[Category:TuCloudAPI Client]][[Category:TuCloudAPI]]

Maintenance script: TuCloudAPI reference: pbx param help -> FuturePBX (API surface unchanged)

2026-08-03T14:30:57Z

TuCloudAPI reference: pbx param help -> FuturePBX (API surface unchanged)

← Older revision		Revision as of 14:30, 3 August 2026
Line 12:		Line 12:
	! Parameter !! Type !! Required !! Default !! Meaning		! Parameter !! Type !! Required !! Default !! Meaning
	\|-		\|-
	\| <code>pbx</code> \|\| string \|\| Yes \|\| — \|\| ~~TuCloud PBX~~ name (tenant boundary; the assistant only touches this PBX).		\| <code>pbx</code> \|\| string \|\| Yes \|\| — \|\| FuturePBX name (tenant boundary; the assistant only touches this PBX).
	\|-		\|-
	\| <code>message</code> \|\| string \|\| Yes \|\| — \|\| The user's message (POST body).		\| <code>message</code> \|\| string \|\| Yes \|\| — \|\| The user's message (POST body).

Maintenance script: TuCloudAPI reference: product name -> FuturePBX (API surface unchanged); regenerated from func=help

2026-08-03T14:13:58Z

TuCloudAPI reference: product name -> FuturePBX (API surface unchanged); regenerated from func=help

← Older revision		Revision as of 14:13, 3 August 2026
Line 1:		Line 1:
	''TuCloudAPI function to manage ~~tucloud~~ (PBX) ~~services~~. Available to: '''SuperRoot, Operator, Client'''.''		''TuCloudAPI function to manage FuturePBX (the cloud PBX). Available to: '''SuperRoot, Operator, Client'''.''

	== Description ==		== Description ==

Maintenance script: TuCloudAPI reference — add func=aichat (AI assistant) + reports category

2026-08-02T17:31:27Z

TuCloudAPI reference — add func=aichat (AI assistant) + reports category

New page

''TuCloudAPI function to manage tucloud (PBX) services. Available to: '''SuperRoot, Operator, Client'''.''

== Description ==
AI assistant for this PBX (Spanish). Agentic loop over DeepSeek that uses a curated subset of this API's own endpoints as tools (each executed through the (ukey,pbx) tenant binding). READ tools auto-run; create/edit/delete are PROPOSED (needs_confirmation) and executed only on a confirm={tool,args} re-post. v1 non-streaming. POST the message (+ optional history/confirm).

== Call ==
GET https://tucloudapi.7kas.com:9087/tucloud?func=aichat&ukey=YOUR_KEY
Requires the <code>ukey</code> parameter.

== Parameters ==
{| class="wikitable sortable"
! Parameter !! Type !! Required !! Default !! Meaning
|-
| <code>pbx</code> || string || Yes || — || TuCloud PBX name (tenant boundary; the assistant only touches this PBX).
|-
| <code>message</code> || string || Yes || — || The user's message (POST body).
|-
| <code>history</code> || string || No || — || JSON array of prior turns [{role,content}] (the client keeps state).
|-
| <code>confirm</code> || string || No || — || JSON {tool,args} of a proposed write the user has confirmed.
|}
== Example ==
<nowiki>https://tucloudapi.7kas.com:9087/tucloud?func=aichat&ukey=KEY&pbx=tucall (message in POST body)</nowiki>

== Response ==
{ok, text, tools_used:[{tool,ok,error?}], widgets:[{type:"simflow",data:{...simulatecall...}}], needs_confirmation:{tool,args,summary}|null, history:[...]}.

----
Back to [[TuCloudAPI]]
[[Category:TuCloudAPI SuperRoot]][[Category:TuCloudAPI Operator]][[Category:TuCloudAPI Client]][[Category:TuCloudAPI]]