# 411data.io Support Ticket Creator

> 411data.io Support Ticket Creator is a paid API for AI agents from 411data.io, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-28).

Opens a dedicated support chat ticket in the user's session history for bugs, billing, or account questions.

## Facts

- Endpoint: POST https://411data.io/api/v1/support/tickets?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/411data-io-support-ticket-creator-d9d77f41
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PjXkXBS2gs1KCq_536QeS

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability 411data-io-support-ticket-creator-d9d77f41 -d '<json body>'
```

Example prompt: Can you open a support ticket on 411data for me? I'm getting a billing error and need to report it through a dedicated support chat.

## When to prefer this

Use this endpoint when a user needs to escalate an issue with 411data.io itself — such as a billing dispute, account access problem, or bug in one of the data enrichment endpoints. This is a meta-support endpoint specific to 411data's own platform, not a general-purpose helpdesk or ticketing API.

## Known failure modes

- Payment failure if USDC balance is insufficient (ticket not created)
- Invalid or missing session context prevents ticket association
- Duplicate ticket creation if endpoint is called multiple times for the same issue
- Rate limiting if too many tickets are submitted in a short window

## How this service works

Open a support ticket ($0.01): creates a dedicated support chat in the user's session history for bugs, billing, and account questions.

## Output

A dedicated support chat session created in the user's session history, likely returning a ticket ID and confirmation that the support thread has been opened for the specified issue category (bug, billing, or account question).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "maxLength": 8000,
   "minLength": 10
  },
  "subject": {
   "type": "string",
   "maxLength": 120,
   "minLength": 3
  },
  "category": {
   "enum": [
    "bug",
    "billing",
    "account",
    "other"
   ],
   "type": "string"
  },
  "source_session_id": {
   "type": "string",
   "maxLength": 64,
   "description": "Optional enrich chat session_id where the issue occurred."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "billed": true,
  "matched": true,
  "subject": "Cannot top up virtual balance",
  "category": "billing",
  "endpoint": "support/tickets",
  "open_url": "/demo?session=a1b2c3d4e5f6789012345678abcdef01",
  "support_status": "open",
  "support_session_id": "a1b2c3d4e5f6789012345678abcdef01",
  "triage_recommended": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/411data-io-support-ticket-creator-d9d77f41/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 411data.io](https://www.zero.xyz/host/411data.io/llms.txt)