Connecting an AI to Orax (MCP)

You can connect your own AI assistant straight to your Orax account: it will see your services, their expiry dates, your orders and your balance, and answer questions about them in plain language. This works over MCP (Model Context Protocol), an open standard that Claude, ChatGPT and other clients understand.

What the agent can do

• Read your profile and display currency.
• List your services with their status and expiry date.
• Open one service in detail.
• Diagnose a service: is the site reachable, how many days are left on its certificate, what this month's uptime was, and whether the renewal is already covered.
• Show your wallet balance and your orders.
• Browse the plan catalogue.

What the agent cannot do

None of this: order, renew, pay, change plan, delete, or change a setting.

That is a rule, not an omission: money is moved by a human. The agent reads and advises; you click, in the cabinet. That is why connecting it to a third-party client is safe.

How to connect

1. In your AI client, add an MCP server with this address:

https://orax.uz/api/v1/mcp

1. The client works out that it needs authorisation and opens the MyIT login — the same login as the cabinet.
2. Confirm the permissions. Only four are requested, all read-only: profile, services, orders, wallet.
3. Done. Ask something like "when does my hosting expire" or "is my site up".

No separate key or password is needed: the client finds the entry point itself and sends you to the normal Orax login page.

Why a one-click "add" button may not work

Some apps expect the server to register a client for them automatically (RFC 7591). We deliberately do not: an endpoint that mints OAuth clients for anyone needs protection of its own. So paste the address by hand — that works everywhere.

If your client asks for a token

Some clients cannot log you in themselves and expect a ready token. Our public API issues one over the standard OAuth2 flow; the addresses are published at /.well-known/oauth-authorization-server and described on the developer page.

For resellers: every client at once

If you are on the partner programme there is a second endpoint — https://orax.uz/api/v1/reseller/mcp. It authenticates with your ordinary rsk_… key; no OAuth. The agent sees all your clients' services together, so you can ask who expires this week and whose renewal will not cover itself, without exporting anything. The catalogue comes back with the wholesale price and the suggested retail price at your markup.

What the agent sees, and what it does not

The agent sees exactly what you see in your own cabinet and nothing belonging to anyone else. Passwords — control panel, FTP, databases — are never returned: they have no API representation at all. A read token must not become full access to a server.

How to disconnect

Remove the server in your AI client's settings. Access stops immediately; nothing has to be done in Orax.