AI Agents & TailyX

AI agents can discover any TailyX-powered company, read its qualification schema, and prepare a qualified enquiry for submission — without manual form filling. Submission itself always requires explicit user confirmation using the TailyX Agent API.

How it works

Discover — Look up the company by domain to retrieve their embed key and confirm agent mode is enabled.
Read the schema — Fetch the widget schema to understand required fields, intents, and scoring questions.
Confirm — Present a single confirmation block to the user before submitting.
Submit — POST the qualified lead. TailyX scores, routes, and alerts the firm.
Report — Return the decision, score, and any booking handoff URL to the user.

Discovery endpoints

OpenAPI specification: GET https://tailyx.ai/.well-known/openapi.json
Agent service manifest: GET https://tailyx.ai/.well-known/agents.json
MCP server: https://tailyx-mcp-55758bb6fb79.herokuapp.com/mcp
Lookup endpoint: GET https://tailyx.ai/agent/v1/lookup?domain=example.com

Machine-readable discovery files

Important rules

Always call the schema endpoint before submitting — required fields are per-widget, not global.
Always present one confirmation block to the user before submitting.
Never submit automatically without explicit user confirmation.
Check the lookup response for agent_mode_enabled: true before proceeding.

Where TailyX submission works

Client context	Can submit?	Requirement
Custom GPT with Actions	Yes	TailyX Actions enabled
Claude Desktop	Yes	Local MCP configured
Claude.ai	Yes, when connected	Remote MCP connector enabled
ChatGPT App / connector-enabled ChatGPT	Yes, when connected	TailyX MCP/App connector enabled
Standard ChatGPT / Codex chat	No	No TailyX tool is available in the session
Standard Claude chat	No	No TailyX MCP connector is available in the session
Browse-only agents	Discovery only	Can read pages/tags, but cannot submit unless they can call tools/APIs

Discovery tells an AI agent that TailyX can accept structured lead submissions. It does not by itself grant a generic chat session permission to call the TailyX API. Submission requires a tool-enabled context such as Custom GPT Actions, MCP, or a ChatGPT App connector. These discovery tags and endpoints still help AI systems understand that TailyX is agent-ready, even when the current chat session cannot execute external tools.

Technical reference

For full endpoint documentation, request/response shapes, and workflow instructions, see the Agent API reference or read the OpenAPI spec.