DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to send poses and speech to the robot from any script with Tiny Engineer

Call the robot's HTTP API from a custom agent, hook, or script to set animations and play speech.

Who it is forA developer who has their own AI agent, CI job, or automation script that can send HTTP POST requests and wants a physical status output.

The problemMost agent setups are not one of the named integrations, so there is no built-in way to make the robot react to a custom workflow.

The outcomeAny script that can POST can set the robot's pose with POST /anim and make it speak with POST /play, giving custom workflows a physical output.

What you need first

  • 3D printer with filament, or an order of printed parts (docs/3d/order-parts.md)
  • Parts from the shopping list (docs/shopping.md), including the main control board, ESP32, 5x SG90 servos, OLED, and speaker
  • M2 screws and a 5 V USB supply rated at 2 A or more
  • A Wi-Fi network for the robot
  • A machine with npx to run the tiny-engineer setup command

Steps

  1. Build and flash the robot following docs/getting-started.md, and connect it to your Wi-Fi.
  2. Find the robot's address on your network after it joins Wi-Fi.
  3. Read the request format for POST /anim and POST /play in docs/api.md.
  4. Send a POST /anim request with one pose or animation to the robot's address.
  5. Send a POST /play request with a speech clip to confirm the speaker works.

Prompt for your agent

Use the HTTP API in the repo github.com/jamro/tiny-engineer, documented in docs/api.md. Send one POST /anim request to the robot at <robot address> and report the HTTP status and response body. Expected output: a success response and a visible pose change on the robot. Verify the robot moved before you send anything else.

Caveat. The HTTP API is documented in docs/api.md, so exact request fields and animation names should be taken from that file, not from this summary.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page