# Vantacore web API

The Vantacore marketing site exposes a small web API at
`https://vantacore-ai.com/api`. Its machine-readable OpenAPI 3.1 description is
available at [`/openapi.yaml`](https://vantacore-ai.com/openapi.yaml).

## Endpoints

- `GET /api/healthz` — returns the service health status as JSON.
- `POST /api/contact` — web inquiry intake is held by default and returns
  HTTP 503 without saving an inquiry or requesting a reCAPTCHA assessment.
  Only `CONTACT_INTAKE_ENABLED=true` can opt into the retained server path;
  restoring the website form and approving its handling are separate steps.
  The request schema and response formats are defined in the OpenAPI description.

Use the published email or telephone details on the
[Contact page](https://vantacore-ai.com/contact/) while web intake is held. No consultation,
routing or reply is promised. The contact endpoint does not provide account
registration, OAuth, or agent provisioning.

## MCP server

Agents can also reach a public Model Context Protocol server over Streamable
HTTP at `https://vantacore-ai.com/api/mcp` (POST, JSON-RPC 2.0). Its SEP-1649
server card is published at
[`/.well-known/mcp/server-card.json`](https://vantacore-ai.com/.well-known/mcp/server-card.json) and is also
readable over the protocol as the `mcp://server-card.json` resource.

The server is unauthenticated, stateless, rate limited, and strictly read-only.
It exposes these tools:

- `get_company_profile` — The corporate identity Vantacore publishes on its own site: the registered legal name and display brand, the jurisdiction of incorporation, the registered office address, and the published enquiry email and phone number. These are the same facts the site's structured data and llms.txt carry — nothing here is inferred.
- `list_offerings` — What Vantacore publishes that it offers: the capability pillars (infrastructure, consulting, platform, enterprise), the deployment shapes it runs in (managed, single-tenant, disconnected), and the engagement models it sells (evaluate, build, operate). Filter with category to get just one of the three. Each entry carries the published headline, summary, and detail — no pricing, no benchmark figures, and no customer names, because the site publishes none.
- `get_service_health` — Current health of the Vantacore public web API, as reported by the service itself. Returns the same status as GET /api/healthz, plus the time of the check and how long the answering process has been running.
- `list_api_operations` — List the operations published in Vantacore's OpenAPI description: operation id, HTTP method, path, summary, and tags. Optionally filtered by tag. This is the public web API only — no internal services.
- `get_api_operation` — Full published detail for a single operation: its description, JSON request-body fields with their validation constraints, and the documented responses. Look up the operation id with list_api_operations first.

Submitting the contact form is deliberately not exposed as an MCP tool; it
remains a human-initiated HTTP request.