Acceptable use
You may use the public endpoints for learning, demonstrations, and light client testing. You may use Dispatch only with accounts, computers, models, software, and files you own or are allowed to control. Do not evade limits, probe another owner’s records, upload malware, interfere with the service, or use DemoAPI to handle secrets or regulated data.
Public fixtures and listing requests
Built-in catalog responses are deterministic fixtures. They may resemble model, vision, or robot data, but they do not inspect a device or complete a production job. Do not use fixture output for operations, safety decisions, or performance claims.
When you submit a listing request, you confirm that you control the endpoint or have permission to share it. A request does not guarantee acceptance, publication, ranking, or continued listing. You remain responsible for the listed API and its content.
Dispatch Runs
A Run can vary only the typed fields allowed by an Armed Recipe. DemoAPI does not provide a remote shell, arbitrary HTTP proxy, raw workflow editor, or general tunnel. Do not try to turn a Recipe into one.
Cancellation is best effort. A queued Run can stop before claim, but work already submitted to local software may finish even after the owner requests cancellation, signs out, or revokes a Station. A Receipt reports the control-plane result; it is not a guarantee that every local process stopped at the same instant.
Your computer, software, and output
You are responsible for your operating system account, physical access, power, network, model and software licenses, local backups, and the content you generate. Keep the connector package current and review a Recipe before Arming it. DemoAPI account deletion does not remove the connector, ComfyUI, models, or output files from your computer.
Local AI and automation can use substantial GPU time, electricity, disk space, and memory. Watch your own system and stop local software if it behaves unexpectedly. DemoAPI cannot protect a computer that is already compromised.
Availability and responsibility
The site, queue, connector protocol, and demo routes are provided as available, without an uptime, delivery-time, compatibility, or output guarantee. Runs can expire, fail, or wait while a Station is offline. We may change limits or block unsafe use to protect owners and the service.
To the extent permitted by law, AI Embedded Systems is not responsible for lost local work, hardware wear, energy charges, software conflicts, generated content, or actions taken outside the typed Recipe boundary.
Changes and contact
The date above changes when these terms change. Continued use after an update means you accept the current version. You may stop using Dispatch and delete the account from Settings.
Questions or deletion requests can be sent to sohagan@aiembeddedsystems.com. You can also read the security contact note.