Hunter 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.Documentation Index
Fetch the complete documentation index at: https://authsome.agentr.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
At a glance
| Provider name | hunter |
| Display name | Hunter |
| Auth type | API key |
| Header | Authorization: Bearer <key> |
| Proxy host | api.hunter.io |
| Env var | HUNTER_API_KEY |
| Where to get a key | https://hunter.io/api_keys |
Get a key
Create an API key in the Hunter dashboard at https://hunter.io/api_keys.Log in
http://127.0.0.1:7998. Paste the key into the masked input and submit.
On a headless machine without a graphical session, authsome falls back to masked terminal input via getpass. The browser bridge is skipped automatically when no display is available.
Verify:
Use the key
Run the agent under the proxy. The library tab is for embedding authsome inside a larger Python orchestrator.HUNTER_API_KEY=authsome-proxy-managed in the child’s environment and injects the real key into outbound requests to api.hunter.io. The child process never sees the actual value.
Multiple keys
Pass--connection <name> on login and on every read command to keep two or more accounts on the same provider side by side. See Multiple connections per provider for the full pattern.
Rotate or remove the key
revoke and remove are equivalent for Hunter.
Override the bundled definition
What’s next
Run agents with the proxy
Keep the key out of the agent’s environment entirely.
Multiple connections per provider
Keep two or more keys on the same provider side by side.
API-key providers
All bundled API-key providers.
Provider schema
Every field in a provider definition.