AEL Docs
Follow updates
Menu
Follow updates
Browse the documentation

AEL 1.0.0

Use cases

With AEL 1.0.0 you build software-engineering agents, agents that serve HTTP or MCP clients, agents on devices and microcontrollers, and robot agents. This section shows what you build in each field with AEL, the Agent Engineering Language, which optional packages each one uses, and what each does and does not promise.

Complete example agent systems and deployment recipes come with AEL 1.0.0.

The pages

  • Services and APIs

    Turning a console agent into an HTTP, gRPC, WebSocket or MCP service that sends each reply to the authenticated caller that asked for it, and services built elsewhere that call your agents over gRPC.

  • Retrieval over your documents

    Retrieval (RAG) from ingestion to cited answers, with your own knowledge connectors.

  • Robotics

    Typed units and frames, ROS 2 and DDS, simulation first, deterministic safety and hierarchical robot agents.

  • Scientific computing

    Numerical arrays, complex numbers, linear algebra, optimization, signal processing, integration and automatic differentiation.

  • Quantum computing

    Typed circuits, simulators, export to OpenQASM and QIR, jobs on quantum hardware and hybrid agent workflows.

  • Calling your existing programs

    Your Python, JavaScript, Java or .NET programs, shell commands and operating-system operations as typed tools.

What every use case shares

  • No server until you add one. An agent needs no server. It becomes an HTTP, gRPC, WebSocket or MCP service of your own design only when you add that server package and, for HTTP, declare routes. An edge that your deployment places on the network needs no server package: it uses AEL's built-in gRPC-compatible transport with TLS, as Communication between agents describes.
  • Optional packages. The packages of each field are optional official packages, and only what you use ships: an HTTP-only app carries no WebSocket code, and no gRPC code unless an edge is placed on the network. The Package catalog lists the families.
  • You run the outside systems. When a package talks to an outside system, such as a database, a model server, a robot or a quantum computer, it uses that system's own interface, and you run that system.
  • The same building blocks. Every agent on these pages is made of nodes and edges, described in Agents.