AstroFabric started life as a marketing-intelligence dashboard: visibility charts, competitor feeds, creative galleries, opportunity queues. It worked. It was even pretty. And every week of building it made one thing clearer: the people we want to serve were never going to live in another tab.
Developers embed capability. They call functions, they wire webhooks, they hand tools to AI assistants. The dashboard sat between our engine and their code like a lobby you are forced to walk through, so we removed the lobby. One commit deleted the pages, the components, the report builders and the feed machinery. What remains on the web is a console: keys, usage, webhooks, billing.
What survived
- The tool layer: audits, visibility checks, deliverability scoring, Search Console and GA4 access, each a metered endpoint with a JSON schema.
- The agent layer: outcome-shaped endpoints that plan across tools and return typed reports, with a hard cost cap per run.
- The autopilots: standing programs for AI-search visibility and ad operations that run on our schedulers and report to your webhooks.
The lesson we keep relearning: an interface you have to visit is a cost, and an interface your code can call is an asset. We chose the asset.
Every playbook on this blog ships as a runnable mission.
Open a free workspace and the playbook library is waiting - describe the outcome and the agents carry it end to end, with 1,000 trial credits on us.