F200.ai / For AI agents

A front door
for your agent.

AI Workforce Factory: AI workers, company intelligence and coding agents built by engineers on a governed cloud. Read the same published facts and articles through a structured interface.

Live website example

An assistant finds a service and prepares an inquiry.

“We need help with incident response and on-call reliability.”

  1. Discover the available tools.
  2. Read the published SRE offering.
  3. Prepare a brief for you to review.

This scripted demonstration calls our real public MCP endpoint. It uses a fixed example, without model inference. Inquiry preparation sends no email and stores no contact details.

Start with the facts

No model call or JavaScript is needed to read our company and offering information. Request a public page with Accept: text/markdown, or append .md to a service, product or editorial URL.

Connect through MCP

The remote endpoint is https://f200.ai/mcp. Inspect its live discovery response for supported tools and protocol compatibility.

Domain discovery is experimental. A client may require you to add the endpoint explicitly.

Explore, then act

  1. Use get_company, list_offerings and get_offering to read company facts, solutions and offering status.
  2. Use ask_website for a compact, cited answer. Request includeComposition only when you need a generated view.
  3. Use search_content, list_editorial and get_editorial to find and read published articles. Inspect citations, publication dates and limitations.
  4. Prepare an inquiry for the user to review.
  5. Hand off to the browser contact form for the user to review and explicitly submit with consent. Public MCP never submits an inquiry.

Know the boundaries

The site’s AI selects from reviewed content; it does not invent prices, product availability or company claims. Generated layouts contain trusted components.

Submitting an inquiry does not book a meeting, make a purchase or execute a product. The public website MCP is read-only and has no CMS administration or publishing tools. Inquiry preparation stores nothing and sends nothing.

Explore the experience map as data.

The experience map connects the site’s navigation to published offerings, canonical pages and their MCP interactions. Use the same AI-backed view composition to select relevant content and an overview, comparison or roadmap. Inspect the returned source and offering IDs before following a recommendation.

Agents can complete the discovery and inquiry-preparation journey through these structured operations.

Built into the browser, too.

On browsers that support the experimental WebMCP API, the page offers read-only portfolio and view-composition tools. Standard links, HTML and remote MCP remain available to other clients.

WebMCP browser support is checked when JavaScript runs. Remote MCP and public documents work independently.

Start with the problem.

We’ll start with a conversation.