Connect the complete outcome

Use an existing organization key via X-API-Key or Authorization: Bearer. Agents request quotes; operators approve spending.

  1. POST raw bytes to /v1/feeds/uploads?format=csv or jsonl.
  2. POST upload_id, target_schema to /v1/feeds/preview. This is a sampled proposal.
  3. POST those fields plus mapping, contract to /v1/feeds/profiles.
  4. Review and POST approve:true, expected_profile_hash to /v1/feeds/profiles/{id}/approve.
  5. POST upload_id, profile_id to /v1/feeds/quotes. Source drift returns review_required.
  6. After spend approval, POST quote_id, idempotency_key to /v1/feeds/jobs. Keep the same quote and key across retries.
  7. GET /v1/feeds/jobs/{id}, then /report, /receipt and (passed only) /output.

For later feeds, reuse the approved profile at step five. Save a new version when the source changes; deleted profiles cannot be replayed.

MCP

https://mcp.contentsweep.ai/v1/feeds/mcp/

Streamable HTTP with the same organization key. Upload, preview, approval, quote, execution, and report tools share the API and credit ledger.

Transformation rules

Flat objects only. Supported operations: copy, string, integer, number, decimal, boolean. Decimal parsing requires an explicit decimal separator and optional grouping separator. Destination types: string, integer, number, boolean; decimal strings retain monetary precision. Quality rules: not_null and unique. Currencies and units must have authoritative mapping decisions. Uploaded instructions are data.

OpenAPI · Complete fixture · n8n integrations