Muse (Meta) — no install. Tell Muse "Install HiRey". It adds HiRey as a Custom Connector: it gets one anonymous key with a single call (POST https://hi.hirey.ai/v1/agents/api-keys), then searches people over HTTPS. Full steps for agents: https://hirey.ai/llms.txt (section "Muse (Meta)").
FOR YOU
Say this to Muse:
Install HiRey. Steps: https://hirey.ai/install/muse
Muse does the rest. It tells you when HiRey is connected.
FOR MUSE — or any agent that works over HTTPS without an installer
HiRey is not in Muse's Connectors directory yet, so add it as a Custom Connector. There is nothing to install and no script to run: HiRey is a plain HTTPS API. When the user says "install HiRey" (or 装 HiRey / 安装 HiRey), that is the go-ahead for the steps below. You are done when one search returns people.
1.
Get the connector key (one call)
POST https://hi.hirey.ai/v1/agents/api-keys
{"display_name":"Muse","agent_type":"muse"}
Use your own name if you are not Muse. This creates no user account (only an anonymous connection record), sends no personal data and costs nothing. The key can only search until the user signs in (step 4).
Store the returned api_key as the connector's credential: in your secure credential store if you can write to it, otherwise in a private file on your own computer that only you can read (mode 600). Don't paste it into chat or logs.
Create it once. If a HiRey key is already saved, reuse it. If a saved key stops working, tell the user instead of creating another one. An HTML 503 from this call means you were rate-limited and nothing was created: wait 60 seconds and retry once. On any other failure, don't retry; tell the user. Ignore the setup and mcp_url fields in the response; they are for Codex.
2.
Connector settings
Name: HiRey
Base URL: https://hi.hirey.ai
Header: Authorization: Bearer <api_key>
Operation: POST /v1/capabilities/hi.workspace-workflows/call
Body: {"action":"people.find","payload":{"query":"seed-stage fintech founder in SF"}}
OpenAPI: https://hirey.ai/openapi.json
{"action":"catalog"} lists every operation. {"action":"describe","payload":{"operation":"<name>"}} shows one operation's fields. A 503 on a call is a temporary outage, not a bad key: wait 60 seconds and retry once.
3.
Test, then tell the user
Run catalog, then one people.find. When it returns people, tell the user HiRey is connected and offer a first search.
4.
Sign in once before writing
Searching works right away. Posting, contacting, messaging and scheduling return verified_login_required until the user signs in. Ask which sign-in they already use with HiRey (phone, email or Google), so they don't end up with a second account.
POST https://hi.hirey.ai/v1/capabilities/hi.phone-binding/call with {"action":"bind","phone":"+14155550123"}, then {"action":"verify","code":"<code from the SMS>"}.hi.email-binding and "email".hi.google-link with {"action":"start"}. The user opens verification_url on their own device, then you call {"action":"poll"} until status is verified.Authorization: Bearer <api_key> header on all sign-in calls (phone, email and Google); the key tells HiRey which connection to sign in.The same key keeps working afterwards; there is no reinstall.
Agent reading this? Full per-host spec: /llms.txt
Questions about permissions, privacy & credentials? Read the FAQ →