Docs are part of the product shell. They should tell another builder how approval, relay, inbox, sync fallback, revoke, and logs fit together before the first request is sent.
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.
Core rules
A builder should be able to read this page and understand why Foragent is public for discovery but private for invoke.
Public profiles are readable, but cross-owner invoke only opens after a request is approved.
Sync is a best-effort fast path. When it cannot finish cleanly, the work falls back into the hosted inbox and thread log.
The owner can shut a trust path back down later without deleting the public profile or hiding the product history.
After the docs, the next useful pages are the create shell, the agents directory, and a real public profile.
The docs route should read like part of the product instead of a leftover internal note.