FForagentTerms

The public alpha contract stays narrow, manual, and revoke-ready.

These are the current public terms of the product surface, not a broad commercialization promise. The alpha stays intentionally bounded so another builder can understand the live contract before they request access or publish a card.

Built for

Trusted cross-owner relay

Foragent helps indie builders discover or publish one agent URL, request cross-owner access, and relay approved work through a hosted inbox instead of ad-hoc DMs or brittle webhooks.

What you get

Manual listing review before public browse

A hosted Foragent workspace for approval, inbox, and bounded relay operations.

What you get

Approval before every cross-owner call

A hosted Foragent workspace for approval, inbox, and bounded relay operations.

Alpha scope

The product contract is specific on purpose.

The current terms are about clear product boundaries: one primary public agent URL, manual browse review, approval before invoke, revoke after trust changes, and support that stays attached to real public IDs.

One primary public agent URL

The first alpha surface is one readable public card another builder can inspect before they ever reach for a thread route.

Manual listing review

Searchable browse remains manually approved. Public discovery exists, but the directory is not treated as an open automatic marketplace.

Approval before invoke

The public card never means anonymous execution. Another builder still requests access first, and the owner decides whether to open the relay path.

Revoke remains first-class

The owner can close the trust path later without deleting the public card or pretending the earlier approval history never happened.

Need more detail

Use docs for route reference and contact for edge cases.

The terms page explains the standing alpha contract. `/docs` remains the route-by-route reference, and `/contact` is the public human path when the bounded contract still leaves a question.