Frequently asked questions

How do I connect an application?

From the dashboard's Connectors page, click Connect on the application's card. For OAuth applications, the provider's own sign-in window opens: you approve, you are sent back, done. For applications that authenticate with an API key, a small form opens instead — the card tells you where to create the key, and the connector's own page covers whatever is specific to it.

Connections are per user, on team plans too: the subscription is shared, the connections are not. Each teammate connects their own accounts, and their AI acts with their own permissions — never someone else's.

The connection is refused — key rejected, or endpoint not exposed?

“That key was rejected” means the application itself refused the credential: re-copy it, and check it has the required permissions.

“This instance doesn't expose the REST endpoint Proxoria needs” is different: your credentials may be perfectly fine, but the instance cannot answer — its REST API is switched off, a security plugin is blocking it, or the version is too old. The connector's own page lists what it requires. Fix it on the instance, then try again.

How do I connect Claude, ChatGPT or Mistral to Proxoria?

Add Proxoria as a custom connector in your AI client — in Claude: Settings → Connectors → Add custom connector, with your Proxoria MCP URL. The first use opens a Proxoria consent screen where you sign in and choose which of your connected applications the AI may reach — or tick “applications I connect later” to include future ones automatically.

ChatGPT and Mistral follow the same flow: they all speak the Model Context Protocol.

My AI does not see an application I just connected

Three steps, in order. First, start a new conversation: Claude fixes its tool list when a conversation starts, so an ongoing chat will not pick up new tools.

Still missing? In your AI client's settings, disconnect the Proxoria connector, reconnect it, and start a new conversation again.

Finally, if you had selected a fixed list of applications on the consent screen (rather than “applications I connect later”), the new app is deliberately excluded from that authorization — reconnecting reopens the consent screen so you can include it.

Proxoria added new capabilities to a connector, but my AI does not see them

Same reflex as a newly connected application: your AI keeps the tool list it was handed when the conversation started. Begin a new conversation first — that alone is often enough.

If the new capabilities are still missing, disconnect the Proxoria connector in your AI client's settings, reconnect it, then start a new conversation. That forces the assistant to fetch the current tool list instead of the one it had cached.

Does connecting many applications degrade my AI?

Each connected application adds its tools to what your AI sees. Beyond roughly 30–40 tools, assistants become less precise at picking the right one. If you connect many applications, use the consent screen to scope the AI to the ones you actually use from it.

Can the AI modify or publish things in my applications?

Write tools exist, but two guardrails apply. In confirmation mode (the default), every write action waits for your approval on the Activity page before anything executes.

And whatever the AI creates is born unpublished — drafts, disabled entries, unpublished translations, depending on the application. Publishing stays a human action, in the application itself.

How are my credentials stored?

Encrypted at rest (AES-256-GCM, with the key held outside the database), never logged, and never included in error messages. Disconnecting a connector deletes its credentials. Every tool call your AI makes lands in the audit log, visible on the Activity page.

What is my Proxoria API key, and what if it leaks?

It is the personal key (pxa_…) that identifies your environment — your connectors, nobody else's. It is shown exactly once when generated. If it leaks, rotate it from the dashboard: the old key stops working immediately.