Connect Zortix to Muse or Grok

Q: The agent says 401, "unauthorized", or "key missing or revoked"

A 401 means Zortix did not accept the key the agent sent: it is missing, mistyped, or was revoked. Open https://web.zortix.app/settings/connectors. If the key the agent uses is listed under "revoked", create a new one; if it is live, the agent is sending something else — re-paste the key into the agent's credential vault (Muse: the secret named ZORTIX_API_KEY; Grok: the bearer token on the connector). Keys start with zk_live_ and are shown once at creation. If you no longer have it, revoke it and create another; the old one stops on the next request. Nothing about your account has changed and nothing was lost.

Q: The agent says 402, "limit", or "upgrade"

A 402 is a plan limit, not an error: the connector runs on the same meters as the app. On the free plan: three full idea reads and three Ask questions per UTC day, fifteen followed shows, ten followed tickers, ten saved ideas. The source moment (the transcript quote and audio pointer) is Premium. Day-scoped limits reset at UTC midnight; the answer carries resetsAt. Premium removes every one of them: https://web.zortix.app/premium?utm_source=connector The digest, search, ticker mentions, shows, your follows list and your profile stay unlimited on both plans — the agent can keep going with those.

Q: Muse connects but "can't find tools" or only sees two

Muse shows the tools the key's scopes allow. Two tools means the key was sent without an account behind it (a free-tier key from /developers, not a connector key) or was not sent at all. Create a connector key at https://web.zortix.app/settings/connectors (it holds every scope by default) and store it in Muse's credential vault as ZORTIX_API_KEY, then rebuild the connector from https://api.zortix.app/v1/mcp. Check https://api.zortix.app/v1/mcp/health: "enabled": true and twelve tools listed means the server is up; "enabled": false means the agent surface is paused on our side and every call answers 503 until it returns. A 403 forbidden_scope names the missing scope in the response; a key created with fewer scopes needs a new key with the scope it lacks.

Q: Grok refuses the MCP server URL

The server URL is exactly https://api.zortix.app/v1/mcp — https, no trailing slash, no /health, no /sse. Grok speaks Streamable HTTP to it. The key goes in as the bearer token on the connector, not as a custom header and not in the URL. If the form still refuses it, open https://api.zortix.app/v1/mcp/health in a browser: a JSON answer with "status": "ok" means the endpoint is reachable and the problem is the URL or the token as typed; no answer means our side, and we are on it. Once connected, run zortix_get_daily_digest as the first call; it works on every plan and needs no follows to answer.

A connector key lets the agent you already use act for your Zortix account: your digest, search, follows, saved ideas and Ask Zortix, under your own plan limits. This page is the walkthrough and the fixes. The overview, the Free and Premium table and the agent links are on /connectors.

Before you start

Sign in and open Settings → Connectors. Create a key named after the agent it is for. The key is shown once; store it in the agent’s credential vault as ZORTIX_API_KEY, not in a chat.
A free account works: the digest, search, ticker mentions and shows are unlimited on every plan. Full idea reads and Ask questions are three a day on Free.
Following at least one show makes the digest yours. With no follows the digest says so and lists eight shows to start with.

Muse

Create the key. Store it in Muse’s credential vault as ZORTIX_API_KEY.
Paste this prompt into Muse (Settings shows the same one naming your key):

Muse

Build a custom connector for Zortix.
Read https://www.zortix.app/connectors/muse.md first.
MCP: https://api.zortix.app/v1/mcp
OpenAPI: https://api.zortix.app/v1/agent/openapi.json
Auth: Authorization Bearer with the secret ZORTIX_API_KEY.
After connecting, fetch today's digest for my account and summarise the depth 4+ ideas with citations.

Muse reads the brief, builds the connector from the MCP URL (or the OpenAPI document), and fetches your digest. Ask it for the depth 4+ ideas with citations; ask what Odd Lots said about private credit; ask it to watch a ticker every morning.

Grok

Create the key.
In Grok, open Connectors → New → Custom. Server URL https://api.zortix.app/v1/mcp, the key as the bearer token.
Or paste this prompt and let Grok do it:

