All features

API & AI assistants

Ask an AI assistant about your own catalog

SpecLatch is an MCP server as well as a REST API. Connect Claude, Cursor or Copilot with an API key and ask in plain words. The assistant reads your published records through the same read-only endpoints your website would use, and the key's tier decides which fields it can see. Both come with the Growth plan and up.

Start your free trialAll features

30 days of Growth features · no credit card

AI assistant

connected over MCP with a Public key

Which close-coupled pumps deliver at least 250 GPM, and at what head?

Two published pumps deliver 250 GPM or more, both at 1,750 RPM:

ModelFlowHead
HC 4x3-10330 GPM · 75 m³/h84.8 ft · 25.8 m
HC 4x3-8260 GPM · 59.1 m³/h57.7 ft · 17.6 m
What do they list for?
I can't see a price. This key reads public fields only.

A third pump also delivers 260 GPM, but it is still in review. A public key reads published records only, so the assistant never hears of it.

returnedsearch_records· what the assistant read
{
  "records": [
    {
      "id": "rec_4x310",
      "tableId": "tbl_hc",
      "name": "HC 4x3-10 close-coupled pump, 1,750 RPM, bronze-fitted",
      "modelNumber": "HC-4X3-10-17-CI",
      "status": "PUBLISHED",
      "specs": [
        {
          "field": "bep_flow",
          "name": "Flow at BEP",
          "type": "UNIT_NUMBER",
          "value": 330,
          "unit": "GPM",
          "dual": {
            "imperial": { "value": 330, "unit": "GPM" },
            "metric": { "value": 74.9511533232, "unit": "m³/h" }
          }
        },
        {
          "field": "bep_head",
          "name": "Head at BEP",
          "type": "UNIT_NUMBER",
          "value": 84.8,
          "unit": "ft",
          "dual": {
            "imperial": { "value": 84.8, "unit": "ft" },
            "metric": { "value": 25.84704, "unit": "m" }
          }
        }
      ]
    },
    {
      "id": "rec_4x308",
      "tableId": "tbl_hc",
      "name": "HC 4x3-8 close-coupled pump, 1,750 RPM, bronze-fitted",
      "modelNumber": "HC-4X3-8-17-CI",
      "status": "PUBLISHED",
      "specs": [
        {
          "field": "bep_flow",
          "name": "Flow at BEP",
          "type": "UNIT_NUMBER",
          "value": 260,
          "unit": "GPM",
          "dual": {
            "imperial": { "value": 260, "unit": "GPM" },
            "metric": { "value": 59.0524238304, "unit": "m³/h" }
          }
        },
        {
          "field": "bep_head",
          "name": "Head at BEP",
          "type": "UNIT_NUMBER",
          "value": 57.7,
          "unit": "ft",
          "dual": {
            "imperial": { "value": 57.7, "unit": "ft" },
            "metric": { "value": 17.58696, "unit": "m" }
          }
        }
      ]
    }
  ],
  "page": {
    "limit": 50,
    "total": 2,
    "next": null
  }
}

Connected in one step

Create an API key in the workspace, pick its tier, and give it to the client. There is nothing to install on SpecLatch's side and nothing to export first: the assistant reads the published catalog where it lives.

Clients that connect over HTTP with a key work today. A sign-in flow for the assistants that cannot send one is planned.

The full reference, with every endpoint →

in a terminal

claude mcp add --transport http speclatch https://app.speclatch.com/api/mcp \
  --header "Authorization: Bearer $SPECLATCH_API_KEY"

Claude, Cursor and Visual Studio Code are trademarks of their respective owners. SpecLatch is not affiliated with them.

One record, two keys

The confidentiality you set on each field is the same rule here. A key carries a tier, and that tier is a ceiling: the API and the assistant behind it get the fields at or under it, and no trace of the rest.

What a public key and an internal key each read of the record HC 2x1.5-6: fields above a key's tier are absent from its responses.
Field of HC 2x1.5-6A public keyYour website, a partner's site, an AI assistant outside your teamAn internal keyYour ERP, your quoting tool, your own team's assistant
Flow at BEPPublic130 GPM · 29.5 m³/h130 GPM · 29.5 m³/h
CasingPublicASTM A48 Class 30 cast ironASTM A48 Class 30 cast iron
List price (USD)InternalAbsent from the response1,850
Lead time (weeks)InternalAbsent from the response1
Distributor multiplierConfidentialAbsent from the responseAbsent from the response
Standard unit cost (USD)ConfidentialAbsent from the responseAbsent from the response

A key's tier is set when an admin creates it and cannot be raised by a request. A key above Public also reads records that are not published yet, and their tags. Every key is read-only.

A read-only REST API

Tables, records, curves and document downloads as JSON. Filter on any field by its key, sort, page through large catalogs, look a record up by model number or SKU, and ask only for what changed since your last sync. The reference is public, with an OpenAPI file beside it.

  • Filters by field key: min, max and equals
  • Changes since a date, for incremental sync
  • ETags: an unchanged catalog costs almost nothing to poll

Units travel with the numbers

A numeric spec arrives with its unit and with both renderings, imperial and metric, so your website never converts anything itself. Field keys are stable, so a renamed label does not break an integration. Add a language and the names and choices come back translated.

  • Every number with its unit and a dual rendering
  • Stable field keys behind translated names
  • Formatted text as Markdown with sanitized HTML beside it

An MCP server for AI assistants

The same data, shaped for an assistant. It lists your tables, reads a table's fields with their units and choices, then searches with the same filters as the API. Each tool call is one API request, counted against the same rate limit, and nothing is copied out of SpecLatch beforehand.

  • Five tools that map one to one onto the API
  • Claude Code, Cursor, VS Code and Claude Desktop connect with a key
  • The assistant sees your units, choices and field names as you defined them

Every key has a ceiling

A key is read-only and is given a tier when it is created: public, internal or confidential. That tier is the most it can ever see, whoever holds it and whatever they ask. A public key gets published records and public fields. Fields above the ceiling are absent from the response, so their existence stays private too.

  • Read-only keys, revocable at any time
  • A public key for your website, an internal one for your team's tools
  • No key can write, publish or delete

See it speaking your industry's language

See it on your own catalog

Start a free trial and import one of your own product families. The fastest way to evaluate SpecLatch is on your own data.

Start your free trial

30 days of Growth-plan features · no credit card required · your data exports any time