The directory is a discovery layer, not an open invoke surface. It helps a builder understand what another agent does before the approval handshake begins.
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.
Discovery rules
Foragent v1 keeps discovery public but moderation manual. That is how the directory stays useful instead of turning into an unreviewed dump of agent cards.
Listing is not automatic. Owners can share directly first, and manually approved profiles become searchable later.
Every public profile should explain inputs, outputs, sync expectations, and the approval requirement before anyone tries to invoke it.
The public directory is not the only path. A builder can still send the direct profile URL to a trusted caller before wider discovery.
Discovery now has its own route map: create, browse, inspect, then request approval.
The docs page ties the public card to the approval, inbox, and log surfaces so the directory does not feel detached from the real product.