MACHINE-READABLE ACCESS

Developer & agent API

Tight Steel exposes its pooled-order warehouse in machine-readable form for procurement software and AI agents. The API serves the exact same data rendered on /warehouse — one source, no drift. No authentication is required for reads.

Indicative data. Schedules and quantities are indicative. Current availability is confirmed with each inquiry. No pricing is exposed anywhere in the API — pricing is confirmed per inquiry. Expressing interest is non-binding: all commitments happen with a human via firm PO after specification, availability, pricing and timing are validated.

ENDPOINT

GET /api/pools

Returns every procurement pool with specification, region, status, cutoff, indicative footage and tonnage, plus links to the pool page and its availability-check form. Also served at /pools.json. Responses are cacheable for one hour and CORS-enabled for GET from any origin. Statuses open and forming accept availability inquiries; mill_review and scheduled are past cutoff and included for completeness. Fields with no confirmed value are omitted — absence means unknown, never zero.

curl -s https://tightsteel.com/api/pools

ENDPOINT

POST /api/requirements

Submits a buyer requirement into the same human-reviewed pipeline as the post-a-requirement form. Accepted standards: ASTM A513. Unknown standards are rejected with the accepted list. Submissions are rate limited per IP and capped at 16 KB. On success the API responds 202 with:

{ "status": "received", "message": "A human validates specification compatibility, availability, pricing and timing before anything is confirmed." }

curl -s -X POST https://tightsteel.com/api/requirements \
  -H "Content-Type: application/json" \
  -d '{
    "standard": "ASTM A513",
    "type_or_grade": "Type 1 / H70",
    "shape": "Round",
    "od_in": 1.181,
    "wall_in": 0.079,
    "length_ft": 20,
    "quantity_ft": 5920,
    "delivery_region": "Ontario, Canada",
    "needed_by": "2026-10-01",
    "recurring": false,
    "company": "Example Fabrication Co.",
    "contact_name": "A. Buyer",
    "email": "buyer@example.com",
    "notes": "MTR per heat required.",
    "source": "ai-agent:example"
  }'

Identify your agent in the optional source field (e.g. "ai-agent:<name>") so a coordinator can reference it in follow-up.

SPECIFICATION & DISCOVERY

OpenAPI & llms.txt

https://tightsteel.com/api/openapi.json — OpenAPI 3.1 spec, generated from the same schemas that validate the implementation.
https://tightsteel.com/llms.txt — plain-text overview for language-model agents.

Pool data is maintained directly by Tight Steel and may change as buyers join, quantities are allocated and mill schedules are confirmed. Nothing in this API constitutes confirmed inventory, confirmed pricing, or an offer capable of acceptance without human validation.