Integrations
Talk to your fleet
TechMedix is an authenticated OpenAPI connector. Point Muse — or any assistant that speaks OpenAPI — at the spec below and query fleet health, alerts, failure modes, repair protocols, AR guidance, and parts in natural language. No SDK, no directory review.
OpenAPI 3.1 · Bearer auth · per-customer keys. The same spec powers the reviewed Muse connector submission.
What you can ask
“How's my fleet doing right now?” — every robot with its latest alert and open work order.
“Show me active alerts across the fleet.” — filter by status and robot, newest first.
“What are the known failure modes for the Unitree H1?” — documented signatures per platform.
“Give me the repair protocol for knee actuator drift on the H1.” — step-by-step.
“I need AR repair guidance for H1-07's left knee actuator.” — overlay instructions + confidence.
“Find me a replacement knee actuator for the H1, in stock in the US.” — matching parts + suppliers.
“Run a diagnostic analysis on platform unitree-h1 with this telemetry.” — a scored report.
“Create a work order for H1-07's actuator fault, high priority.” — confirms first, idempotent.
Connect in three steps
Get an API key
Sign in to the TechMedix dashboard → Settings → API keys → Mint key. The key is shown once — save it immediately. It starts with tmdx_live_.
Paste the setup prompt into Muse
Muse builds the connector from the published spec and asks for your key. Copy the prompt, fill in your customer ID, and paste it in.
I want to connect TechMedix (AI maintenance intelligence for my robot fleet) as a custom connector. The OpenAPI spec is at https://blackcatrobotics.com/.well-known/techmedix-openapi.yaml Build the connector from that spec. Then ask me for my TechMedix API key (it starts with tmdx_live_) and store it securely — send it as Authorization: Bearer <key> on every call. My customer ID is: _____ Rules: - Read tools (fleet_status, alerts_list, platform_catalog, diagnose, ar_guidance, parts_advisor, tasks_list) need no confirmation. - Write tools (dispatch_create, alert_resolve, task_create) ALWAYS need my explicit confirmation first. - When creating a dispatch or task, generate a UUID and send it as the Idempotency-Key header so retries never duplicate work. - Never claim a payment, telemetry ingestion, or robot-control capability — the connector can't do those.
Ask
“How's my fleet doing right now?” Read tools run immediately; write tools (create work order, resolve alert, add task) always ask for your confirmation first.
Frequently asked
Do I need a directory listing to connect TechMedix?
No. Any Muse user can connect TechMedix today as a Custom Connector — point Muse at the OpenAPI spec at blackcatrobotics.com/.well-known/techmedix-openapi.yaml and paste the setup prompt. A reviewed directory listing is in progress.
How is the connection authenticated?
With a per-customer Bearer API key issued in the TechMedix dashboard. The key is bound to your customer ID server-side, so it can never read another customer's fleet. Only a SHA-256 hash of the key is stored; the full key is shown once at mint time.
Can the connector place orders or control my robots?
No. The connector cannot process payments, ingest raw device telemetry, or modify robot firmware. Payment checkout stays on the website and telemetry uses a separate ingestion firehose. Write actions (creating a work order, resolving an alert, adding a task) always require your explicit confirmation.
Are retries safe?
Yes. Work-order and task creation honor an Idempotency-Key header, so a retried request never creates duplicate work.
Muse directory listing — in review
The reviewed Muse connector submission (functional, security, and legal review by Meta) is prepared and queued. Until it lists, the Custom Connector path above gets you connected today.