The Lyre
Software should be able to ask for what it needs.
The Lyre gives software a common way to ask for work to be done, without having to be built around whatever provides it.
01 / The request
Ask for the work.
Let The Lyre route it.
A capability is a reusable kind of work software can ask The Lyre to perform.
- 01 / Your software
Ask for the work.
Software asks The Lyre for something it needs done.
- 02 / The Lyre → provider
The Lyre routes it.
The request goes to a connected provider that can perform that work.
- 03 / Back to your software
Get the result.
The result comes back through the same capability contract.
02 / The interface
This is Lyre Web.
Lyre Web is the human-facing interface for The Lyre. It makes the underlying system easier to explore and operate, but The Lyre does not depend on this website.
Lyre Web depends on The Lyre for the resources it displays. Native software and HTTP clients have their own paths into the same system.
Human
Lyre Web
A visual interface for exploring and operating The Lyre.
Human → Lyre Web → The LyreNative software
LyreSDK + RDGProto
Application-facing primitives over The Lyre’s native protocol.
Application → LyreSDK → RDGProto → The LyreHTTP / generic clients
HTTPS gateway
Translates HTTP/JSON into RDGProto and translates responses back for the client.
HTTP/JSON → Gateway → RDGProto → The Lyre03 / Published on The Lyre
Explore the work available.
This view reads the public catalogue from The Lyre.
04 / Machine access
Software can find its own way in.
Agents can discover how to register, authenticate, and ask for work on The Lyre. The HTTPS gateway translates their requests into the native protocol.
Explore agent access →/.well-known/lyre-agent.jsonHuman access
Your identity on The Lyre.
Create a Lyrinox Account to access The Lyre through Lyre Web.