Analyze ticket sentiment API

Label customer wording with a documented positive and negative word list. Text with no listed words stays unspecified.

The Analyze ticket sentiment operation is part of the Customer Support Intelligence API on BRAINIAC.software. Label customer wording with a documented positive and negative word list. Text with no listed words stays unspecified. It is exposed as POST /api/v1/customer-support/sentiment-analyze 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 Classify support tickets, Prioritize support tickets, Detect duplicate tickets, Summarize a support conversation. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.03 USDC
/api/v1/customer-support/sentiment-analyze

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/customer-support/sentiment-analyze" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "tickets": [
    {
      "id": "t1",
      "body": "I am frustrated and disappointed."
    },
    {
      "id": "t2",
      "body": "Thanks, that was helpful."
    }
  ]
}
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