Skip to content
United AI Explorer

For agents

Every way to reach UAI Explorer — the human lanes first, then the machine lanes: bounded JSON endpoints, server-side redaction, audited reads. Each card states what the service advertises and what was actually observed; credentials never appear here.

Public website

Anyone — no account, no key

advertised advertised by the service — endpoint observed 200 on 2026-09-19; the lane itself was not authenticated from this environment

Authentication
Anonymous — no credential
Connection instructions
https://explorer.united-ai.ca/for-agents
  1. Read the public pages — Products, the founder story and this guide need no account.
  2. Check readiness — GET https://explorer.united-ai.ca/ready answers JSON: status, version, redaction boundary.

Observed 200 on 2026-09-19. Anonymous pages cache publicly; every response is redacted server-side before it leaves the service.

Human reader

People with an Explorer account

advertised advertised by the service — endpoint observed 200 on 2026-09-19; the lane itself was not authenticated from this environment

Authentication
Username + password session
Connection instructions
https://explorer.united-ai.ca/login
  1. Open the sign-in page — The login form posts your username and password — nothing else is needed.
  2. Sign in — The session cookie is HttpOnly and expires after 12 hours; password managers and no-JS submits are supported.
  3. Read in the workspace — /workspace/documents lists, previews and reads the documents your account may see, with history back to any revision.

Login page observed 200 on 2026-09-19. This lane is for humans: machine clients use one of the lanes below.

Custom GPT Actions — Bearer PAT

Custom GPTs and API clients with an Explorer PAT

advertised advertised by the service — endpoint observed 200 on 2026-09-19; the lane itself was not authenticated from this environment

Authentication
Bearer PAT — Authorization header
Connection instructions
https://explorer.united-ai.ca/api/ai/chatgpt/instructions
MCP endpoint
https://explorer.united-ai.ca/api/ai/mcp
OpenAPI schema
https://explorer.united-ai.ca/api/ai/chatgpt/openapi.json
  1. Fetch the instructions — GET https://explorer.united-ai.ca/api/ai/chatgpt/instructions returns the machine-readable lane metadata.
  2. Configure the key in GPT settings — Actions authentication: API Key with auth type Bearer in the Authorization header. The Explorer PAT goes in the GPT's settings — never in chat.
  3. Call in order — uai_ready (health) → uai_bootstrap (start) → uai_context on the slugs start returns.

Advertised by the service; instructions endpoint observed 200 on 2026-09-19. The PAT is issued by the operator — tokens are prefixed uai_pat_ and shown nowhere on this site.

Local MCP adapter — PAT

Local agent runtimes (Hermes/Codex-style) via the Explorer MCP endpoint

reported reported by a configured worker — no adapter in this environment, client side unverified here

Authentication
Bearer PAT — Authorization header
Connection instructions
https://explorer.united-ai.ca/api/ai/chatgpt/instructions
MCP endpoint
https://explorer.united-ai.ca/api/ai/mcp
  1. Point the adapter at the MCP URL — https://explorer.united-ai.ca/api/ai/mcp — streamable-HTTP JSON-RPC.
  2. Send the PAT as a Bearer token — One Authorization header on every call; tokens in query, body or cookie are rejected.
  3. Call in order — uai_ready (health) → explorer_start (bootstrap) → explorer_context on the slugs start returns — the MCP names for uai_bootstrap / uai_context.

Reported lane: a worker configured a vault-backed local adapter (Hermes report); no adapter is configured in this environment, so the client side is unverified here. The server endpoint is implemented and advertised; unauthenticated calls answer 401 with the OAuth resource-metadata pointer.

OAuth Connect — RFC 7591 + PKCE

Hosted clients (ChatGPT-style) that register dynamically

advertised advertised by the service — endpoint observed 200 on 2026-09-19; the lane itself was not authenticated from this environment

Authentication
OAuth Connect — RFC 7591 + PKCE
Connection instructions
https://explorer.united-ai.ca/api/ai/chatgpt/instructions
MCP endpoint
https://explorer.united-ai.ca/api/ai/mcp
OpenAPI schema
https://explorer.united-ai.ca/api/ai/chatgpt/openapi.json
Server metadata
https://explorer.united-ai.ca/api/ai/oauth/.well-known/oauth-authorization-server
Register (RFC 7591)
https://explorer.united-ai.ca/api/ai/oauth/register
Authorize
https://explorer.united-ai.ca/api/ai/oauth/authorize
Token
https://explorer.united-ai.ca/api/ai/oauth/token
  1. Read the server metadata — GET https://explorer.united-ai.ca/api/ai/oauth/.well-known/oauth-authorization-server — issuer, endpoints, grant and PKCE methods.
  2. Register a client (RFC 7591) — POST https://explorer.united-ai.ca/api/ai/oauth/register with your redirect URIs; the response carries the client_id (no client secret — token endpoint auth is none).
  3. Authorize with PKCE S256 — GET https://explorer.united-ai.ca/api/ai/oauth/authorize with code_challenge; approve with the Explorer PAT to mint a one-time code.
  4. Exchange the code — POST https://explorer.united-ai.ca/api/ai/oauth/token with the verifier; the response is a Bearer token scoped explorer.read.

Metadata verified 200 on 2026-09-19 (both well-known endpoints). The full client flow has not been run from this environment, so this lane is advertised, not read-verified. Scope is explorer.read only.

Tool order — every machine lane

  1. uai_ready — health only; no credential needed to learn reachability.
  2. uai_bootstrap — compact start; returns the canonical context slugs.
  3. uai_context — read the slugs start returned; continue from advertised links.

MCP endpoint names the same steps: uai_bootstrap → explorer_start, uai_context → explorer_context. What to do next lives in Explorer, not on this page.

Access contract

The durable first-connect rule is prepared as an issue-ready document (uai-doc-docs-runbooks-explorer-access-contract-v1) and is not issued yet — issue is the owner-and-operator release gate. Start here carries the pointer.

Ground rules