Juro (BYOK)

Juro (BYOK) — connector documentation

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

What Juro (BYOK) is for

Juro (BYOK) lets an AI assistant read your own Juro data through the Juro API with a key you supply (Juro API key). Read-only: 5 tools (check_api_access, list_templates, get_template, list_contracts, get_contract). 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.juro.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Juro. Juro 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:

• "Is my Juro API key working?"
• "Which contract templates do we have in Juro?"
• "Show the details of Juro template 5de9227402e24204247757c4"
• "Which Juro contracts were updated since 1 January 2026?"
• "What is the status of Juro contract 5de92ae0bb0bf42c5ce2fe7c?"

What it does

• check_api_access: Check that the Juro API key is valid and the API is reachable; returns a short status message.
• list_templates: List the contract templates in the Juro account with id, name, status (published or edit in progress) and dates.
• get_template: Get one Juro template: name, status, dates, its questions, fields and signing sides.
• list_contracts: List contracts with id, name, template, workspace and dates, newest first as returned by Juro; filter by update time, workspace or template.
• get_contract: Get one Juro contract: name, status (draft, sent for signing, fully signed and so on), owner, template, dates and field values.

BYOK key

You bring your own Juro Juro API key (https://app.juro.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.juro.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

• https://api-docs.juro.com/ (the API this connector calls, with a BYOK key)

Live from the Juro API (api.juro.com) with a BYOK key; documentation: https://api-docs.juro.com/. 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 Juro. Juro 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 Juro account.

Built for: Worldwide. Languages: English.

Juro (BYOK) — Privacy Policy

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

What Juro (BYOK) is. Juro (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Juro data: Read your Juro contract templates and contracts, with status, owner and dates, using your own API key. You bring your own Juro Juro API key; the assistant sends it to us with each request.

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

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

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

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

Juro (BYOK) — Terms of Service

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

1. The Service. Juro (BYOK) provides: Read your Juro contract templates and contracts, with status, owner and dates, using 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 Juro credentials and only access data you are allowed to access. Juro's terms apply to your use of Juro; 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 Juro. Juro 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 Juro returns, lightly trimmed; it may be incomplete, delayed or changed by Juro. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Juro 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 Juro'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; Juro 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 Juro 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 Juro 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-juro

Juro (BYOK) support

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

• MCP endpoint: https://byok-juro.connectorbay.com/mcp
• REST API: https://byok-juro.connectorbay.com/openapi.json
• Live status: https://byok-juro.connectorbay.com/health

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