# How Blormmy works
Blormmy is an agentic key management platform built on the Solana blockchain that allows users to initiate onchain actions and e-commerce transactions through natural language. It combines artificial intelligence and secure key infrastructure to create a seamless interface for decentralized operations. At its core, Blormmy uses large language models to interpret user intent and execute logic through smart wallets in a non-custodial manner. This is made possible by integrating with a Trusted Execution Environment (TEE), which securely manages the keys used to authorize transactions without exposing them to the outside world.
When a user submits a request—such as a tweet or a post on Blormmy.com—the system parses the command and initiates an agentic orchestration flow. The backend identifies the type of action requested, whether it involves token swaps, purchases, or fund transfers. Each Blormmy agent operates as a modular unit equipped with multiple tools and reasoning capabilities, allowing it to interpret user input, reason about its context, and securely execute the corresponding blockchain transaction. These agents use MCP (multi-context processing) and interact with a series of APIs and services to carry out the user's request.
The types of actions Blormmy handles fall into two primary categories: commerce and token flows. In commerce scenarios, Blormmy processes purchases using USDC, validates stock availability, checks the user's balance, and can even determine whether the purchase is intended as a gift by comparing shipping and sender information. In token flows, Blormmy can swap tokens or transfer assets between wallets. For instance, when a user requests a token swap like "swap 10 USDC for $BLORMMY," the system identifies the input and output tokens, converts the amount to base units, ensures the user has the required associated token accounts, fetches a real-time swap quote from Jupiter (Solana's leading liquidity aggregator), and then signs and executes the transaction securely within the TEE. Afterward, it formats the output, generates a Solscan link for transparency, and sends a confirmation back to the user.
Blormmy supports multiple user interfaces for these interactions. Whether the intent is submitted via a tweet on X.com or directly through Blormmy.com, the backend handles each entry point with tailored logic. For example, tweets require the system to listen for mentions, authenticate the sender, and initiate agent flow through the X API. Meanwhile, requests on Blormmy.com can trigger richer workflows such as order validation, item lookup, and transactional metadata standardization.
The underlying goal of Blormmy is to make complex onchain operations simple, secure, and user-friendly. By fusing AI, cryptographic infrastructure, and commerce functionality, it enables everyday users to interact with blockchain systems without needing to understand the technical details. Whether it’s swapping assets, sending tokens to friends, or ordering gifts, Blormmy’s architecture is designed to handle every step with precision, security, and transparency. As it evolves, the system aims to further reduce friction through features like email-based onboarding, peer-to-peer fund transfers for non-users, and expanded integration with third-party services, ultimately building a network effect that brings more users into the ecosystem.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.blormmy.com/blormmy/readme/overview.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.