Spike.sh (BYOK)

Spike.sh (BYOK) — connector documentation

• MCP endpoint: https://byok-spike-sh.connectorbay.com/mcp
• REST API: POST https://byok-spike-sh.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-spike-sh.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Spike.sh Spike API key, sent in the X-Upstream-Key header and the Spike team _id (24 hex characters, not the short uid); most calls are scoped to one team in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-spike-sh.connectorbay.com/health · Tool schemas: https://byok-spike-sh.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-spike-sh · agent@connectorbay.com

What Spike.sh (BYOK) is for

Spike.sh (BYOK) lets an AI assistant read your own Spike.sh data through the Spike.sh API with a key you supply (Spike API key). Read-only: 12 tools (list_teams, list_incidents, get_incident, list_incident_occurrences, list_services, get_service, list_integrations, list_escalations, list_alert_rules, list_on_call_schedules, list_status_pages, list_status_page_components). 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.spike.sh. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Spike.sh. Spike.sh 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 Spike teams exist?"
• "Which Spike incidents are open?"
• "Show Spike incident ab12-17"
• "What incidents did Spike record last week?"
• "Which services are set up in Spike?"
• "How many open incidents does Spike service 3 have?"

What it does

• list_teams: List all teams in the organization with id, name, short uid and privacy flag. Use a returned _id as the team id of this connector.
• list_incidents: List the team's incidents with status (NACK triggered, ACK acknowledged, RES resolved), priority, severity and times, plus counts of total and open incidents.
• get_incident: Get one incident by counterId (for example ab12-17): message, status, priority, severity, times and duration.
• list_incident_occurrences: List incident occurrences in a time window across teams, filterable by status, service and integration. Paged.
• list_services: List the team's services (scopes that group integrations and incidents) with name, description and counter id.
• get_service: Get one service by counter id with the number of its open incidents.
• list_integrations: List the team's alert integrations with name, type slug, linked service and escalation ids and creation time (tokens and webhook URLs are left out).
• list_escalations: List the team's escalation policies (names and ids).
• list_alert_rules: List the team's alert routing rules with name, enabled flag and creation time.
• list_on_call_schedules: List the team's on-call schedules with timezone and active flag (the people in them are not returned).
• list_status_pages: List the organization's status pages with name, custom domain and creation time.
• list_status_page_components: List all components of a status page with current status (operational, degraded-performance, partial-outage, critical-outage, planned-maintenance), parent and order.

BYOK key

You bring your own Spike.sh Spike API key (https://app.spike.sh/api). 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.spike.sh 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.

Notices

Read-only. User details, integration tokens and webhook URLs are left out of every answer.

Data sources

• https://docs.spike.sh/spike-api-docs/getting-started (the API this connector calls, with a BYOK key)

Live from the Spike.sh API (api.spike.sh) with a BYOK key; documentation: https://docs.spike.sh/spike-api-docs/getting-started. 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 Spike.sh. Spike.sh 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 Spike.sh account.

Built for: Worldwide. Languages: English.

Spike.sh (BYOK) — Privacy Policy

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

What Spike.sh (BYOK) is. Spike.sh (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Spike.sh data: Read your Spike.sh incidents, services, escalation policies, alert rules, on-call schedules and status pages with your own API key and team id. You bring your own Spike.sh Spike API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Spike.sh 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.spike.sh, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Spike.sh 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 Spike.sh receives. The request we make on your behalf, including the key and the arguments, under Spike.sh's own terms and privacy policy. Spike.sh acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

Spike.sh (BYOK) — Terms of Service

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

1. The Service. Spike.sh (BYOK) provides: Read your Spike.sh incidents, services, escalation policies, alert rules, on-call schedules and status pages with your own API key and team id. 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 Spike.sh credentials and only access data you are allowed to access. Spike.sh's terms apply to your use of Spike.sh; 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 Spike.sh. Spike.sh 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 Spike.sh returns, lightly trimmed; it may be incomplete, delayed or changed by Spike.sh. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Spike.sh 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 Spike.sh'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; Spike.sh 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 Spike.sh 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 Spike.sh 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-spike-sh

Spike.sh (BYOK) support

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

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