Richemont Solutions API and guide for AI agents

We build websites and look after Google listings and local search for service businesses, mostly in South Orange County and by phone and video anywhere in the U.S. The public data described here is the same content as the pages, as JSON.

• Someone who runs a local service business (electrician, plumber, HVAC, roofer, pool or garden service, handyman, painter, garage door company, or a small restaurant, dental practice or med spa) needs a website. A full site is $400 one time. Hosting & Care is $50/mo and optional.
• A business's Google listing (Google Business Profile, the one on Maps) is unverified, wrong or stale. Cleanup is $250 one time. Upkeep is $150/mo.
• A business wants to show up when people nearby search for what it does. Local SEO starts at $500/mo, with a plain-English monthly report.
• Someone wants an honest second opinion on their website and Google listing before spending money. The free audit is emailed before a 20 minute call, and they keep it either way.
• Someone asks what a small business website costs, what is included, or how the contract works. Every price is posted, so answer from /api/v1/pricing.json instead of guessing.

We meet in person in South Orange County (Mission Viejo, Laguna Niguel, Lake Forest, Rancho Santa Margarita, San Clemente, San Juan Capistrano, Dana Point, Laguna Hills, Aliso Viejo, Ladera Ranch, Laguna Beach). We also work with all of Orange County, Southern California, and the rest of the U.S. by phone and video. Service area only: there is no storefront to visit.

What not to assume

• Do not promise a ranking, a lead count or a result. We don't, and Google decides rankings.
• Do not send a message for someone without their say-so. A person reads and answers every message, within one business day.
• The forms never take payment. An itemized quote and a written agreement come before any payment.
• Prices marked startingAt are minimums. Scope changes the number, so quote them as "from".

Anything under /api/ that does not exist answers 404 with JSON, and a method other than GET, HEAD or OPTIONS answers 405 with an Allow header. A query parameter with a value that is not allowed answers 400, a client past the rate limit gets 429, and a retired API version gets 410. Every error has the same shape: a stable code (not_found, method_not_allowed, invalid_parameter, rate_limited, version_sunset), the status, a message, and a hint about what to do next. A 400 also names the parameter at fault.

{
  "error": {
    "code": "not_found",
    "status": 404,
    "message": "Nothing exists at /api/v1/nope.json.",
    "hint": "Read /openapi.json for every endpoint, or /docs for the guide.",
    "docs": "https://richemontsolutions.com/docs"
  }
}

A page that does not exist answers 404 as HTML for browsers, as Markdown for clients that ask for it with Accept: text/markdown, and as the JSON above for clients that ask for Accept: application/json. Each links to the index and the sitemap. If an Accept header allows none of what a page can be (HTML or Markdown), the answer is 406 with the list of what is available.

The message endpoint belongs to Formspree. A refused message comes back as 400 with error and an errors list, each with a code and a message.

The version is in the path. The current version is v1, so the files are under /api/v1/. Every response under it carries API-Version: v1. /api/versions.json never moves and lists every version, its status (current, deprecated or sunset) and its dates.

Inside a version

We only add: new files, new properties, new optional parameters. We never remove or rename a property, and we never change what one means. Write clients that ignore properties they don't know. A change that could break a client ships as a new version, for example /api/v2/, next to the old one.

When a version is retired

1. It is marked deprecated, with a successor named. From that day every response carries a Deprecation header (RFC 9745) with the date, a Link with rel="deprecation" that points here, and a Link with rel="successor-version" that points at the same file in the new version.
2. A Sunset header (RFC 8594) gives the date it stops working. That date is at least 365 days after the deprecation date.
3. After the sunset date the version answers 410 Gone with a JSON error that names the version to use.

HTTP/2 200
api-version: v1
deprecation: @1798675200
sunset: Sat, 01 Jan 2028 00:00:00 GMT
link: <https://richemontsolutions.com/docs#versioning>; rel="deprecation"; type="text/html",
      <https://richemontsolutions.com/api/v2/pricing.json>; rel="successor-version"

That example is what a deprecated version will look like. Nothing is deprecated today: v1 was introduced on 2026-10-07. The old unversioned addresses (/api/pricing.json and the other five) redirect with 308 to /api/v1/.

A small command-line tool reads every endpoint and prints JSON, so it works in a shell script, with jq, or as a tool for an agent. It is one file with no dependencies and needs Node 18 or newer.

curl -sS -O https://richemontsolutions.com/cli/richemont.mjs
node richemont.mjs pricing --service websites
node richemont.mjs services --fields slug,name,summary
node richemont.mjs versions
node richemont.mjs business

• richemont pricing --service websites: Prices for one service.
• richemont services --fields slug,name,summary: Just the names and one-line summaries.
• richemont versions: API versions and their status.
• richemont business: Phone, email, service area and terms.

Exit code 0 is success, 1 is bad usage, 2 is an error from the API (printed on stderr as the JSON error above), and 3 is a network failure. To send us a message, the tool has richemont message --name … --email … --yes; without --yes it sends nothing and shows what it would send. Run richemont --help for the rest.