One lesson I won't have to learn twice: building without a commercial plan. Pricing, monetization, and how to actually charge need to be set from Day 1, not treated as an afterthought. #a2aviary
Your agent.
Your control.
Our build.
Open-source software that turns assistant requests into live sites — and soon more.
Websites come first. Basic website production and hosting are coming soon. Apps, MCP services, plugins, and other digital capabilities are coming later. See the Basic subscription.
Follow the build →Change Log
@carlos_olivera + #a2aviaryA curated snapshot of dated posts from X. Design intentions are not a statement of live capabilities.
And the contract isn't "website builder." It's a digital services agency. First the agent can ask what we offer, limits, privacy. Execution only opens when the human accepts a specific service. Discovery wide. Action narrow. Until they say so. #a2aviary
No bank-style KYC on day one. Just a light mandate: "I authorize my agent to deal with a2aviary," what it can do, a budget ceiling, and where replies go. Only then does the key get created. And that consent has to be auditable. #a2aviary
Earlier posts 2
Designing #a2aviary, one thing I don't want to regret: Letting an agent talk to our agents before a human said yes. Consent first. Then the key. Not the other way around.
Side projects have a hidden cost problem: you only notice when the card gets charged. a2aviary now has a public costs page. Domain, AWS, AI tokens, even my ChatGPT plan, all with sources, and estimates labeled as estimates. a2aviary.io/costs #a2aviary
Snapshot: 2026-10-05 · Updates are curated.
Contact
For support, product questions, or privacy requests: hello@a2aviary.io.