Kyra

Product Snapshot

Kyra Agent is a Base-native AI agent platform for creating user-owned agents that operate through Telegram, maintain private dashboard records, publish shareable agent profiles, and prepare onchain actions behind explicit owner and wallet approval.

Kyra is designed for users and teams who want an agent interface without giving up wallet authority. Agents can understand intent, produce planning or risk context, and prepare bounded action reviews. Sensitive execution stays behind the owner dashboard, Base Account, approval gates, receipt checks, and privacy-safe logging.

Live Product Surface

What Kyra Can Do

• Deploy agent profiles from clear templates.
• Persist signed-in agent records through the backend.
• Publish private dashboard and public profile views.
• Reply in Telegram with read-only commands and planning chat.
• Convert risky wallet or transaction requests into review drafts.
• Refuse Telegram-triggered execution while still producing useful plans, checklists, and risk reviews.
• Require owner approval and wallet approval before any onchain action can move forward.
• Preserve sanitized logs, support evidence, and release readiness records.

Telegram Commands

Connected Telegram agents support a read-only command surface:

Natural prompts can produce campaign plans, market briefs, narrative maps, launch copy, community pulse summaries, and risk reviews. Swap, transfer, approval, contract, wallet, and Base MCP execution requests from Telegram are refused and converted into safe review output.

Agent Templates

Templates are the product package. Kyra modules are the internal capability layer behind them.

Approval-First Execution

Kyra is built around a simple rule: the agent can prepare, but the user wallet decides.

Current safety guarantees:

• No seed phrase collection.
• No private key custody.
• No hidden transaction execution.
• No Telegram-triggered signing.
• No public exposure of Telegram bot tokens.
• No raw session tokens, provider payloads, or wallet internals in public views.
• Owner approval, wallet approval, receipt verification, rollback readiness, and privacy checks stay part of the execution path.

Base MCP And Base Account

Kyra's primary user transaction boundary is Base Account: the user connects their own account, reviews the prepared action, and remains the final approval gate.

Base MCP remains an optional provider adapter track. It is not a blocker for Kyra's Base Account path, and it stays separated until provider metadata, scope semantics, consent, token lifecycle, revocation, rate limits, and owner approval are fully verified.

Product Status

Kyra has closed the current release-readiness roadmap for agent deployment, Telegram-native interaction, wallet policy modeling, Base Account readiness, controlled owner execution flow, public hardening, support operations, launch QA, final security/privacy review, and public product polish.

Public execution remains approval-first by design. Any widened transaction rollout must preserve the same owner dashboard, Base Account approval, risk review, receipt verification, emergency disable, and privacy-safe evidence requirements.

Detailed engineering evidence is tracked in:

• docs/product-phase-roadmap.md
• docs/supporting-readiness-closeout.md
• docs/phase-10-product-release-readiness.md
• Product Readiness Snapshot

Product Principles

• User wallet authority first.
• Telegram-native agent UX.
• Backend-only handling for sensitive integrations.
• Read-only by default; approval before execution.
• No custody, no seed phrases, no hidden signing.
• Clear public copy, sanitized evidence, and explicit release controls.

Links