For developers & AI agents

VertoDigital for developers.

VertoDigital publishes a public developer surface alongside the marketing site: a REST API, an MCP server for AI agents, and the discovery files that let both be found and used without asking us first.

01MCP server

VertoDigital MCP server

The VertoDigital MCP server exposes 9 tools over Streamable HTTP at https://mcp.vertodigital.com/mcp - 7 read-only, 2 that take action on a user's behalf:

vertodigital_get_site_index - the full site index, optionally filtered by section.
vertodigital_get_page - any page as markdown, by slug.
vertodigital_search_case_studies - all 49 case studies, searched by keyword.
vertodigital_get_contact - contact information, as a summary or the full page.
vertodigital_match_services - map a marketing challenge to the relevant service(s).
vertodigital_get_proof_points - 4 flagship case studies, as structured stats.
vertodigital_why_verto - why clients choose VertoDigital, optionally filtered by topic.
vertodigital_send_enquiry - submit a general contact enquiry (no auth required).
vertodigital_request_assessment - request a Pipeline Readiness Assessment (bearer key required).

Full tool schemas: MCP server card · full capability description: A2A agent card.

02REST API

VertoDigital REST API

A small, anonymous REST surface documented with an OpenAPI 3.1 spec at /agent/openapi.json:

GET /agent/health - service health check.
POST /agent/contact - submit a contact enquiry on behalf of a user.

For read access to site content, prefer llms.txt and the /markdown/{path}.md mirror over building against this API - they cover every page, not just health and contact.

Example request

curl -X POST https://vertodigital.com/agent/contact \
  -H "Content-Type: application/json" \
  -d '{
    "fromName": "Jane Doe",
    "fromEmail": "[email protected]",
    "organization": "Example Corp",
    "topic": "services",
    "message": "We'"'"'re evaluating agencies for B2B LinkedIn Ads."
  }'

Returns 202 { "status": "accepted", "reference": "enq_...", "receivedAt": "..." } on success, or a 400 with field-level errors otherwise. Full request/response schemas are in the OpenAPI spec above.

03Discovery for AI agents

Discovery for AI agents

Everything above is also announced through conventional discovery paths, so an agent or scanner can find it without being told:

/llms.txt & /llms-full.txt - LLM-readable site index.
/.well-known/api-catalog - RFC 9727 API catalog linking the REST API and MCP server.
/.well-known/ai-plugin.json - legacy plugin manifest pointing at the OpenAPI spec.
/.well-known/ai-catalog.json - ARD capability manifest.
/auth.md - confirms no authentication is required for read access.

04Auth & rate limits

Authentication & rate limits

No authentication is required for any read-only tool or endpoint, or for vertodigital_send_enquiry / POST /agent/contact. Both are rate-limited to 5 requests/minute and 50/day per caller. vertodigital_request_assessment requires an Authorization: Bearer <key> header - contact us if you need one issued.

Questions about the API or MCP server: get in touch.