---
title: "Rich Steinmetz API and MCP documentation"
description: "Public, read-only API and MCP reference for Rich Steinmetz consulting, including requests, responses, errors and versioning."
canonical: "https://richsteinmetz.com/docs/"
last-updated: "2026-11-17"
---

# Rich Steinmetz API and MCP documentation

Search or read Rich Steinmetz's public consultancy site. The NLWeb API and MCP server are read-only and require no credentials. Search covers the English homepage, About, Contact, Pricing, Privacy, and Terms. To book a call, open Google Calendar from the [contact page](https://richsteinmetz.com/contact/).

## Search the site with NLWeb

Send a natural-language question as `query.text` in a JSON body to `POST /v1/ask`. The query must contain 1–512 characters and include some non-whitespace text. The full body must fit within 16 KiB. If you set a response format or mode, use `conversational_search` and `list`.

```sh
curl -sS https://richsteinmetz.com/v1/ask \
  -H 'Content-Type: application/json' \
  --data '{"query":{"text":"How much does the Solution Definition Call cost?"}}'
```

The JSON response contains `_meta` with NLWeb version `0.55` and a `response_type` of `answer` or `failure`. An answer contains one to three results, each with a page URL, heading, and matching excerpt. A failure contains an `error` object with `code` and `message`.

You can also send `GET /v1/ask?q=...` with a URL-encoded question. See the [OpenAPI description](https://richsteinmetz.com/ask.openapi.json) for request and response schemas.

### Stream results

Set `prefer.streaming` to `true` in the POST body, add `streaming=true` to a GET URL, or send `Accept: text/event-stream`.

```sh
curl -sSN https://richsteinmetz.com/v1/ask \
  -H 'Content-Type: application/json' \
  --data '{"query":{"text":"How much does the Solution Definition Call cost?"},"prefer":{"streaming":true}}'
```

Read the event stream from `start` through `complete`. Each `result` event has a zero-based `index` and an `item`. A failed search sends an `error` event before `complete`. An invalid request can return a JSON failure before a stream opens.

### Handle search errors

- `400 INVALID_QUERY` for missing, malformed, blank, or oversized input.
- `405 INVALID_QUERY` for an unsupported HTTP method.
- `415 INVALID_QUERY` when a POST body lacks the `application/json` content type.
- `200 NO_RESULTS` when nothing matches your question.
- `200 UNSUPPORTED_FORMAT` or `200 UNSUPPORTED_MODE` for an unsupported preference.
- `500 INTERNAL_ERROR` when an unstreamed search cannot read site content. In a stream, read the `error` event.

## Rich Steinmetz MCP server

See the dedicated [Rich Steinmetz MCP server guide](https://richsteinmetz.com/docs/mcp/) for connection settings, tools, and installable agent resources.

Add `https://richsteinmetz.com/mcp` as a Streamable HTTP server in your MCP client. Let the client initialize the connection, then use `tools/list` and `tools/call`. The endpoint accepts POST requests and returns JSON. For direct HTTP calls, send `Content-Type: application/json` and `Accept: application/json, text/event-stream`.

- `get_consulting_overview` reads the public homepage.
- `get_solution_definition_call` reads the published price, payment terms, and booking link.
- `read_public_page` accepts a `page` of `home`, `about`, `contact`, `pricing`, `privacy`, `terms`, or `docs` and returns that page in Markdown.

Each tool also returns structured content with `page`, `uri`, `mimeType`, and `markdown`. Use `resources/list` and `resources/read` to open the public Markdown for the homepage, pricing, contact, or this guide by URI.

The server returns HTTP `405` for methods other than POST and `403` if you provide an `Origin` header that differs from the server's origin.

[MCP server card](https://richsteinmetz.com/mcp/server-card) · [Access and authentication](https://richsteinmetz.com/auth.md) · [Agent index](https://richsteinmetz.com/docs/llms.txt)

## API versions and compatibility

The site search API is version 1 at `/v1/ask`. `/ask` remains a supported alias for version 1. The `_meta.version` value `0.55` identifies the NLWeb response format, separately from this API version.

Compatible updates may add optional fields. Breaking request or response changes will use a new versioned path. No endpoint is currently deprecated. Before retiring an API version, this page will announce the change and affected responses will include `Deprecation` and `Sunset` headers with the retirement date.

## Safe retries and testing

Both GET and POST searches only read public site content. Retrying a request cannot book a call, change data, or charge a card; no idempotency key is required. The examples on this page are safe to run against the public API. Search returns up to three best matches in one response, with no additional pages or background jobs.

The application does not currently impose a per-client quota or advertise a rate-limit allowance. If hosting protection returns HTTP `429`, respect `Retry-After` when provided and otherwise retry with exponential backoff.

## Agent resources

[Official MCP Registry entry](https://registry.modelcontextprotocol.io/v0.1/servers/com.richsteinmetz%2Fconsulting/versions/1.0.0): `com.richsteinmetz/consulting`, version `1.0.0`.

- [Agent plugin bundle](https://richsteinmetz.com/agent-plugin.zip): The research skill and MCP connection in one portable package.
- [Plugin manifest](https://richsteinmetz.com/agent-plugin/plugin.json) and [MCP configuration](https://richsteinmetz.com/agent-plugin/mcp.json).
- [Research skill](https://richsteinmetz.com/.well-known/agent-skills/research-rich-steinmetz/SKILL.md): Instructions for evaluating consulting fit, pricing, and contact options.
- [Rich on GitHub](https://github.com/RichStone).

## MCP errors

An unknown tool returns a JSON-RPC `error` with code `-32602` and a readable message. Invalid tool arguments return `isError: true` with code `INVALID_ARGUMENTS`; a failed public-page fetch returns `CONTENT_UNAVAILABLE`. For these tool errors, read the `code` and `message` in `_meta.error` or the JSON text content. Successful calls keep their normal `structuredContent` shape.
