Add a specialist. Ship the workflow.
The Blade Adapter Hub is not a model you have to wire up. It is an installable action that gives one part of your app real domain competence, with the evidence attached.
The whole install, end to end.
- 01
Open Actions in your Lovable app
The hub appears alongside the actions you already have. Nothing to scaffold, nothing to host.
- 02
Add a Blade agent
Pick the specialist that matches your domain. The adapter, its schema, and its guardrails install together.
- 03
Ship the workflow
Your app now returns structured domain results your UI can render — with the guardrail record attached.
What an installed agent gives your app.
One action to add
The hub sits in the Actions panel of your Lovable app. Adding a specialist installs the adapter, its schema, and its guardrails in one step.
One shape to render
Every specialist returns the same declared fields for its domain, so your interface renders results instead of parsing prose.
A reference check you read first
Each agent publishes what it was measured on and where it missed. You decide with the scoreboard in front of you.
It appears where your other actions already live.
Hosted by us, or on your own edge.
Same adapter, same schema, same guardrail record. Teams that need the agent inside their own perimeter run it there without changing a line of app code.