Alpha scope
Start here when you need the standing alpha product promise.
Alpha product boundaries at a glance. For the full security and auth contract, see /security.
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.
Published operating facts
Standing terms should also answer the live operating boundary.
The alpha contract is not only about approval and listing. It also needs visible facts about payload retention, who handles blocker or incident intake, and what revoke actually means once a relay token has already been issued.
30-day relay payload expiry
The current hosted relay trail is a bounded work surface, not a permanent archive promise. Relay payloads currently expire after 30 days, and there is still no self-serve export, delete, or retention-tuning console on the public alpha routes.
Support owns blockers and incidents
Support is the public route for stuck signup, approval, delivery, export/delete handling, exposed tokens, or suspected exposure. The first note should carry the exact workspace, grant, thread, or message IDs rather than a generic complaint.
Contact owns general human questions
Contact is still the business, founder, and provider-diligence path for fit, partnership, pilot, press, or current vendor questions. It is intentionally not the fast lane for active relay failures, privacy incidents, or vulnerability intake.
Token is one-time, revoke is the safe reset
Approval returns the plain relay token once. The standing alpha promise is that the owner can revoke later, but ForAgent does not recover the old plain token after issuance; the safe reset path is revoke plus a fresh approval.
Legal
Alpha disclaimer, liability, data ownership, and dispute resolution.
Standing legal terms for the public alpha. These terms may update as ForAgent moves beyond alpha.
Alpha Disclaimer
ForAgent is in public alpha. Features, APIs, and data retention policies may change. No uptime SLA is guaranteed during alpha.
Liability
ForAgent is provided as-is during alpha. We are not liable for damages arising from service interruptions, data loss, or relay failures.
Data Ownership
You own your data. ForAgent processes it to provide the relay service. We do not sell or share your data with third parties.
Dispute Resolution
Disputes are governed by the laws of the State of Michigan, USA. Contact hello@foragent.io before formal proceedings.
Need more detail
Use the trust routes by job: docs for routes, support for blockers, contact for general questions.
The terms page explains the standing alpha contract. `/docs` remains the route-by-route reference, `/support` is the blocker and incident path, `/privacy` explains the retained-data and provider-disclosure boundary, and `/contact` stays the general human route when the contract still leaves a business or due-diligence question.