Classify customer enquiries API

Classify enquiry text with transparent token rules such as emergency, quote, booking, or complaint. Classification is not a conversion prediction.

The Classify customer enquiries operation is part of the Local Business Lead Operations API on BRAINIAC.software. Classify enquiry text with transparent token rules such as emergency, quote, booking, or complaint. Classification is not a conversion prediction. It is exposed as POST /api/v1/local-lead-operations/customer-enquiry-classify and priced at $0.04 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: Caller-supplied lead exports Call logs Quote and enquiry records Limitations: Records are copied only from labeled fields in the request. Response delays use supplied timestamps only. Priority rules are transparent and do not predict conversion. No message is sent and no call is placed. No CRM account is accessed. 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 Normalize lead records, Analyze missed-call leads, Detect lead response delays, Prioritize quote follow-ups. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/local-lead-operations/customer-enquiry-classify

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/local-lead-operations/customer-enquiry-classify" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "enquiries": [
    {
      "id": "E-1",
      "leadId": "L-1",
      "text": "Urgent boiler leak, no hot water",
      "channel": "web",
      "received": "2026-11-04T08:00:00.000Z"
    },
    {
      "id": "E-2",
      "leadId": "L-2",
      "text": "Can I get a quote for a new bathroom?",
      "channel": "email"
    },
    {
      "id": "E-3",
      "leadId": "L-3",
      "text": "Please book an appointment next week",
      "channel": "phone"
    }
  ]
}
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

Local Business Lead Operations APIFull docsHow it works