mirror of
https://github.com/agentrhq/authsome.git
synced 2026-09-19 01:34:19 +08:00
Manoj Bajaj
61515356a2
Align public docs with Principal/Vault/Identity terminology, current daemon API paths, and the CLI/proxy/export integration surface instead of the removed AuthService library API. Co-authored-by: Cursor <cursoragent@cursor.com>
98 lines
2.7 KiB
Plaintext
98 lines
2.7 KiB
Plaintext
---
|
|
title: "Mention Me"
|
|
sidebarTitle: "Mention Me"
|
|
description: "Store and use your Mention Me API key with authsome. Local encrypted vault, proxy injection, no key in the agent's environment."
|
|
keywords: ["mention me api key authsome", "mention me key broker", "mention-me agent credentials", "authsome mention-me"]
|
|
---
|
|
|
|
import MultiConnectionsCta from "/snippets/multi-connections-cta.mdx";
|
|
import MaskedInputNote from "/snippets/masked-input-note.mdx";
|
|
import WhatsNextApiKey from "/snippets/whats-next-apikey.mdx";
|
|
|
|
Mention Me uses a long-lived API key. Authsome stores the key encrypted in the local vault, injects it at request time through the proxy, and keeps it out of shell history, process listings, and environment dumps.
|
|
|
|
## At a glance
|
|
|
|
| | |
|
|
|---|---|
|
|
| Provider name | `mention-me` |
|
|
| Display name | Mention Me |
|
|
| Auth type | API key |
|
|
| Header | `Authorization: Bearer <key>` |
|
|
| Proxy host | `mention-me.com` |
|
|
| Env var | `MENTIONME_API_KEY` |
|
|
| Provider docs | [https://mention-me.com/api](https://mention-me.com/api) |
|
|
|
|
## Get a key
|
|
|
|
See the Mention Me API documentation at [https://mention-me.com/api](https://mention-me.com/api) for how to obtain a key.
|
|
|
|
Mention Me API keys are account-managed; contact your account manager to enable API access.
|
|
|
|
## Log in
|
|
|
|
```bash
|
|
authsome login mention-me
|
|
```
|
|
|
|
A local browser form opens at `http://127.0.0.1:7998`. Paste the key into the masked input and submit.
|
|
|
|
<MaskedInputNote />
|
|
|
|
Verify:
|
|
|
|
```bash
|
|
authsome get mention-me --field status
|
|
# → connected
|
|
```
|
|
|
|
## Use the key
|
|
|
|
Run the agent under the proxy (recommended).
|
|
|
|
<CodeGroup>
|
|
|
|
```bash Proxy (recommended)
|
|
authsome run -- python my_agent.py
|
|
```
|
|
|
|
```bash Environment
|
|
eval "$(authsome export mention-me --format env)"
|
|
echo $MENTIONME_API_KEY
|
|
```
|
|
|
|
</CodeGroup>
|
|
|
|
Under the proxy, authsome sets `MENTIONME_API_KEY=authsome-proxy-managed` in the child's environment and injects the real key into outbound requests to `mention-me.com`. The child process never sees the actual value.
|
|
|
|
## Multiple keys
|
|
|
|
<MultiConnectionsCta />
|
|
|
|
```bash
|
|
authsome login mention-me --connection personal
|
|
authsome login mention-me --connection team
|
|
```
|
|
|
|
## Rotate or remove the key
|
|
|
|
```bash
|
|
authsome login mention-me --force # rotate
|
|
authsome logout mention-me # remove local credential
|
|
authsome remove mention-me # remove all local state for the provider
|
|
```
|
|
|
|
API-key providers have no revocation endpoint, so `revoke` and `remove` are equivalent for Mention Me.
|
|
|
|
## Override the bundled definition
|
|
|
|
```bash
|
|
authsome inspect mention-me > ~/.authsome/providers/mention-me.json
|
|
# edit fields
|
|
authsome list # source now shows "custom" for mention-me
|
|
```
|
|
|
|
## What's next
|
|
|
|
<WhatsNextApiKey />
|