Agent contract

The page is the front door. The row is the API.

Agents do not start at an API. They start at a search result or a page, read it, and then call a tool. FaultDesk is built so the same row works for both.

What is live now

Static JSON is generated with the site. No key, no rate limit, no auth:

EndpointReturns
/api/codes.jsonAll 188 rows
/api/tajima.jsonAll Tajima rows
/api/barudan.jsonAll Barudan rows
/api/swf.jsonAll SWF rows
/api/codes/tajima/3a6.jsonOne row
/llms.txtThe site summary for language models
/mcpHosted MCP: diagnose_fault, lookup_code, list_brands
/v1/diagnosePaid row + citation (API key or x402)

Example row

{
  "brand": "Tajima",
  "code": "3A6",
  "kind": "error",
  "meaning": "Incorrect ATH movable knife retract position",
  "checks": [
    "Check the position of the ATH movable knife"
  ],
  "systems": [
    "trimmer"
  ],
  "source": "https://www.theembroiderywarehouse.com/errorlist.pdf",
  "updated": "2026-11-18"
}

MCP endpoint

The hosted endpoint is live at https://faultdesk.kasafox.com/mcp: JSON-RPC 2.0 over HTTP, no key, no auth. It exposes diagnose_fault, lookup_code, and list_brands. A stdio copy is in the repo (python3 scripts/mcp_server.py). The input is deliberately small: an agent usually knows the brand and the code on the display.

POST https://faultdesk.kasafox.com/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "diagnose_fault",
    "arguments": {
      "brand": "Tajima",
      "code": "3A6"
    }
  }
}
{
  "name": "diagnose_fault",
  "description": "Look up an embroidery machine error code and return the meaning, manual checks, systems involved, and source.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "brand": {
        "type": "string",
        "enum": [
          "Tajima",
          "Barudan",
          "SWF"
        ]
      },
      "model": {
        "type": "string",
        "description": "Optional model or series"
      },
      "code": {
        "type": "string",
        "description": "The code shown on the machine"
      },
      "symptom": {
        "type": "string",
        "description": "Optional free-text symptom"
      }
    },
    "required": [
      "brand",
      "code"
    ]
  }
}

Paid API

POST https://faultdesk.kasafox.com/v1/diagnose returns the same row plus a citation block. Send an API key in Authorization: Bearer or X-API-Key. Agents with a wallet can use x402 v2: the 402 carries accepts for exact on eip155:8453 (USDC on Base), the client retries with PAYMENT-SIGNATURE, and a settled response carries PAYMENT-RESPONSE. Without either, the endpoint returns 401 (or 402 when x402 is on).

POST https://faultdesk.kasafox.com/v1/diagnose
Authorization: Bearer <key>
Content-Type: application/json

{
  "brand": "Tajima",
  "code": "3A6"
}

Why an agent should trust it

Each row carries a source URL, a last-checked date, a confidence flag, and the manual’s checks. The paid endpoint returns the same fields plus a machine-readable citation block. The point is not to replace the manual; it is to give the agent a citable row instead of a hallucinated guess.

What comes next

Current status: the static JSON, llms.txt, the local stdio MCP server, the hosted /mcp endpoint, and the paid /v1/diagnose endpoint are live. x402 v2 is live with PayAI as the primary facilitator; a CDP fallback is one env pair away. Dealer white-label is the next build.