Propose CSV normalization API

Propose trim, email lowercase, boolean tokens, and unambiguous thousands separators. Each change names its rule and keeps the original cell. Dates that are not already YYYY-MM-DD are not rewritten.

The Propose CSV normalization operation is part of the Data Quality Intelligence API on BRAINIAC.software. Propose trim, email lowercase, boolean tokens, and unambiguous thousands separators. Each change names its rule and keeps the original cell. Dates that are not already YYYY-MM-DD are not rewritten. It is exposed as POST /api/v1/data-quality/csv-normalize 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: CSV and JSON tables supplied in the request. Limitations: No business system is contacted or updated. Rows past 2,000 and columns past 40 are not read, and the omitted counts are reported. Normalization is a proposal. Original values stay beside the proposed values. A statistical outlier is not a confirmed error. Dates are not rewritten unless they are already real YYYY-MM-DD days. 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 Detect a CSV schema, Profile CSV columns, Detect CSV column types, Audit missing CSV values. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/data-quality/csv-normalize

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/data-quality/csv-normalize" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "csv": "id,email,amount,status,joined\n1,Ada@Example.com,10,yes,2024-01-15\n2,ada@example.com, 12,no,2024-02-01\n3,grace@example.com,11,,2024-03-01\n4,bea@example.com,13,yes,2024-04-01\n2,ada@example.com,12,no,2024-02-01\n6,cy@example.com,10,yes,2024-05-01\n7,not-an-email,11,no,03/11/2026\n8,di@example.com,12,yes,2024-06-01\n9,ed@example.com,500,no,2024-07-01\n10,fay@example.com,11,yes,2024-08-01\n11,gus@example.com,12,yes,2024-09-01\n12,hoa@example.com,10,no,2024-10-01\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

Data Quality Intelligence APIFull docsHow it works