Classify support tickets API

Classify supplied tickets into billing, access, outage, defect, delivery, or account when one documented keyword list has the most matches. A caller-supplied category list replaces that set. A tie stays unclassified.

The Classify support tickets operation is part of the Customer Support Intelligence API on BRAINIAC.software. Classify supplied tickets into billing, access, outage, defect, delivery, or account when one documented keyword list has the most matches. A caller-supplied category list replaces that set. A tie stays unclassified. It is exposed as POST /api/v1/customer-support/ticket-classify and priced at $0.03 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Ticket text, conversations, and support exports supplied in the request. Limitations: No support system is contacted or changed. A ticket is not marked resolved, and no reply is sent. Policies, account details, and customer history are not invented. A category, priority, or escalation flag comes only from the supplied text and the documented rules. A similar ticket is a suggestion with a confidence level, not a merged case. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Prioritize support tickets, Detect duplicate tickets, Summarize a support conversation, Analyze ticket sentiment. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.03 USDC
/api/v1/customer-support/ticket-classify

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/customer-support/ticket-classify" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "tickets": [
    {
      "id": "t1",
      "subject": "Cannot log in",
      "body": "I cannot log in. The password page is broken.",
      "email": "ada@analytical.example"
    },
    {
      "id": "t2",
      "subject": "Invoice 104",
      "body": "Please review invoice 104.",
      "email": "grace@navy.example"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Customer Support Intelligence APIFull docsHow it works