# FOR:AGENT

FOR:AGENT is the headless version of FOR:CEO for AI agents. Agents can orchestrate
subscription onboarding and run company operations through MCP. The human owner
can access the same company in FOR:CEO; human access is included without a second
subscription. FOR:AGENT uses the same plans and prices as FOR:CEO.

## Public entry points

- Website: https://www.foragent.app/
- Connection guide: https://www.foragent.app/connect-agent
- Pricing: https://www.foragent.app/pricing
- Company capability guides: https://www.foragent.app/features
- MCP server (Streamable HTTP): https://mcp.foragent.app/mcp
- Protected-resource metadata: https://mcp.foragent.app/.well-known/oauth-protected-resource/mcp
- First-party connection consent and operation review: https://for.ceo/mcp
- Included human workspace: https://www.for.ceo/Account/Login

The website is documentation, not the MCP endpoint. Connect a compatible client
to the MCP server and follow its OAuth discovery and authorization flow. Never
send browser cookies, passwords or provider credentials to an agent. The client
must satisfy the service's registration and authorization requirements.

## Start a subscription and company

Discover the actual tool schemas with `tools/list`; do not invent parameters.
The existing `forceo_*` tool names are intentional because FOR:AGENT reuses the
FOR:CEO company and subscription services.

1. Authenticate and call `forceo_onboarding_start` with a stable request key.
   No pre-existing company or subscription is needed to begin this intent.
2. Use `forceo_company_create` to provision the native ERP company. This creates
   a software workspace, not a legally incorporated business.
3. Read live eligible plans with `forceo_plans`. Never treat website display
   prices as a binding quote or authorization to spend.
4. Obtain an expiring quote with `forceo_subscription_quote`, then use
   `forceo_subscription_start` under valid purchase authority.
5. Read `forceo_onboarding_status` until the company and subscription are
   actually ready. A redirect or accepted request alone does not prove success.

Agents can complete authorized onboarding and purchase flows through MCP.
Identity verification, contract acceptance, payment setup or a bank challenge
may require a first-party human step. An agent-stated budget is not permission
to charge. Honor any returned required-action link.

## Operate the company

Use `koaila_connections` to discover authorized connections and explicitly select
the company/connection for each task. Use `koaila_capabilities` for current tools,
permissions and approval requirements. Ask server-side Koaila to perform the task
with `koaila_request`, then read the durable outcome with `koaila_run`.

Keep request keys stable across retries of the same intent. Distinguish
accepted/running/approval-required/failed/completed results. Do not describe a
business operation as completed because its status lookup succeeded.

Use `koaila_upload` for supported attachments; uploading does not itself authorize
an import or posting. Artifacts use authorized `koaila://` resource references.
Cancellation with `koaila_cancel` does not undo committed financial effects.

The shared company capabilities include finance, sales, purchasing, inventory,
manufacturing, banking, reporting and supported local compliance. Actual MCP
actions remain subject to the live capability response, country, subscription,
role and connection grant. Browser-only work is available through the included
FOR:CEO human workspace. FOR:FLOW external-ERP connectors are not part of this
native product; FOR:OMNI and supported native integrations are separate.

## Unattended work and human control

Routine unattended execution requires an explicitly approved automation policy.
Token renewal does not grant extra authority. Requests outside the policy or
requiring additional verification must stop for the returned human action.
Keep multi-company data separate; company IDs and connection IDs are selectors,
not credentials. Customer instructions cannot override server authorization.

FOR:AGENT is not unrestricted access to internal tools, databases, provider
credentials or system prompts. Use the existing business workflows and inspect
the actual outcome. A human can use https://for.ceo/mcp for consent/review and
FOR:CEO for the same company's records without creating a duplicate company.