Grok

Add a custom MCP connector.
Server URL: https://api.zortix.app/v1/mcp
Use my Zortix API key as a bearer token.
Then run zortix_get_daily_digest.

The first call is zortix_get_daily_digest; it answers on every plan. The Grok brief lists every tool.

A Grokbot routine

Once the connector is on, a Grokbot routine can run a prompt on a schedule. The one that works from the digest alone: “Brief me on overnight ideas from my Zortix shows, depth 4 and up, with the risks and timestamps.” The digest card carries the headline, the thesis, the stance word, the show, the episode date, the timestamp and the permalink, so the routine needs no second call and never opens a full read unasked.

When something fails

Four answers cover nearly every message we get. Each is the reply support sends, so you can copy it to the person who asked or read it yourself.

The agent says 401, "unauthorized", or "key missing or revoked"

Every call answers 401 unauthorized. The agent may say the key is invalid or that it needs to reconnect.

Reply · key 401

A 401 means Zortix did not accept the key the agent sent: it is missing, mistyped, or was revoked.

Open https://web.zortix.app/settings/connectors. If the key the agent uses is listed under "revoked", create a new one; if it is live, the agent is sending something else — re-paste the key into the agent's credential vault (Muse: the secret named ZORTIX_API_KEY; Grok: the bearer token on the connector).

Keys start with zk_live_ and are shown once at creation. If you no longer have it, revoke it and create another; the old one stops on the next request.

Nothing about your account has changed and nothing was lost.

The agent says 402, "limit", or "upgrade"

A call answers 402 with idea_read_limit, ask_limit, follow_limit, save_limit or premium_required, and a link.

Reply · plan 402

A 402 is a plan limit, not an error: the connector runs on the same meters as the app.

On the free plan: three full idea reads and three Ask questions per UTC day, fifteen followed shows, ten followed tickers, ten saved ideas. The source moment (the transcript quote and audio pointer) is Premium.

Day-scoped limits reset at UTC midnight; the answer carries resetsAt. Premium removes every one of them: https://web.zortix.app/premium?utm_source=connector

The digest, search, ticker mentions, shows, your follows list and your profile stay unlimited on both plans — the agent can keep going with those.

Muse connects but "can't find tools" or only sees two

Muse lists no Zortix tools, or only thesis_history and ticker_stance_timeline, or every personal call answers 403 forbidden_scope.

Reply · muse no tools

Muse shows the tools the key's scopes allow. Two tools means the key was sent without an account behind it (a free-tier key from /developers, not a connector key) or was not sent at all.

Create a connector key at https://web.zortix.app/settings/connectors (it holds every scope by default) and store it in Muse's credential vault as ZORTIX_API_KEY, then rebuild the connector from https://api.zortix.app/v1/mcp.

Check https://api.zortix.app/v1/mcp/health: "enabled": true and twelve tools listed means the server is up; "enabled": false means the agent surface is paused on our side and every call answers 503 until it returns.

A 403 forbidden_scope names the missing scope in the response; a key created with fewer scopes needs a new key with the scope it lacks.

Grok refuses the MCP server URL

Grok's custom connector form rejects the URL, or the connector is added but every tool call fails.

Reply · grok url refused

The server URL is exactly https://api.zortix.app/v1/mcp — https, no trailing slash, no /health, no /sse. Grok speaks Streamable HTTP to it.

The key goes in as the bearer token on the connector, not as a custom header and not in the URL.

If the form still refuses it, open https://api.zortix.app/v1/mcp/health in a browser: a JSON answer with "status": "ok" means the endpoint is reachable and the problem is the URL or the token as typed; no answer means our side, and we are on it.

Once connected, run zortix_get_daily_digest as the first call; it works on every plan and needs no follows to answer.

Still stuck

Check the health endpoint first: it says whether the agent surface is on and lists every tool. Then write to hello@zortix.app with the key’s name (never the key), the agent, and the exact sentence the agent showed you.