SF Compute (BYOK)

SF Compute (BYOK) — connector documentation

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

What SF Compute (BYOK) is for

SF Compute (BYOK) lets an AI assistant read your own SF Compute data through the SF Compute API with a key you supply (SF Compute API token (sk_live_...) with read grants). Read-only: 11 tools (list_instances, get_instance, list_pools, get_pool, list_orders, get_order, list_skus, list_sku_availability, list_workspaces, list_images, list_pool_transfers). 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.sfcompute.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SF Compute. SF Compute 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 SF Compute GPU instances are running?"
• "What state is SF Compute instance inst_1 in?"
• "How many GPU nodes do my SF Compute pools hold over time?"
• "What is the allocation of SF Compute pool pool_1?"
• "What compute orders did I place on SF Compute?"
• "What happened with SF Compute order ord_1?"

What it does

• list_instances: List GPU instances with state (awaiting_allocation, running, terminated, failed), SKU, image, private IP and creation time.
• get_instance: Get one instance by id or name: state, SKU, image, private IP, public IP flag and creation time.
• list_pools: List pools (buckets of compute allocation over time) with their allocation schedule by node count.
• get_pool: Get one pool by id, resource path or name with its allocation schedule.
• list_orders: List buy and sell orders for compute time with side, state, SKU, limit price per node-hour and fills.
• get_order: Get one order by id with side, state, SKU, limit price, schedule and fills.
• list_skus: List the hardware SKUs offered with region, accelerator, form factor, vCPUs, memory and storage.
• list_sku_availability: List purchasable capacity per SKU over time (node counts by start and end time).
• list_workspaces: List the workspaces (resource containers) of your account.
• list_images: List machine images in a workspace with public flag and upload status.
• list_pool_transfers: List transfers of compute allocation between pools with status and SKU.

BYOK key

You bring your own SF Compute SF Compute API token (sk_live_...) with read grants (https://docs.sfcompute.com/preview/tokens). 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.sfcompute.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://docs.sfcompute.com/preview/using-the-api (the API this connector calls, with a BYOK key)

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

Built for: Worldwide. Languages: English.

SF Compute (BYOK) — Privacy Policy

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

What SF Compute (BYOK) is. SF Compute (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own SF Compute data: Read your SF Compute GPU instances, pools, orders, SKUs, availability, images and workspaces with your own API token. You bring your own SF Compute SF Compute API token (sk_live_...) with read grants; the assistant sends it to us with each request.

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

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

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

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

SF Compute (BYOK) — Terms of Service

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

1. The Service. SF Compute (BYOK) provides: Read your SF Compute GPU instances, pools, orders, SKUs, availability, images and workspaces 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 SF Compute credentials and only access data you are allowed to access. SF Compute's terms apply to your use of SF Compute; 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 SF Compute. SF Compute 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 SF Compute returns, lightly trimmed; it may be incomplete, delayed or changed by SF Compute. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your SF Compute 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 SF Compute'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; SF Compute 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 SF Compute 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 SF Compute 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-sfcompute

SF Compute (BYOK) support

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

• MCP endpoint: https://byok-sfcompute.connectorbay.com/mcp
• REST API: https://byok-sfcompute.connectorbay.com/openapi.json
• Live status: https://byok-sfcompute.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. SF Compute (BYOK) never asks for them.