Agent readiness evidence

Current result

The September 9, 2026 release verification completed the authenticated REST and hosted MCP handoff loop. It checked project-key authorization, handoff creation, respondent review and submission, independent structured-result retrieval, MCP initialization and hosted lifecycle tools, and deletion behavior. The CI regression suite passed 180 tests plus two browser onboarding checks. This is release evidence for those checks, not a claim that every agent, query, form provider, browser, voice session, or downstream system will succeed.

The named public discovery and task route check previously recorded 15 of 15 HTTP 200 responses for the deployed revision checked on July 22, 2026. That historical reachability result does not establish current search placement or citation frequency.

Live voice deadline

On September 10, 2026, one production test used synthetic silent audio and a brief provider response. The server began ending the call at its 180-second deadline, confirmed termination 2.2 seconds later, and the realtime connection stopped before browser cleanup. The matching durable Workflow deadline step completed successfully. Both server controls ran close together; this check does not prove which issued the first hangup or test recovery from a server process failure.

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

These checks do not prove search placement, citation frequency, cross-agent compatibility, voice quality, conversion lift, or downstream processing. The local MCP package remains a schema, template, and validation surface; the hosted project tools require a project key and the explicit retention and deletion contract described in the current documentation.

Follow the implementation

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