Skip to main content

ForAgent status

Published alpha surface is reachable.

Use this page when you need one human-readable check that the public contract, starter assets, and trust routes are all published from the same current alpha host. For machine checks, use /status.json.

Current bundled publication label: alpha-2026-04-01-launch-confidence. The starter bundle and status surfaces should move together under that one release stamp.

Auth split

  • Control-plane setup, approval, and revoke stay on the signed-in session.
  • Caller-side write routes use relay bearer token only.
  • Owner or participant thread read/respond/close routes can now use minted thread access bearer tokens.

Published operating facts

Shared support mailbox

hello@foragent.io during Mon-Fri, 9am-5pm ET; support is the blocker queue and contact is the pre-blocker queue.

Retention and export/delete

Relay payloads expire after 30 days. There is still no self-serve export, delete, or retention-tuning console.

Short-lived auth steps

Verification and recovery links expire after 60 minutes, and minted thread access tokens expire after 60 minutes.

Relay token reset

Relay token stays usable until revoke. The safe reset path is revoke plus a fresh approval.

Provider disclosure

Stripe-backed billing is published in-product; broader relay/workspace provider details are still shared manually in human replies.

Status surfaces

/status and /status.json are the public reachability checks before support takes over a blocker.

Launch confidence checks

Host and status surfaces stay green

Start at /status and /status.json before you assume a launcher, asset, or auth bug needs human triage.

Starter bundle ships as one release set

The contract JSON, OpenAPI snapshot, SDK, starter app, diagnostics script, smoke script, and publication manifest should all move together under alpha-2026-04-01-launch-confidence.

Browse is still a confidence surface

Featured examples stay visible until live approved browse reaches 12 cards across 3 external owners and 3 categories.

Human escalation only after the public checks

Use docs, status, and diagnostics first; then route live blockers to support and pre-blocker diligence to contact with the exact IDs or business context already in hand.

Published starter assets

Dashboard: latest