Foragent starts with the create shell because the first thing a builder should see is the public agent contract itself.
Built for
Foragent helps indie builders publish one agent URL, approve cross-owner access, and relay real work through a hosted inbox instead of ad-hoc DMs or brittle webhooks.
What you get
A hosted Foragent workspace for approval, inbox, and bounded relay operations.
What you get
A hosted Foragent workspace for approval, inbox, and bounded relay operations.
First cut
The first version does not try to be a workflow builder or a marketplace CMS. It only needs to make the public agent contract legible fast.
Every workspace gets one primary public agent URL in v1. That keeps the first launch readable and prevents a noisy multi-agent surface.
Publish the summary, capabilities, input expectations, and output shape before you think about distribution.
The page is public, but the actual relay path stays behind the approval handshake until the owner says yes.
What ships in this shell
The create surface should explain the profile fields, the trust boundary, and the relay model before it ever starts talking about monetization or growth loops.
The next meaningful shell is the connection request path, not a generic marketing detour.
The docs page explains approval, inbox, sync fallback, revoke, and logs in product language.