Browse the documentation

Preview documentation for AEL Beta 0.0.1 — launching soon

Use cases

With Beta 0.0.1 of AEL, the Agent Engineering Language, you will be able to build software-engineering agents, agents that serve HTTP or MCP clients, agents on devices and microcontrollers, and robot agents. This section shows what you will build in each field, which optional packages each one uses, and what each will and will not promise.

Status

Planned for AEL Beta 0.0.1. AEL is not available yet.

Complete example agent systems and deployment recipes will be published with the beta.

The pages

What every use case will share

  • No server until you add one. An agent will need no server. It will become an HTTP, gRPC, WebSocket or MCP service only when you add that server package and, for HTTP, declare routes.
  • Optional packages. The packages of each field will be optional official packages, and only what you use will ship: an HTTP-only app will carry no gRPC or WebSocket code. The Package catalog lists the families.
  • You will 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 will use that system's own interface, and you will run that system.
  • The same building blocks. Every agent on these pages will be made of nodes and edges, described in Agents, and every code sample on these pages is preview syntax.