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

Okareo (BYOK)

Read your Okareo projects, registered models and agents under test, evaluation checks, scenario sets, simulation drivers and test runs with your own API token

Unify Dynamics LLC

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

Try asking

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

Which Okareo projects does my organization have?
Tools called
list_projects
Which models and agents are registered in Okareo?
Tools called
list_models_under_test
Show Okareo model under test 6f1b8d0e
Tools called
get_model_under_test
Which evaluation checks are available in Okareo?
Tools called
list_checks
Describe Okareo check 6f1b8d0e
Tools called
get_check
What scenario sets exist in Okareo?
Tools called
list_scenario_sets

About

Okareo (BYOK) lets an AI assistant read your own Okareo data through the Okareo API with a key you supply (Okareo API token). Read-only: 9 tools (list_projects, list_models_under_test, get_model_under_test, list_checks, get_check, list_scenario_sets, list_drivers, get_test_run, list_available_target_models). 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.okareo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Okareo. Okareo and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Okareo API (api.okareo.com) with a BYOK key; documentation: https://docs.okareo.com/docs/api/get-all-projects-v-0-projects-get. 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

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

OpenAPI
Read your data9 tools
  • List projectsList the organization's Okareo projects with onboarding status, tags and number of evaluations.
  • List models under testList registered models and agents under test with version, tags, datapoint count and app link, optionally for one project.
  • Get model under testGet one registered model or agent under test by id: name, version, tags, datapoint count and app link.
  • List checksList evaluation checks (predefined and custom) with description, output type, version and tags; code is not returned.
  • Get checkGet one evaluation check by id: name, description, output type, version and tags (code is not returned).
  • List scenario setsList scenario sets (test inputs) with name, type, scenario count, tags and app link; the scenario rows are not returned.
  • List driversList simulation drivers with name, temperature, model id and creation time (prompt templates are not returned).
  • Get test runGet one evaluation test run by id: status, type, timing, datapoint count, progress and app link.
  • List available target modelsList the target models Okareo can evaluate against, with provider and model names.

Information

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

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-okareo.connectorbay.com/mcp
RESTPOST https://byok-okareo.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-okareo.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 Okareo API token in the X-Upstream-Key header (get one at app.okareo.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Okareo connector: questions and answers

What is the Okareo connector?

Okareo (BYOK) lets an AI assistant read your own Okareo data through the Okareo API with a key you supply (Okareo API token). It is a hosted MCP server with 9 tools such as List projects, List models under test, Get model under test, List checks, Get check, List scenario sets, published by Unify Dynamics LLC. It is independent and not affiliated with Okareo.

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

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

Do I need a Okareo account or API key?

Yes: this is a bring-your-own-key connector. Create a Okareo API token at https://app.okareo.com 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 Okareo read-only?

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

Is the Okareo 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

Insta WP (BYOK)

Read your InstaWP WordPress sites, plans, templates, snapshots, teams, tags, WP-CLI commands and domain pricing and DNS with your own API token

Live · MCP + REST11 tools

Integrate.io (BYOK)

Read your Integrate.io ELT and ETL pipelines: clusters, packages, jobs and run status, schedules, connections and hooks with your own API key

Live · MCP + REST11 tools

Interlynk (BYOK)

Read your Interlynk SBOM products, versions, components, vulnerabilities and VEX statuses with your own security token

Live · MCP + REST8 tools

IONOS Certificate Manager (BYOK)

Read your IONOS Cloud TLS certificates, automatic certificates and ACME providers (Frankfurt endpoint) with your own IONOS API token

Live · MCP + REST5 tools

IONOS Cloud (BYOK)

Read your IONOS Cloud data centers, servers, volumes, snapshots, IP blocks, LANs, Kubernetes clusters and contract limits with your own API token

Live · MCP + REST12 tools

IONOS Container Registry (BYOK)

Read your IONOS Cloud private container registries, repositories, image artifacts and vulnerability counts with your own API token

Live · MCP + REST5 tools

Documentation

Back to top

Okareo (BYOK) — connector documentation

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

What Okareo (BYOK) is for

Okareo (BYOK) lets an AI assistant read your own Okareo data through the Okareo API with a key you supply (Okareo API token). Read-only: 9 tools (list_projects, list_models_under_test, get_model_under_test, list_checks, get_check, list_scenario_sets, list_drivers, get_test_run, list_available_target_models). 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.okareo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Okareo. Okareo 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:

  • "Which Okareo projects does my organization have?"
  • "Which models and agents are registered in Okareo?"
  • "Show Okareo model under test 6f1b8d0e"
  • "Which evaluation checks are available in Okareo?"
  • "Describe Okareo check 6f1b8d0e"
  • "What scenario sets exist in Okareo?"

What it does

  • list_projects: List the organization's Okareo projects with onboarding status, tags and number of evaluations.
  • list_models_under_test: List registered models and agents under test with version, tags, datapoint count and app link, optionally for one project.
  • get_model_under_test: Get one registered model or agent under test by id: name, version, tags, datapoint count and app link.
  • list_checks: List evaluation checks (predefined and custom) with description, output type, version and tags; code is not returned.
  • get_check: Get one evaluation check by id: name, description, output type, version and tags (code is not returned).
  • list_scenario_sets: List scenario sets (test inputs) with name, type, scenario count, tags and app link; the scenario rows are not returned.
  • list_drivers: List simulation drivers with name, temperature, model id and creation time (prompt templates are not returned).
  • get_test_run: Get one evaluation test run by id: status, type, timing, datapoint count, progress and app link.
  • list_available_target_models: List the target models Okareo can evaluate against, with provider and model names.

BYOK key

You bring your own Okareo Okareo API token (https://app.okareo.com). 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.okareo.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.

Data sources

Live from the Okareo API (api.okareo.com) with a BYOK key; documentation: https://docs.okareo.com/docs/api/get-all-projects-v-0-projects-get. 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 Okareo. Okareo 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 Okareo account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Okareo (BYOK) — Privacy Policy

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

What Okareo (BYOK) is. Okareo (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Okareo data: Read your Okareo projects, registered models and agents under test, evaluation checks, scenario sets, simulation drivers and test runs with your own API token. You bring your own Okareo Okareo API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Okareo 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.okareo.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 Okareo 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 Okareo receives. The request we make on your behalf, including the key and the arguments, under Okareo's own terms and privacy policy. Okareo acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Okareo 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 Okareo 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. Okareo (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 Okareo at any time to end all access.

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

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

Terms of service

Back to top

Okareo (BYOK) — Terms of Service

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

  1. The Service. Okareo (BYOK) provides: Read your Okareo projects, registered models and agents under test, evaluation checks, scenario sets, simulation drivers and test runs with your own API token. 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 Okareo credentials and only access data you are allowed to access. Okareo's terms apply to your use of Okareo; 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 Okareo. Okareo 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 Okareo returns, lightly trimmed; it may be incomplete, delayed or changed by Okareo. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Okareo 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 Okareo'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; Okareo 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 Okareo 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 Okareo 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-okareo

Okareo (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. Okareo (BYOK) never asks for them.

Get Okareo (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Okareo Okareo API token. Create one at https://app.okareo.com, 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 Okareo. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Okareo.