Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Zealy (BYOK) icon

Zealy (BYOK)

Read your Zealy community info, leaderboards, sprints, quests, modules, reviews and member XP with your own API key

Unify Dynamics LLC

Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderZealyunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

How many members does the Zealy community 'join' have?
Tools called
get_community
Who is at the top of the Zealy leaderboard of 'join'?
Tools called
get_leaderboard
Which sprint is running in the Zealy community 'join'?
Tools called
list_sprints
Which quests does the Zealy community 'join' have and how often were they claimed?
Tools called
list_quests
What modules are in the Zealy community 'join'?
Tools called
list_modules
Which Zealy submissions in 'join' are still pending review?
Tools called
list_reviews

About

Zealy (BYOK) lets an AI assistant read your own Zealy data through the Zealy API with a key you supply (Zealy API key (read-only scope is enough)). Read-only: 8 tools (get_community, get_leaderboard, list_sprints, list_quests, list_modules, list_reviews, get_member, get_member_review_marks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api-v2.zealy.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Zealy. Zealy and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Zealy API (api-v2.zealy.io) with a BYOK key; documentation: https://docs.zealy.io/authentication. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

8 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data8 tools
  • Get communityGet basic public info about a community: name, subdomain, sector, blockchain, type and total member count.
  • Get leaderboardGet the leaderboard of a community (all-time, or one sprint) with rank data: member name, XP and number of quests done.
  • List sprintsList the leaderboard sprints of a community with name, start and end time and reward zone; use onlyCurrent to get just the running one.
  • List questsList the quests of a community (needs an admin key) with name, publish and archive flags, recurrence, claim limit, claim count and last update.
  • List modulesList the modules (quest categories) of a community with name, colour and position.
  • List reviewsList quest submissions (reviews) of a community with status, star or flag mark, user name, quest name and time.
  • Get memberGet one community member by Zealy user ID: name, XP, level, rank, role, ban flag, referrer and sign-up time.
  • Get member review marksGet how many stars and flags a member received on reviewed submissions in a community.

Information

PublisherUnify Dynamics LLC
CategoryMoney & business
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-zealy.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 8 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-zealy.connectorbay.com/mcp
RESTPOST https://byok-zealy.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-zealy.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Zealy API key (read-only scope is enough) in the X-Upstream-Key header (get one at docs.zealy.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

Zealy connector: questions and answers

What is the Zealy connector?

Zealy (BYOK) lets an AI assistant read your own Zealy data through the Zealy API with a key you supply (Zealy API key (read-only scope is enough)). It is a hosted MCP server with 8 tools such as Get community, Get leaderboard, List sprints, List quests, List modules, List reviews, published by Unify Dynamics LLC. It is independent and not affiliated with Zealy.

How do I connect Zealy to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-zealy.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-zealy.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-zealy.json.

Do I need a Zealy account or API key?

Yes: this is a bring-your-own-key connector. Create a Zealy API key (read-only scope is enough) at https://docs.zealy.io/authentication and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Zealy read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Zealy connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Logicbroker (BYOK)

Read your Logicbroker drop-ship and EDI documents: orders, acknowledgements, shipments, invoices, supplier stock availability, events and webhooks, with your own API key

Live · MCP + REST11 tools

Loyverse (BYOK)

Read your Loyverse point-of-sale stores, items, inventory, receipts, shifts and staff with your own access token

Live · MCP + REST12 tools

Loyverse Setup (BYOK)

Read your Loyverse POS tax rates, discounts, modifiers, POS devices, suppliers and store details with your own access token

Live · MCP + REST11 tools

Lunch Money (BYOK)

Read your Lunch Money budget: accounts and balances, transactions, categories, tags, recurring items, budget settings and spending summary with your own access token

Live · MCP + REST10 tools

MailChannels (BYOK)

Read your MailChannels email metrics, usage, suppression list, sub-accounts, DKIM keys, tracking domains and webhooks with your own API key

Live · MCP + REST11 tools

Mailjet (BYOK)

Read your Mailjet contacts, contact lists, campaigns, campaign statistics, messages, senders and templates with your own API key and secret

Live · MCP + REST9 tools

Documentation

Back to top

Zealy (BYOK) — connector documentation

  • MCP endpoint: https://byok-zealy.connectorbay.com/mcp
  • REST API: POST https://byok-zealy.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-zealy.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Zealy Zealy API key (read-only scope is enough), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-zealy.connectorbay.com/health · Tool schemas: https://byok-zealy.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-zealy · agent@connectorbay.com

What Zealy (BYOK) is for

Zealy (BYOK) lets an AI assistant read your own Zealy data through the Zealy API with a key you supply (Zealy API key (read-only scope is enough)). Read-only: 8 tools (get_community, get_leaderboard, list_sprints, list_quests, list_modules, list_reviews, get_member, get_member_review_marks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api-v2.zealy.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Zealy. Zealy and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "How many members does the Zealy community 'join' have?"
  • "Who is at the top of the Zealy leaderboard of 'join'?"
  • "Which sprint is running in the Zealy community 'join'?"
  • "Which quests does the Zealy community 'join' have and how often were they claimed?"
  • "What modules are in the Zealy community 'join'?"
  • "Which Zealy submissions in 'join' are still pending review?"

What it does

  • get_community: Get basic public info about a community: name, subdomain, sector, blockchain, type and total member count.
  • get_leaderboard: Get the leaderboard of a community (all-time, or one sprint) with rank data: member name, XP and number of quests done. Emails and wallet addresses are not returned.
  • list_sprints: List the leaderboard sprints of a community with name, start and end time and reward zone; use onlyCurrent to get just the running one.
  • list_quests: List the quests of a community (needs an admin key) with name, publish and archive flags, recurrence, claim limit, claim count and last update.
  • list_modules: List the modules (quest categories) of a community with name, colour and position.
  • list_reviews: List quest submissions (reviews) of a community with status, star or flag mark, user name, quest name and time. Task answers are not returned. Needs a reviewer or admin key; page with nextCursor.
  • get_member: Get one community member by Zealy user ID: name, XP, level, rank, role, ban flag, referrer and sign-up time. Email, wallet and social handles are not returned.
  • get_member_review_marks: Get how many stars and flags a member received on reviewed submissions in a community.

BYOK key

You bring your own Zealy Zealy API key (read-only scope is enough) (https://docs.zealy.io/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api-v2.zealy.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Zealy API (api-v2.zealy.io) with a BYOK key; documentation: https://docs.zealy.io/authentication. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Zealy. Zealy and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Zealy account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Zealy (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Zealy (BYOK) is. Zealy (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Zealy data: Read your Zealy community info, leaderboards, sprints, quests, modules, reviews and member XP with your own API key. You bring your own Zealy Zealy API key (read-only scope is enough); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Zealy call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api-v2.zealy.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Zealy rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Zealy receives. The request we make on your behalf, including the key and the arguments, under Zealy's own terms and privacy policy. Zealy acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Zealy gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Zealy data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Zealy (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Zealy at any time to end all access.

Children. Zealy (BYOK) is a general-audience service operated by the adult using the assistant, under Zealy's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Zealy (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Zealy (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Zealy (BYOK) provides: Read your Zealy community info, leaderboards, sprints, quests, modules, reviews and member XP with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Zealy credentials and only access data you are allowed to access. Zealy's terms apply to your use of Zealy; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Zealy. Zealy and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Zealy returns, lightly trimmed; it may be incomplete, delayed or changed by Zealy. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Zealy account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Zealy's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Zealy may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Zealy key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Zealy takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-zealy

Zealy (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Zealy (BYOK) never asks for them.

Get Zealy (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Zealy Zealy API key (read-only scope is enough). Create one at https://docs.zealy.io/authentication, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Zealy. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Zealy.