{"id":"zevorn-rt-claw","name":"rt-claw","homepage":"https://www.rt-claw.com","repo_url":"https://github.com/zevorn/rt-claw","category":"ai-ml","subcategories":[],"tags":["ai","embedded","agent","tool-use","llm","freeRTOS","rt-thread","linux","uart","swarm","skills","memory"],"what_it_does":"RT-Claw is an OpenClaw-inspired intelligent assistant for embedded devices. It provides an AI chat engine that calls an LLM over HTTP, supports tool-use via function calling (30+ built-in tools), and includes a framework for skills, memory (RAM + persistent NVS/flash), swarm-style node discovery/remote tool invocation, scheduled tasks, and a UART chat-first shell with /commands. It is designed to run across multiple OSAL targets (FreeRTOS, RT-Thread, Linux) and includes networking components (HTTP client, Ethernet/WiFi).","use_cases":["Running an on-device/edge AI assistant that can control hardware tools (GPIO, LCD, audio, etc.)","Building multi-step AI workflows via composable “skills” that orchestrate multiple tools","Persisting user/system context using device memory (NVS/flash) for long-term recall","Distributed/connected embedded setups using swarm discovery and remote tool invocation across nodes","Scheduling automated tasks driven by AI (create/list/remove tasks)","Interactive development/debugging using a UART REPL that forwards user input to the AI"],"not_for":["A full-featured cloud SaaS API platform with standard REST/SDKs for developers who want to integrate quickly from a PC/server","Use cases requiring strict, clearly documented enterprise security/compliance guarantees (data handling, auth policies, auditability) without reviewing the underlying implementation","High-assurance reliability requirements where retry/idempotency/error semantics are not documented"],"best_when":"You have embedded/edge hardware (or a validated QEMU target) and want a local tool-using AI assistant framework that can be ported across FreeRTOS/RT-Thread/Linux with OS abstraction.","avoid_when":"You need a well-specified external API contract (OpenAPI/SDK) or documented security controls (TLS/auth/rate-limit/error codes) at the integration surface without inspecting source/docs.","alternatives":["OpenClaw / nanobot / MimiClaw (inspiration lineage for similar embedded assistant approaches)","Ollama-based agent stacks with your own tool runner on a host system","Commercial embedded voice/agent platforms with managed security and API contracts"],"af_score":32.8,"security_score":36.8,"reliability_score":30.0,"package_type":"skill","discovery_source":["openclaw"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:25:12.077058+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Environment variable for LLM API key (RTCLAW_AI_API_KEY)"],"oauth":false,"scopes":false,"notes":"The README indicates an API key is set via RTCLAW_AI_API_KEY, but does not describe server-side auth, scope granularity, or rotation/auditing mechanisms for RT-Claw itself."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source (MIT). Costs would primarily be your LLM provider usage if you connect to external LLM APIs."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":32.8,"security_score":36.8,"reliability_score":30.0,"mcp_server_quality":0.0,"documentation_accuracy":40.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":70.0,"rate_limit_clarity":0.0,"tls_enforcement":30.0,"auth_strength":35.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":60.0,"security_notes":"README mentions setting an API key via an environment variable, which is a better-than-hardcoding default, but it does not document transport security (TLS requirements), how keys are stored/used, scope restrictions, rate limiting, or how errors/logging avoid leaking secrets. Dependency hygiene and CVE posture cannot be determined from the provided content.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":40.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["No MCP/standard agent interface documented; integration likely requires wiring into its HTTP/LLM and UART/tool interfaces from the agent runtime you control.","Because this targets embedded OSAL platforms, tool invocation and failure modes may depend on hardware drivers and network conditions; error semantics are not documented in the provided material."]}}