Read a tender document: cables built, requirements, schedule, conflicts and gaps
read_tenderRead a project or tender document (a purchase or project specification, a tender volume, a GTP / data schedule; a PDF of up to 80 pages and 20 MB, or its text) and answer what it asks for: every cable it lists built as a design by the designer's rules and checked against its rule set, the required / offered schedule beside the document's own required values with their pages, each requirement mapped to a requirement card or listed as having none, the conflicts (one parameter with two values, a printed construction against a requirement, a value against the standard the document names, a voltage outside IEC 60038, a schedule row with no construction) and the missing sections. An LLM (Claude) copies the document's values and pages; it decides nothing: every design, check, conflict and gap is the deterministic rules with their sources. A reading takes up to a few minutes, so the call starts a job and answers a poll link; the reading is held in memory for one hour, then gone, and the file is never stored. The poll answer (thecablecode.tender/v1) has job, status (running, done or failed), pages and, when done, the reading; a failed paid reading starts again with the same file at no charge, and the same file within the hour is the same job, not charged twice. For one cable use design_cable or check_cable; for one maker's datasheet, extract_datasheet. Here the document's text; a PDF goes to POST /api/v1/tender. Always paid: $4.00 up to 20 pages, $2.00 for each further 10 pages begun, up to 80 pages.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hint | No | A cable tag or a voltage to look for first. | |
| lang | No | The language of the schedule's parameter names: any of the site's 15 (en, tr, de, nl, sv, fr, es, da, no, fi, it, ro, pl, cs, ru). Default en. | |
| text | Yes | The document's text (a Word file turned into text); it counts one page per 1,700 characters begun. |