Evidence · July 22, 2026

What Talkform’s agent readiness evidence actually proves

A small, named denominator with reproducible checks—without treating protocol files as search-ranking guarantees.

Current result

15 of 15 named public discovery and task routes returned HTTP 200 on July 22, 2026. The repository test suite also covers the text interview path, required-field progress, correction, review, and local export. This is release evidence, not a claim that every agent, query, form provider, or browser will succeed.

Route denominator

  • /
  • /app
  • /import
  • /pricing
  • /docs
  • /docs/mcp
  • /agents.md
  • /llms.txt
  • /.well-known/ai-agent.json
  • /.well-known/agent-card.json
  • /schemas/audioform-config.json
  • /schemas/audioform-session-result.json
  • /use-cases/user-research
  • /import/typeform
  • /faq

Reproduce the route check

for route in / /app /import /pricing /docs /docs/mcp /agents.md /llms.txt \
  /.well-known/ai-agent.json /.well-known/agent-card.json \
  /schemas/audioform-config.json /schemas/audioform-session-result.json \
  /use-cases/user-research /import/typeform /faq; do
  curl -L -sS -o /dev/null -w "%{http_code} $route\n" "https://www.talkform.ai$route"
done

What remains unproven

This check does not prove search placement, citation frequency, cross-agent compatibility, production handoff durability, or conversion lift. Talkform’s current MCP package is local schema/template tooling. Hosted handoff and remote MCP remain gated on durable account storage, authorization, retention, and deletion controls.

Follow the implementation

See the agent workflow, MCP install path, security boundary, and changelog.