Connect your own AI to your portal.

• Sign in with your email. Only people on your portal’s sign-in list can connect an AI app, and anything it sends shows who set it up. An old portal link can’t set one up.
• It has to be turned on for your portal. When it is, you’ll see Use your own AI in your portal’s Connections tab. If you don’t, ask your engineer.
• Your AI app has to allow apps you add yourself. In Claude and ChatGPT that depends on your plan, and on a company account an admin may need to allow it.

1. In Claude, open Customize, then Connectors, and choose Add custom connector.
2. Name it Answered Work and paste the address above. You don’t need a client ID or secret.
3. Choose Connect. When our sign-in page opens, sign in with your portal email.
4. On the Allow page, check that it says Claude and shows your business. Pick See and send or See only, then choose Allow.
5. Start a new chat and ask something like “What’s the latest on my project?” If Claude doesn’t use it, turn on Answered Work in the chat’s tools menu.

On a Team or Enterprise plan, an owner of your Claude account adds the connector first. Then each person connects with their own sign-in.

1. In ChatGPT, open Settings, then Apps & Connectors.
2. Under Advanced, turn on Developer mode.
3. Create an app. Name it Answered Work, paste the address above and choose OAuth for sign-in.
4. When our sign-in page opens, sign in with your portal email, then choose Allow.
5. In a chat, add Answered Work from the tools menu and ask it something.

Developer mode isn’t on every ChatGPT plan. On a work account, your ChatGPT admin may need to turn it on.

Any app that can add a remote MCP server with a sign-in can connect, such as Claude Code, Cursor or VS Code. Add the address above as a remote (HTTP) MCP server and the app opens our sign-in page. In Claude Code, for example:

claude mcp add --transport http answered-work https://answered.work/mcp/portal

Then type /mcp in Claude Code and choose Answered Work to sign in. If an app asks for a key instead of a sign-in, make one as below.

1. In your portal’s Settings, under API keys, name the key and pick See only, unless your script needs to send things.
2. Copy the key when it appears. It’s shown once.
3. Send it with each request as a Bearer token:

curl https://answered.work/api/v1/overview \
  -H "Authorization: Bearer YOUR_KEY"

Every endpoint is listed in the API reference. A key also works at the address above, for an AI app that takes keys.

It can

• See your project: systems and their numbers, updates, meetings, goals, requests and your engineer’s questions.
• Look up your business records the way the portal assistant does, with emails and phone numbers hidden.
• With See and send, send requests and messages to your engineer and answer their questions. They land in your engineer’s inbox like anything you send from the portal.

It can’t

• Change anything in your systems or connected accounts. Your engineer reviews every request and makes every change.
• See anything outside your portal: other businesses, our own tools, your portal chat, files you’ve uploaded, or the access your connected accounts grant.
• Send more than 10 requests and messages a day (portal and AI together) or 20 answers a day.

• Start from your AI app. Don’t connect from a link someone sends you.
• Check the Allow page. The address bar should say answered.work, and the page should name the app you’re connecting and show your business and email. If it says the app “calls itself” something you didn’t just connect, choose Cancel.
• Pick See only if you only want answers. You can connect again later to allow sending.
• Mind your AI app’s other tools. If it can also browse the web, send email or open files, it can use what it reads in your portal there too. Connect it only in an app you trust, and check what it plans to send.
• Treat keys like passwords. Keep them in a password manager or your software’s secret settings, never in email, chat or a shared document. Delete keys you don’t use.
• Look over your connections now and then. Your portal’s Settings lists every app and key, who set it up and when it was last used.

What your AI app reads from your portal goes to the company that runs it, under your agreement with them, not ours. Our Privacy Policy has the details.

In your portal’s Settings, choose Disconnect next to the app or Delete next to the key. It stops working right away. Your engineer can do it for you too.

Connections also end on their own when the person who set them up is removed from your sign-in list, and an app that hasn’t been used for 90 days drops off.

The page says Not available yet.

Connecting isn’t turned on for your portal. Ask your engineer.

You’re asked to sign in again.

Sign in with the email on your portal’s sign-in list. If yours isn’t on it, ask your engineer to add it.

Your AI app says it can’t reach your portal.

Disconnect it in your portal’s Settings, then connect again from the app.

It says it can only read.

It was connected with See only. Connect again and choose See and send.

It says there were too many calls.

Wait a few minutes. Limits keep a stuck app from flooding your portal.

Anything else.

Message your engineer in your portal, or email [email protected].