Connect your application securely

Create your first key#

1. Add a key with a recognizable name, such as a device or application name.
2. Choose the group, model access, quota, and expiration available on the current form. Grant only the access you need.
3. Copy the key and store it in a password manager or the application’s private configuration.

Available groups and models may differ between accounts. Follow the options shown in your own console.

Three fields for your client#

Some clients append /v1 automatically. Check the resulting request URL to avoid /v1/v1.

Check your key and available models#

Set an environment variable in your terminal, then query the models available to your key. Replace the placeholder with your own key.

export MOMAPI_API_KEY='YOUR_MOMAPI_API_KEY'

curl --fail-with-body 'https://api.momapi.link/v1/models' \
  --header "Authorization: Bearer ${MOMAPI_API_KEY}"

Quota, usage, and revocation#

Account balance and key quota are separate limits. Your account pays for usage, while a key may also have its own quota, expiration, or model restrictions. A positive balance does not grant every key access to every model.

Check requests and charges in usage logs, and your account balance in the wallet. Disabling or deleting a key prevents applications using it from making requests; update those applications first.

Keep keys in private configuration#

• Create separate keys for separate applications to make unexpected usage easier to identify.
• Do not commit keys to Git, embed them in frontend code, or share them in public chats and screenshots.
• If a key may have leaked, revoke it and create a replacement.