Connect your AI agent

You can connect the AI agent you already use, such as Claude Code, Claude Desktop, Cursor, Codex, claude.ai or ChatGPT, to your HOA.AM account, and ask it about your account, such as your balance or your open requests. It sees and does only what you can in the app, and only while its token or connection is valid.

Open the user menu at the right of the header, select My account, then the AI agents tab.

Create a token

1. In the Tokens card, select New token.
2. Enter a Name that says which agent and device will use the token, for example Claude Code on my laptop. It can be up to 80 characters.
3. Under Access, keep Read to let the agent look things up. Add Make changes only if you want the agent to act for you, such as reporting a request, once the portal offers agents such actions.
4. Choose when the token Expires after: 7, 30, 90 or 365 days. Administrators’ tokens last at most 90 days.
5. Enter your Current password. With two-factor authentication on, also enter a code from the app or a recovery code.
6. Select Create token.

The token is shown only once. Select Copy token, or copy the setup below it, before you select Done. If you lose it, revoke it and create a new one.

Add HOA.AM to your agent

Right after you create a token, the drawer shows the setup for each agent with the token filled in. Choose your agent, select the copy button and:

• Claude Code: run the copied command in a terminal.
• Claude Desktop: add it to claude_desktop_config.json (Settings › Developer › Edit config) and restart Claude Desktop. It needs Node.js.
• Cursor: add it to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project.
• Codex: add it to ~/.codex/config.toml.

The Connect an agent card shows the same setup with hpat_… in place of the token, and the Server address for any other agent that speaks the Model Context Protocol.

Connect a web app

Web apps such as claude.ai and ChatGPT cannot take a token. You add HOA.AM to them by its Server address, and they send you to HOA.AM to allow the connection:

1. In the web app, add a custom connector with the Server address from the Connect an agent card.
2. The app opens HOA.AM. Sign in if you are asked to.
3. The Allow an app to use your account? page shows the app’s name marked Unverified, the address you will be sent back to and the access it asks for. Anyone can register an app under any name, so allow it only if you started connecting it yourself just now.
4. Select Allow to connect, or Deny to refuse. Either way you are sent back to the app. If the page says the request has expired, go back to the app and start connecting again.

Disconnect an app

The Connected apps card lists every web app you allowed, with the address it sends you back to, its access, and when it was connected and last used. Select Disconnect next to an app and confirm. It stops working with your account at once; to use it again, connect it again. Changing your password, resetting it or turning two-factor authentication off disconnects every app.

Revoke a token

Select Revoke next to the token and confirm. An agent that uses it can no longer connect. A revoked token cannot be restored.

Good to know

• Give each agent its own token, so you can revoke one without affecting the others. You can hold up to 20 tokens.
• The list shows only the start of each token (hpat_ and eight characters), when it was last used and when it expires.
• Changing your password, resetting it or turning two-factor authentication off revokes every token and disconnects every connected app.
• A token works only for your agent, never to sign in to the portal.
• While an administrator views the portal as an owner, the AI agents tab says that tokens are not shown and lists none.
• The accounts of the public demo and of a private demo cannot create tokens or connect web apps.