# Semantic Surface

> Machine-first publishing. An agent-conversion agency. We make existing websites
> understandable to machines, operable by browser agents, and measurable as
> conversion systems.

This file exists because we sell machine-readability, so our own site publishes a
machine-readable record of itself. Everything asserted here is also printed on the
page a person can read.

## What we do

Three connected engagements:

- **The Surface Report** — $5,000. An agent-readiness and conversion audit of an
  existing website: up to 25 representative URLs and five critical customer
  journeys. Typically 10 business days from kickoff. The fee is credited toward a
  Retrofit started within 90 days.
- **The Agent-Ready Retrofit** — from $25,000. Non-destructive implementation on
  the existing site: entity and claim registry, semantic HTML, matching JSON-LD, a
  WebMCP action layer of three to eight tools, a human-confirmation workflow, an
  agent evaluation suite and a search-preservation baseline. Existing URLs,
  canonical relationships, content identity and customer experience are preserved.
- **Surface Watch** — from $2,500 per month. Structured-data and machine-file
  monitoring run continuously; full agent journey tests run monthly, and after any
  deployment you tell us about.

## The distinction the business rests on

Semantic Surface tells an agent what a page *means*. WebMCP tells the agent what
it *can do*. We make sure it can finish the job.

## The demonstration case

We have no client case studies, so the site ships one worked demonstration
instead of inventing evidence.

- **Northbank Fluid Power** — a **fictional** hydraulic hose and fittings
  distributor. It does not exist, has no web address, and none of these figures
  were measured on anybody's website.
- The case is Demonstration Case 01, *Compatibility Commerce*: a maintenance
  manager needs two 1/2-inch JIC hose assemblies rated above 3,000 psi, and three
  catalog assemblies that look identical in a photograph differ on the two numbers
  that decide the purchase.
- It is published in full at https://www.semanticsurface.com/demo/ — the
  requirement, the fourteen fields the retrofitted page would publish, the three
  assemblies compared, the six tools the catalog would declare, the call ledger,
  the human confirmation and what monitoring would re-test.
- Every artifact rendered from it carries the same string: *Fictional
  demonstration company · illustrative workflow · not client results*.
- The technical content is real. SAE 100R1AT, 100R2AT and 100R12 are hose
  constructions in SAE J517, the 4:1 design factor is J517's, and the JIC 37°
  flare thread sizes are SAE J514. The company, the catalog, the part numbers,
  the account and the customer are invented.
- The six tools in that walkthrough are an illustration of what a distributor
  would declare. They are **not** registered on our site, and nothing on /demo/
  executes.

## Agent tools on this site

Our own site declares four WebMCP tools. Three are read-only; one prepares a
request and stops for human confirmation rather than submitting it. Which of them
are registered depends on the route — the home page registers all four, and
/demo/ registers only `run_surface_demo`.

- `get_service_details(service_name)` — read-only
- `estimate_engagement_scope(website_url, journey_count)` — read-only
- `run_surface_demo()` — read-only. Reports the current route's published surface
  record: its subject, whether it is a published page or a demonstration, the
  tools registered on it, and the human confirmation gates it carries.
- `prepare_website_test_request(website_url, work_email, primary_conversion)` —
  writes a draft only. A person reviews and submits it.

The declarations are mirrored, without executing our JavaScript, at
https://www.semanticsurface.com/.well-known/webmcp-tools.json — which is our own
file, not a WebMCP standard artifact. WebMCP tools are declared at runtime by the
page itself.

## Things we will not claim

- WebMCP is a proposed browser API, developed by Google and Microsoft in the W3C
  Web Machine Learning Community Group. The spec is a draft Community Group
  Report, not on the W3C standards track, with TAG review pending. It is in origin
  trial in Chrome and Edge; Firefox and Safari have given no signal. We ship it as
  progressive enhancement.
- Google has not identified WebMCP as a ranking signal, and we will not imply
  otherwise. Rankings are never guaranteed.
- The browser does not enforce human confirmation for consequential actions. We
  build that boundary into the page and we test that it holds.
- The Surface Score shown on our site is an illustrative sample for a fictional
  website, not an audit of yours. It is our own scoring model, not an industry
  standard, and we publish the weights.
- We publish no client logos, testimonials, case studies, conversion lifts,
  revenue figures or time-saved numbers, because we have none. The demonstration
  case above states its own omissions rather than leaving you to notice them.

## Contact

hello@semanticsurface.com