Turn product docs into an MCP surface

Give Verify an OpenAPI spec, GitHub repo, Markdown docs, Postman collection, website docs, PDF-derived text, or help-center content. Verify generates tool schemas, a server-card draft, llms.txt, usage examples, policy metadata, a score preview, and a hosted docs page.

Input

docs source

OpenAPI, Markdown, Postman, website docs, PDFs, help centers, or mixed documentation.

Output

agent-ready artifacts

MCP server draft, server-card.json, llms.txt, tool schemas, usage examples, and policy metadata.

Next step

validate + host

Generated surfaces can flow into Verify scoring, hosted runtime, gateway decisions, and audit ledger evidence.

Who buys this

SAAS TEAMS

Become agent-readable

Teams with existing APIs and docs that need MCP schemas, server-card.json, llms.txt, examples, and policy metadata without a hand-built MCP program.

PUBLISHERS

Launch a better MCP surface

MCP publishers who want generated artifacts to enter validation, improve discoverability, and prove readiness before hosting or claiming badges.

MARKETPLACES

Normalize partner docs

Marketplaces and platform teams that need consistent agent-readable metadata across many vendors and internal services.

How it connects to Gateway and Ledger

Docs Compiler creates the agent-readable surface. Gateway uses the generated schemas and policy metadata to decide attempted calls, and Ledger keeps source, artifact, policy, score, and decision evidence linked.

VALIDATE

Generated surfaces become Verify objects

Docs Compiler output can be registered, scored, compared, and moved into hosted runtime activation once validation passes.

GATEWAY

Policy metadata feeds decisions

Generated tool schemas and policy metadata give /v1/decide the tool names, scopes, risk hints, and approval expectations it needs.

LEDGER

Compilation evidence stays attached

Ledger can reference the source docs, generated artifact id, policy metadata, score preview, and downstream decision evidence.

Sample generated artifact

{
  "compilation_id": "docs_7f3a",
  "server_card": {
    "name": "example-saas",
    "tools": [
      "search_records",
      "create_draft_invoice"
    ],
    "mcp_endpoint": "/hosted/example/saas/mcp"
  },
  "llms_txt": "/docs/generated/docs_7f3a/llms.txt",
  "policy_metadata": {
    "requires_oauth": true,
    "write_tools": [
      "create_draft_invoice"
    ],
    "requires_human_approval": [
      "send_invoice"
    ],
    "data_classes": [
      "customer_data",
      "billing"
    ]
  },
  "next_steps": [
    "validate",
    "export_policy",
    "decide_agent_call",
    "host_runtime"
  ]
}

API

curl -sS https://verify.sentinelsignal.io/v1/docs/compile \
  -H 'content-type: application/json' \
  -d '{"title":"Example SaaS","source_type":"openapi","openapi_spec":{"openapi":"3.1.0","paths":{}}}'