Teneo Agent SDK

**Judgement** A capable, well-documented SDK for integrating with Teneo Protocol AI agents from Node/TypeScript environments. It looks production-viable for teams comfortable with Web3 and WebSocket-based backends, especially when you need real-time, room-based interactions and per-request micropayments. **What it does well** - Wraps Teneo’s WebSocket + wallet-signature auth into a straightforward `TeneoSDK` class. - Exposes room and agent management (list/search agents, list rooms, add agents to rooms, subscribe to rooms). - Supports x402 USDC micropayments on multiple EVM networks via simple config (`paymentNetwork`, `paymentAsset`). - Provides strong developer guidance: full connection workflow, retry/backoff, rate-limit handling, payment detection and tracking, and TypeScript interfaces. **Key risks / limitations** - **Private key handling**: Requires a raw Ethereum private key in config/.env. This is a major security and operational risk if not managed correctly (secret storage, access control, rotation). Not suitable for untrusted environments or client-side use without extra protection (e.g., custodial wallets, HSM, or signer abstraction). - **Real-money exposure**: Uses real USDC for x402 micropayments; misconfigurations, bugs, or malicious agents could trigger unexpected spend. Strong monitoring and spend limits are recommended. - **External dependency**: All functionality depends on Teneo’s backend WebSocket service and on-chain USDC infrastructure; outages or rate limits on these services directly impact availability. - **No built-in content safety**: The SDK transports agent responses as-is. Any moderation, PII filtering, or policy enforcement must be implemented by the integrator. **Recommended scenarios** - Backend services (e.g., Node servers, workers, cron jobs) that need to: - Interact with Teneo agents in real time. - Orchestrate multiple agents inside rooms. - Monetize interactions via per-request USDC micropayments. - Internal tools or dashboards for teams already using Teneo Protocol and comfortable managing an Ethereum wallet for the service. **Less suitable for** - Frontend/browser use where embedding a private key is unacceptable. - Teams without Web3/crypto ops maturity (key management, on-chain cost monitoring, regulatory considerations). - Applications requiring strict, built-in safety/morality/PII guarantees without implementing their own filters and guards. Overall, this SDK is a strong fit for Web3-savvy backend developers integrating with Teneo’s AI agent ecosystem, provided they take private key security and spending controls seriously.

**Judgement:** This skill is a capable integration layer for Teneo Protocol agents, well-suited for backend/OpenClaw-style orchestration where you need real-time agent communication plus on-chain micropayments. It appears mature enough for serious prototyping and many production workloads, assuming you are comfortable handling crypto keys and USDC payments. **What it does well** - Provides a focused, well-documented SDK for **connecting to Teneo agents via WebSocket**, with event emitters for responses and connection lifecycle. - Uses **Ethereum wallet-based auth** and supports **USDC micropayments** on Base, Peaq, and Avalanche using the x402 protocol. - Offers a good abstraction for **rooms and agents**: discover rooms, subscribe to public ones, invite/ensure agents in rooms, and send messages with or without room context. - Includes **error-handling patterns** (rate limits, auth failures, payment failures) and **TypeScript types**, which significantly improve usability and robustness. **Key risks / limitations** - **Private key management:** The SDK expects a raw Ethereum private key, usually via environment variable. Mismanagement can lead to key leakage and loss of funds. You need a secure secret-management setup. - **Financial exposure:** Each agent interaction may trigger **real USDC payments**. Bugs (e.g., looping calls, insufficient balance checks) can unintentionally spend funds. - **Service dependence:** All functionality depends on **Teneo Protocol’s backend and supported networks**; outages or chain congestion will directly affect availability and latency. - **Chain & asset constraints:** Currently focused on USDC on specific EVM chains; if your stack or compliance requirements diverge, integration may be constrained. **Recommended scenarios** - OpenClaw skills or Node/TS services that need to **programmatically drive Teneo agents** (e.g., an orchestration layer that calls a Twitter analytics agent and others). - Apps that want **fine-grained, pay-per-request billing** for AI interactions using USDC on Base (or other supported chains), especially where low fees and micropayments matter. - Multi-agent chat or automation backends that benefit from **room-based coordination** and event-driven response streaming. Less ideal if you cannot safely handle crypto keys, wish to avoid on-chain payments entirely, or need offline/air-gapped AI interactions without reliance on Teneo’s infrastructure.