Status

agenta status is the command to run right after agenta login, and the one to reach for whenever something isn’t working. It says who you are signed in as, where going live stands, and the next command to run.

agenta status

Alias: agenta whoami.

Status checks

Account: who you are signed in as, and for which business.
Going live: how many go-live steps are done, your business verification, the free Revenue & Pricing Audit, and your payout account.
Next step: the one command that moves you forward, when there is one.

Test payments work as soon as you are signed in. Live payments wait on a verified business. Payouts wait on a bank account.

Usage

agenta status [--business <id>] [--json]

Flag	Description
`--business <id>`	Show the status of a business you manage.
`--json`	Output a single JSON object instead of the human-readable summary.

Example output

Output

  Signed in as demo@example.com for Acme Freelance on https://api.agentaos.ai.

  Test payments work now. Live money waits on verification.
  Go-live steps done: 1 of 2.
  Business verification: Not submitted.
  Free Revenue & Pricing Audit: Not requested.
  Payout account: not yet added, needed before your first payout.
  Next: start with the free audit (agenta audit request).

The two go-live steps are a first product or payment and a verified business. The dashboard’s setup guide counts three items: the same two, and Go live as the third. A bank account is not a go-live step: you need it before your first payout, not before your first sale. The first line changes as you go:

Where you are	First line
Not verified yet	Test payments work now. Live money waits on verification.
Verified	You can take live payments.

The Next line names the step that blocks you first:

Where you are	`Next` points to
AgentaOS asked for changes on your verification	`agenta verify resubmit`
Not verified, no audit requested	`agenta audit request` (the dashboard shows the audit sealed until you verify; the CLI can ask for it now)
Not verified, audit requested	`agenta verify submit`
Verified, no bank account	Adding a bank account in the dashboard, before your first payout

In every other case there is no Next line, for example while your verification is in review.

`--json`

{
  "account": {
    "authenticated": true,
    "email": "demo@example.com",
    "server": "https://api.agentaos.ai",
    "configDir": "/Users/you/.agenta",
    "orgId": "0b7c6a2e-4f1d-4e8a-9c3b-2d5e7f9a1b04",
    "organization": "Acme Freelance",
    "jwtExpiresAt": "2026-09-28T14:32:00.000Z",
    "jwtSecondsRemaining": 24000,
    "paymentTools": { "ready": true, "mode": "test", "next": "agenta pay checkout -a 50" }
  },
  "goLive": {
    "canGoLive": false,
    "progress": { "done": 1, "total": 2 },
    "verification": {
      "state": "unverified",
      "label": "Not submitted",
      "heldReason": null,
      "rejectReason": null,
      "cooldownUntil": null,
      "changesRequested": []
    },
    "audit": { "label": "Not requested", "requested": false, "reportUrl": null, "grade": null },
    "payouts": { "connected": false },
    "milestones": {
      "firstProductAt": "2026-09-27T09:10:00.000Z",
      "firstTestPaymentAt": "2026-09-27T09:25:00.000Z",
      "firstLivePaymentAt": null,
      "livePaymentCount": 0
    },
    "next": { "command": "agenta audit request", "why": "start with the free audit" }
  }
}

--json also kicks in automatically whenever stdout isn’t a terminal, so piping to jq or writing to a file gives you JSON without the flag: agenta status | jq .goLive.next.

Response fields

Field	Description
`account.authenticated`	Whether you have a valid session.
`account.email`	Account email, decoded from your session token.
`account.organization`	Your business’s name.
`account.orgId`	Your business’s ID.
`account.paymentTools.ready`	Always `true` once you are signed in: test payments work.
`account.paymentTools.next`	A command to try a test payment.
`account.jwtExpiresAt`	ISO 8601 timestamp your session token expires at.
`account.jwtSecondsRemaining`	Seconds left before that expiry.
`account.configDir`	Where the CLI stores its local session config.
`goLive.canGoLive`	Whether you can take live payments.
`goLive.progress`	Go-live steps done, out of the total.
`goLive.verification.state`	`unverified`, `in_review`, `on_hold`, `verified` or `rejected`.
`goLive.verification.label`	The same state in words, including `Changes requested`.
`goLive.verification.changesRequested`	What AgentaOS asked you to change. Empty when it asked for nothing.
`goLive.audit`	Where the free audit stands, with the report link once it exists.
`goLive.payouts.connected`	Whether you have a bank account that can receive payouts. You need one before your first payout.
`goLive.milestones`	When you made your first product, test payment and live payment, and your live payment count.
`goLive.next`	The next `command` and `why`, or `null` when there is nothing to do. `command` is `null` when the step happens in the dashboard.

Not logged in

{
  "account": {
    "authenticated": false,
    "reason": "not-logged-in",
    "next": "agenta login"
  }
}

The command prints this JSON with or without --json, and exits with code 0. reason is either not-logged-in or session-expired, so scripts can tell the two apart.

SDK

CLI

API Reference

Status checks

Usage

Example output

`--json`

Response fields

Not logged in

Next steps

Login

Verify

​Status checks

​Usage

​Example output

​--json

​Response fields

​Not logged in

​Next steps

Login

Verify

Status checks

Usage

Example output

`--json`

Response fields

Not logged in

Next steps