Classify a maintenance request API

Classify a stated type only from an explicit token, and flag a documented safety keyword for a person to review. An unrecognized word is left unrecognized.

The Classify a maintenance request operation is part of the Property Maintenance API on BRAINIAC.software. Classify a stated type only from an explicit token, and flag a documented safety keyword for a person to review. An unrecognized word is left unrecognized. It is exposed as POST /api/v1/property-maintenance/request-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: Maintenance requests, quotes, and invoices supplied in the request. Limitations: Records are copied only from labeled fields in the request. A type is classified only from an explicit token. A safety keyword is a flag for a person, not a finding that the property is unsafe. A quote comparison does not recommend a contractor. No contractor is dispatched and no tenant is contacted. 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 Assess maintenance priority, Draft a maintenance work order, Compare contractor quotes, Check a response service level. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/property-maintenance/request-classify

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/property-maintenance/request-classify" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "text": "Request: M-1 | 10 Example Street | 2026-11-01 | | leak | routine | drip under the sink\nRequest: M-2 | 10 Example Street | 2026-11-02 | | erase | | gas smell in the kitchen\nThe tenant is angry.\n"
}
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

Property Maintenance APIFull docsHow it works