Braze (BYOK)
Read your Braze campaigns, Canvases, segments, custom events, user trend series and email templates with your own REST API key
Read your Credly organization's digital badge templates, issued-badge states and counts, and recommendations with your own authorization token
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_organizationlist_badge_templatesget_badge_templatelist_issued_badgesget_issued_badgelist_recommendationsCredly (BYOK) lets an AI assistant read your own Credly data through the Credly API with a key you supply (Credly organization authorization token). Read-only: 6 tools (get_organization, list_badge_templates, get_badge_template, list_issued_badges, get_issued_badge, list_recommendations). 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.credly.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Credly. Credly and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Credly API (api.credly.com) with a BYOK key; documentation: https://docs.credly.com/browse/docs/getting-started. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
6 tools, grouped by job. Every one is read-only or compute-only.
https://byok-credly.connectorbay.com/mcpThree ways in, the same 6 tools.
https://byok-credly.connectorbay.com/mcpPOST https://byok-credly.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-credly.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at docs.credly.com).Credly (BYOK) lets an AI assistant read your own Credly data through the Credly API with a key you supply (Credly organization authorization token). It is a hosted MCP server with 6 tools such as Get organization, List badge templates, Get badge template, List issued badges, Get issued badge, List recommendations, published by Unify Dynamics LLC. It is independent and not affiliated with Credly.
Add the MCP endpoint https://byok-credly.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-credly.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-credly.json.
Yes: this is a bring-your-own-key connector. Create a Credly organization authorization token at https://docs.credly.com/browse/docs/authentication-methods and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Braze campaigns, Canvases, segments, custom events, user trend series and email templates with your own REST API key
Read your Breezy HR companies, positions, departments, hiring pipelines, questionnaires and message templates (no candidate data) with your own personal access token
Read your Brella event-networking data: events, schedule sessions, tracks, sponsors, ticket types, announcements and event, ticket-sales and session analytics with your own organization token
Read your Brevo account, contacts, lists, segments, email campaigns and their statistics, senders and templates with BYOK
Read your Brevo sending domain authentication status, dedicated IPs, webhooks, contact attribute definitions, folders and consent groups with your own API key (no contacts)
Read your Brevo SMS campaigns, WhatsApp campaigns and templates, WhatsApp account status and transactional SMS aggregate reports with your own API key (no recipients or message text)
https://byok-credly.connectorbay.com/mcpPOST https://byok-credly.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-credly.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-credly.connectorbay.com/health · Tool schemas: https://byok-credly.connectorbay.com/tools.jsonCredly (BYOK) lets an AI assistant read your own Credly data through the Credly API with a key you supply (Credly organization authorization token). Read-only: 6 tools (get_organization, list_badge_templates, get_badge_template, list_issued_badges, get_issued_badge, list_recommendations). 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.credly.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Credly. Credly 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:
get_organization: Show your Credly organization's profile: name, location, verification status, featured badge templates and whether it is a trial account.list_badge_templates: List the organization's badge templates with state, visibility, number of badges issued, level, time to earn and skills. Filter by state or name.get_badge_template: Get one badge template: description, state, visibility, issue counts, level, time to earn, skills and public URL.list_issued_badges: List badges issued by the organization with state, issue and expiry dates and their template. Recipient names and emails are left out of the answer. Filter by state, template or creation date.get_issued_badge: Get one issued badge by id: state, issue and expiry dates, visibility and its template. Recipient details are left out.list_recommendations: List the learning recommendations configured in the organization (title, type, linked template count and last update).You bring your own Credly Credly organization authorization token (https://docs.credly.com/browse/docs/authentication-methods). 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.credly.com 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.
Live from the Credly API (api.credly.com) with a BYOK key; documentation: https://docs.credly.com/browse/docs/getting-started. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Credly. Credly 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 Credly account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Credly (BYOK) is. Credly (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Credly data: Read your Credly organization's digital badge templates, issued-badge states and counts, and recommendations with your own authorization token. You bring your own Credly Credly organization authorization token; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Credly 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.credly.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Credly 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 Credly receives. The request we make on your behalf, including the key and the arguments, under Credly's own terms and privacy policy. Credly acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Credly 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 Credly 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. Credly (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 Credly at any time to end all access.
Children. Credly (BYOK) is a general-audience service operated by the adult using the assistant, under Credly's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Credly (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-credly.connectorbay.com/mcphttps://byok-credly.connectorbay.com/openapi.jsonWhen 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. Credly (BYOK) never asks for them.