Support tickets — API + Enrich Agent (no Connect page)

Use when a user asks to file a bug, contact support, or report billing/account issues.

There is no /connect?action=… wizard for support. Tickets are opened via the REST API or the Enrich Agent chat — not a standalone support form page.

How to open a ticket ($0.01)

Option A — Enrich Agent (humans)

  1. Go to /demo (or /connect?action=enrich_agent).
  2. Ask in the chat: “file a support ticket — …”
  3. The model calls submit_support_request (MCP) or you can call the API yourself.

Option B — REST API (automation / scripts)

curl -sS -X POST https://411data.io/api/v1/support/tickets \
  -H 'Authorization: Bearer 411_…' \
  -H 'Content-Type: application/json' \
  -d '{
    "category": "bug",
    "subject": "Short title (≤120 chars)",
    "body": "What happened, expected behavior, steps to reproduce.",
    "source_session_id": "<optional enrich chat id>"
  }'

category: bug | billing | account | other

Charges $0.01 once (virtual balance → x402). Response includes support_session_id and open_url (e.g. /demo?session=<id>).

Bug bounty: tickets filed with category: bug earn a $1.00 virtual USD credit after operator confirmation (repro steps + expected vs actual behavior help).

After open

curl -sS -X POST \
  "https://411data.io/api/v1/demo/sessions/{support_session_id}/messages" \
  -H 'Authorization: Bearer 411_…' \
  -H 'Content-Type: application/json' \
  -d '{"text": "Additional detail…"}'

Post-open triage (enrich chat only)

When opened from Enrich Agent, the model may still be in the enrich chat and should:

  1. cookbook_read → connect_wizards / api_integrations / topic-specific recipes.
  2. Answer from docs if possible; ask "Does this answer your question?"
  3. Mirror triage text into the support session (author: triage_bot) for operators.

Operators (internal)

Support Inbox on /ui-traffic (staff token):

Endpoint Purpose
GET /api/admin/support/tickets List tickets (?status=open)
GET /api/admin/support/tickets/{id} Full transcript
POST /api/admin/support/tickets/{id}/reply Operator reply
PATCH /api/admin/support/tickets/{id} Update support_status

Webhook

Subscribe to support.ticket_created via event_callbacks.