TailyX Agent API

A REST API for AI agents to discover TailyX-powered companies, retrieve public intake schemas, and submit enquiries programmatically. All submissions require explicit user confirmation.

Discovery

OpenAPI specification
GET /.well-known/openapi.json
Full OpenAPI 3.1.0 spec with endpoint schemas and agent workflow instructions.
Agent service manifest
GET /.well-known/agents.json
Machine-readable service description including capabilities, supported tools, and protocol version.
MCP server
https://tailyx-mcp-55758bb6fb79.herokuapp.com/mcp
Remote Model Context Protocol server for tool-enabled agents.

Machine-readable discovery files: https://tailyx.ai/.well-known/agents.json, https://tailyx.ai/.well-known/openapi.json, https://tailyx-mcp-55758bb6fb79.herokuapp.com/mcp (MCP server), and https://tailyx.ai/llms.txt.

Machine-readable discovery files

Endpoints

GET

/agent/v1/lookup

Find a widget by domain or URL. Returns the embed key and agent mode status.

Query params: domain or url

GET

/agent/v1/manifest/:embed_key

Discover capabilities and available endpoints for a widget. Requires agent mode enabled.

GET

/agent/v1/schema/:embed_key

Get required fields, intents, and public intake questions. Always call this before submitting — fields are per-widget.

POST

/agent/v1/submit/:embed_key

Submit an enquiry. Returns public submission control flow and an optional booking handoff URL.

Requires explicit user confirmation before calling.

GET

/agent/v1/lead/:lead_id/status?embed_key=:embed_key

Check the status of a previously submitted lead. embed_key is required.

GET

/agent/v1/instructions/:embed_key

Workflow instructions for browse-enabled and text-only agents.

Protocol

Protocol name
tailyx-agent
Protocol version
0.1
Confirmation
Required before every submit
Auth
None required for GET endpoints

Execution requirements

Further reading