Member portal

Sign in, create and revoke keys, inspect prepaid balance and usage, copy the Gateway base URL, and change your password.

The MEMBER portal is a session-authenticated self-service console on the Admin host. It replaces the retired JSON auth API; there is no public registration endpoint.

Before a member signs in

An operator must create an ACTIVE MEMBER user, set limits and model permissions, and grant prepaid credit. See Admin console guide. The portal does not sell credit or accept payments; top-ups are operator actions.

Sign in

Open:

https://<admin-host>/my/login/

Sign in with the member email and password. Ten failed attempts for either the email or client IP trigger a 15-minute lock. Sessions have an eight-hour maximum age. INACTIVE or SUSPENDED users are rejected.

Portal sections

The single /my/ page uses anchors for:

  • Overview — current prepaid balance, tier, active-key count, total requests, and total tokens.
  • Quickstart — deployment-specific OpenAI-compatible base URL and curl/Python/JavaScript examples. Operators must pass CORDY_GATEWAY_BASE_URL to the Admin service as shown in Configuration.
  • Balance — up to 100 recent top-up, consume, adjust, and refund ledger entries.
  • API Keys — create, list, and revoke your own keys.
  • Usage — totals and the 50 most recent requests; optional Langfuse links appear when the operator passes ADMIN_LANGFUSE_TRACE_URL_TEMPLATE to the Admin service.
  • Account — email, tier, status, and password change.

Create a key

  1. Open API Keys.
  2. Enter an optional name.
  3. Select Create Key.
  4. Copy the wnx_ plaintext immediately; it is removed from the session after that display.

The deployment defaults to at most three key records per user, though an operator can change the platform setting. The count includes revoked and inactive records, so revoking a key does not free a creation slot. Portal-created keys inherit your default rate and token quota and start with inference scopes. Ask an operator to add balance if a programmatic client must call account endpoints.

To revoke a key, select Revoke in its row and confirm. Revocation is permanent for that key; create another key if needed.

Make a request

Copy the Base URL shown under Quickstart. It normally ends in /v1. Use the copied key:

export CORDY_BASE_URL="https://gateway.example.com/v1"
export CORDY_API_KEY="wnx_..."

curl -sS "$CORDY_BASE_URL/models" \
  -H "Authorization: Bearer $CORDY_API_KEY"

Then choose one returned model ID and follow Client integration. The Gateway accepts text chat and embeddings; chat image and audio parts are rejected.

Understand balance and quota

  • Prepaid balance is account-wide money. Each settled request debits its computed upstream cost. Zero balance returns HTTP 402.
  • Token quota belongs to a key. Exhausting it returns HTTP 429 even if the account still has credit.
  • Rate limit also belongs to a key and counts requests per minute.

The portal shows account totals through its Django session. API account endpoints separately require a key with the balance scope.

Change password and sign out

Under Account, enter the current password and a new password of at least eight characters. A successful change preserves the current session. Use Sign out in the header; logout accepts POST only.