Agent Fabrication Network (UFP) MCP · Agentic Fabrication Network
OperationalAvailability — last 30 days
Last observed 1 h ago by MCP Tools Edge Scanner · scheduled every 120 min
get_shop_gauges was added.get_shop_gauges was added.Raw event details
{
"beforeRev": 10,
"afterRev": 11,
"changeCount": 1
}color_shades was added at preview_quote.inputSchema.color_shades was added at preview_quote.inputSchema.Raw event details
{
"beforeRev": 9,
"afterRev": 10,
"changeCount": 4
}get_fabrication_quote changed.| Path | Change | Classification | Detail |
|---|---|---|---|
| tools.get_fabrication_quote | description changed | Informational | Descriptions or metadata for get_fabrication_quote changed.No structural change. Wording changes can still influence model tool selection. |
| tools.preview_quote | description changed | Informational | Descriptions or metadata for preview_quote changed.No structural change. Wording changes can still influence model tool selection. |
| tools.refine_quote | description changed | Informational | Descriptions or metadata for refine_quote changed.No structural change. Wording changes can still influence model tool selection. |
anyOf) at refine_quote.inputSchema.bends changed.anyOf) at refine_quote.inputSchema.bends changed.Raw event details
{
"beforeRev": 8,
"afterRev": 9,
"changeCount": 4
}Raw event details
{
"result": "timeout",
"error": "No response within 10 seconds."
}refine_quote.inputSchema.color changed from string to string,null.refine_quote.inputSchema.color changed from string to string,null.Raw event details
{
"beforeRev": 7,
"afterRev": 8,
"changeCount": 15
}coupon_code was added at create_checkout.inputSchema.coupon_code was added at create_checkout.inputSchema.Raw event details
{
"beforeRev": 6,
"afterRev": 7,
"changeCount": 2
}clear was added at refine_quote.inputSchema.clear was added at refine_quote.inputSchema.Raw event details
{
"beforeRev": 5,
"afterRev": 6,
"changeCount": 4
}ui://widget/quote-compare-v39.html is no longer advertised.ui://widget/quote-compare-v39.html is no longer advertised.Raw event details
{
"beforeRev": 4,
"afterRev": 5,
"changeCount": 7
}Raw event details
{
"result": "timeout",
"error": "No response within 10 seconds."
}get_fabrication_quote changed.| Path | Change | Classification | Detail |
|---|---|---|---|
| tools.get_fabrication_quote | description changed | Informational | Descriptions or metadata for get_fabrication_quote changed.No structural change. Wording changes can still influence model tool selection. |
ui://widget/quote-compare-v36.html is no longer advertised.ui://widget/quote-compare-v36.html is no longer advertised.Raw event details
{
"beforeRev": 3,
"afterRev": 4,
"changeCount": 3
}powder_finish was added at get_fabrication_quote.inputSchema.powder_finish was added at get_fabrication_quote.inputSchema.Raw event details
{
"beforeRev": 2,
"afterRev": 3,
"changeCount": 4
}ui://widget/quote-compare-v5.html is no longer advertised.ui://widget/quote-compare-v5.html is no longer advertised.Raw event details
{
"beforeRev": 1,
"afterRev": 2,
"changeCount": 4
}Raw event details
{
"contractHash": "sha256:d521f312b04f9baa5e483a593a76a6dddd3dbde64512dbd4d5430ebc07948a68"
}Advertised capabilities
Tools 13
get_fabrication_quote
47 params
Get ranked, purchasable offers (price, ETA, preview image) for fabricating a physical item from a design file.…
Get ranked, purchasable offers (price, ETA, preview image) for fabricating a physical item from a design file. process=fdm_print for 3D printing a model (STL/OBJ/PLY/3MF/AMF/STEP/IGES), process=cnc or process=sheetmetal for machined/bent metal parts (STEP, IGES, DXF), process=decal for stickers/decals from artwork (any common image or design file — PNG/JPG/HEIC/TIFF/GIF/BMP/WEBP/AVIF/SVG/PDF/AI/EPS/PSD/CDR, auto-converted). A .ufp file (UFP part container: the design plus saved spec/constraints in one) is accepted anywhere a design file is — its saved intent applies automatically and anything the user states now wins. If the user just drops a file and asks for a price, omit process — UFP routes it. Provide the design either as design_file (an image/file the user attached or you generated — preferred) or file_url (a public URL). REORDERS: if the user has a UFP part number (from a receipt email or a previous session, looks like UFP-… or part_…), pass it as part_number INSTEAD of any file — the stored design and spec are reused and re-shopped across all current vendors. Locked parts additionally require share_key (from the owner's share link). Returns offers across vendors like Google Flights returns flights.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| process | enum(11) | What to fabricate. If the user just drops a file and asks for a price, OMIT this — UFP detects the file type (artwork, mesh — STL/OBJ/PLY/3MF/AMF, BREP — STEP/IGES, DXF) and routes it to every process that can make it; the response's routing.also_possible lists processes UFP can't quote yet one of: "fdm_print", "resin_print", "powder_print", "metal_print", "elastomer_print", "cnc", "sheetmetal", "laser_cut", … |
| part_number | string | UFP part number from a previous paid order (UFP-… or part_…). Reorders: replaces design_file/file_url entirely; any other fields provided override the stored spec |
| share_key | string | Share key for a LOCKED part — the k=… value from the owner's share link (…/part/UFP-…?k=KEY). Required with part_number when the part is locked; omit otherwise |
| design_file | object | string | The design file itself (user-attached or generated image/STL). ChatGPT supplies the file reference automatically when the user attached a file — just bind the attachment here. Other clients may pass a data: URL (base64) or a public https URL string. Preferred over file_url. |
| file_url | string | Public URL of the design file — only when the design lives at a URL format: uri |
| attachment_urls | array<string> | Additional files for the SAME part — the PDF drawing next to the STEP, spec sheets, BOMs. Pass everything the user gave you; UFP works out which file is the part and which are supporting documents. |
| ship_to_zip | string | Destination US ZIP code, exactly as the user stated it. OMIT if the user has not given one — NEVER guess or invent a ZIP. Without it, prices come back all-in with shipping to an assumed central-US destination, flagged on routing.ship_to pattern: ^\d{5}(-\d{4})?$ |
| quantities | array<integer> | Quantities the user actually wants — pass [1] or [2] if that's the ask. Vendors with a higher minimum quote AT their minimum and the offer notes it (requested_quantity). Default: 25 for decals, 1 for prints; a part_number reorder defaults to the quantity last purchased |
| material | string | ONLY a material the user actually asked for — NEVER guess or default one (a silent "pla" on a bare file drop prunes every maker that does not stock it; OMIT instead and each process quotes across its stocked materials so every maker can bid). fdm_print: pla|petg|asa (free-form — "abs", "polycarbonate" asks resolve to the closest stocked filament with a substitution note); resin_print: standard|tough|high_temp|high_detail resin (free-form asks resolve to the closest supported resin); powder_print: Powder-bed nylon: nylon_12|nylon_12_smooth|nylon_11|nylon_12_gf|nylon_12_esd|nylon_12_white|nylon_pa2200|nylon_12_sls|tpu (free-form — "PA12", "glass filled" resolve to the closest stocked powder); elastomer_print: Jetted elastomer: tepu_30a|tepu_50a (free-form — "TPU", "soft rubber" resolve to the closest stocked durometer); cnc: aluminum_6061|aluminum_7075|stainless_304|titanium|brass|acetal|delrin|abs|nylon_pa6|peek|acrylic (free-form asks resolve to the closest supported stock); sheetmetal: mild_steel|aluminum_5052|stainless_304 (free-form — "steel", "5052", "stainless" resolve; unknown asks get closest-match offers). Omit to compare the defaults; laser_cut: acrylic|plywood|mdf|delrin|uhmw|hdpe|g10|carbon_fiber|mild_steel|aluminum_5052|stainless_304 (free-form — "plexiglass", "birch" resolve; unknown asks get closest-match offers); decal: vinyl|holographic|transparent|glitter (free-form — "chrome" etc. gets closest matches) |
| color | string | ONLY a color the user actually asked for — NEVER pick one for them. fdm_print: Filament color for fdm_print (e.g. black, red); resin_print: Resin color for resin_print (e.g. gray, white, black); powder_print: Powder part color: raw gray/white, or a dye ("black", "dark blue") — vendor-resolved; elastomer_print: Elastomer part color — VCJ parts ship raw; asks resolve with an honest substitution note; cnc: Colour for cnc: with finish anodized it is the anodize colour, otherwise the stock's own colour (black Delrin, clear acrylic). Colour WORDS only; each maker resolves the shade and says what it landed on; laser_cut: Colour of the flat stock for laser_cut (black, clear, natural…). Colour WORDS only; each maker quotes the materials it stocks in that colour and drops the ones that cannot be it; print: Print color ask ("full color", "black and white"). Vendors that only price full color note the substitution; apparel: Garment color for apparel ("black", "heather gray") — vendor-resolved |
| powder_technology | string | Powder process: mjf (HP Multi Jet Fusion) | sls (laser sintering). Omit to let the vendor pick its default lane for the material |
| powder_finish | string | Powder post-processing: as_printed (raw powder surface) | vapor_polished | polished |
| metal_alloy | string | Metal AM alloy: stainless_316l|stainless_17_4ph|titanium_ti64|aluminum_alsi10mg|inconel_718|cobalt_chrome|tool_steel_h13|copper (free-form asks like "Ti-6Al-4V" resolve to the closest stocked powder) |
| metal_technology | string | Metal AM process: laser_powder_bed (SLM/DMLS/LPBF)|binder_jet|ebm. Omit to let the vendor pick its default for the alloy |
| metal_finish | string | Metal AM post-processing: as_printed|bead_blast|machined_critical|polished|heat_treated (as_printed keeps support witness marks) |
| elastomer_technology | string | Elastomer process: vapor_cure_jetting (VCJ). Omit to let the vendor pick its default lane for the material |
| elastomer_finish | string | Elastomer post-processing: as_printed (VCJ parts ship raw — the whole lane today) |
| shore_a | number | Numeric Shore A durometer ask (10-95, e.g. 40). Resolved to the NEAREST stocked durometer with a substitution note — never a silent swap |
| finish | string | cnc: CNC surface finish: standard|anodized|polished|bead_blasted (default standard); sheetmetal: as_cut (default) | deburred | anodized | powder_coat — anodized is aluminum-only; powder coat protects mild steel for outdoor use |
| thickness_in | number | sheetmetal: Sheet thickness in inches (e.g. 0.063 = 14 ga aluminum). Quoted at the nearest stocked thickness; omit for ~16 ga default; laser_cut: Nominal thickness in inches; quoted at the vendor's nearest stocked thickness. Omit for the material's common stock |
| bend_count | number | Number of bends in the design (bend lines must be in the file). Prices CNC bending; omit for flat parts |
| units | string | sheetmetal: DXF drawing units: "mm" (default) or "in". STEP files carry their own units; laser_cut: DXF drawing units: "mm" (default) or "in" |
| width_in | number | Decal width in inches (default 3) |
| height_in | number | Decal height in inches (default 3) |
| cut | string | Decal cut style — pass the user's words verbatim ("triangle", "die cut", "circle"). Known: contour|square|oval|kiss_cut; anything else gets closest-match offers with a substitution note. Omit to compare the main options |
| product | string | print: Print product kind: business_cards|flyers|posters. Omit to quote every kind the artwork fits; apparel: apparel: t_shirt|hoodie|long_sleeve|tank_top (free-form — "tee", "crewneck" resolve to the closest product) |
| size | string | Print size — pass the user's words verbatim ("letter", "24x36", "half letter"). Cards are 3.5x2; flyers 8.5x5.5|8.5x11|11x17; posters 12x18 through 36x48. Unknown sizes get closest-match offers |
| paper | string | Paper stock — free-form ("matte", "glossy", "recycled", "14pt"). Resolved to the closest stock the vendor runs |
| sides | string | single|double sided printing (defaults: cards double, flyers/posters single) |
| placement | string | Print placement for apparel: front (default) | back | front_back |
| bends | array<object> | Sheet-metal bend lines, each as TWO POINTS in the part's own mm frame (flat DXF parts use z=0: a bend from (0,12.7) to (76.2,12.7) is p1 [0,12.7,0], p2 [76.2,12.7,0]). angle_deg is the target bend angle (90 = a right-angle flange), direction "up"/"down" is the fold direction relative to the flat pattern, radius_mm the requested inside radius (omit it — the shop resolves to its tooling and reports what it used). Pass these when the user articulates WHERE the bends go; a bare "it has 2 bends" is bend_count, not this. |
| bends[].id | string | — minLen: 1 · maxLen: 32 |
| bends[].line* | object | — |
| bends[].line.p1* | array<object> | — |
| bends[].line.p2* | array<object> | — |
| bends[].angle_deg* | number | — |
| bends[].direction* | enum(2) | — one of: "up", "down" |
| bends[].radius_mm | number | — |
| bends[].face_id | integer | — |
| bends[].source | enum(2) | — one of: "detected", "user" |
| tapping | array<object> | Tapped (threaded) holes for a sheet-metal part — one record per hole the user wants threads cut into. `thread` is the callout in the user's words ("M6", "M4 x 0.7", "1/4-20") and is all that's required; when known, add the hole's center in the part's own mm frame (located_at_mm), its unit axis, the pre-tap drilled diameter, and depth_mm so the shop taps the right hole. Pass these when the user asks for threaded/tapped holes; vendors with a tapping service price them. |
| tapping[].hole | integer | — min: 1 |
| tapping[].thread* | string | — minLen: 1 · maxLen: 32 |
| tapping[].face_id | integer | — |
| tapping[].drilled_diameter_mm | number | — |
| tapping[].located_at_mm | object | — |
| tapping[].located_at_mm.x* | number | — |
| tapping[].located_at_mm.y* | number | — |
| tapping[].located_at_mm.z* | number | — |
| tapping[].axis | array<object> | — |
| tapping[].depth_mm | number | — |
| inserts | array<object> | PEM-style hardware inserts pressed into holes of a sheet-metal part — one record per hole. `insert` is the species (nut | flush_nut | standoff | blind_standoff | stud) and `thread` its size ("M4", "1/4-20"); both are required. When known, add length_mm (standoff/stud post length), the hole's center (located_at_mm, part's own mm frame), its axis, the drilled diameter, and `points` — the signed unit vector the insert's functional side faces (flip = negate). Pass these when the user asks for press-in nuts/standoffs/studs; vendors with a hardware service price them. |
| inserts[].hole | integer | — min: 1 |
| inserts[].insert* | enum(5) | — one of: "nut", "flush_nut", "standoff", "blind_standoff", "stud" |
| inserts[].thread* | string | — minLen: 1 · maxLen: 32 |
| inserts[].face_id | integer | — |
| inserts[].points | array<object> | — |
| inserts[].length_mm | number | — |
| inserts[].drilled_diameter_mm | number | — |
| inserts[].located_at_mm | object | — |
| inserts[].located_at_mm.x* | number | — |
| inserts[].located_at_mm.y* | number | — |
| inserts[].located_at_mm.z* | number | — |
| inserts[].axis | array<object> | — |
| inserts[].depth_mm | number | — |
| processes | array<string> | Only quote these fabrication processes — a constraint that narrows the auto-routing fan. Friendly terms accepted ("sheet metal", "3d printing", "cnc", "laser"); unmappable terms are reported, never an error. Usually OMIT: auto-routing quotes every process that can make the file. Pass it only when the user explicitly limits the process |
| ships_from | array<string> | Only vendors that ship from these countries/regions ("only US vendors", "keep it domestic") — an INCLUDE list. Friendly terms accepted ("US", "Europe", "Germany", "China", "UK"); unmappable terms are reported, never an error. Vendors whose origin is unknown or whose network is worldwide (origin not guaranteed) are excluded, each with a note saying why. Usually OMIT: pass it only when the user explicitly limits where vendors ship from |
| vendors | array<string> | Only these specific vendors/makers ("just quote Slant 3D") — an INCLUDE list of vendor names as they appear on offers. Friendly names accepted ("A3D", "slant 3d"); unmatched names are reported, never an error. Usually OMIT: pass it only when the user explicitly names the vendors they want |
| deadline | string | Latest acceptable delivery date, ISO YYYY-MM-DD |
| outdoor_rated | boolean | Must survive outdoor exposure |
| submersible | boolean | Must survive submersion in water |
| high_temp | boolean | Must tolerate sustained heat (vendor heat-resistance claim) |
| food_safe | boolean | Must be vendor-certified food safe |
| requirements | array<string> | Verbatim context terms from the user — materials, finishes, certifications, tolerances ("UV resistant", "anodized: red", "iso 13485", "tolerance: 0.1mm"). UFP applies what it can and reports what it could not; unresolvable terms are logged for vendor sourcing. Do not interrogate the user to fill this — pass what they said. |
| callouts | array<object> | Dimensions you read off the user's drawing that matter ("hole_diameter 6.5mm ±0.1"). The tightest tolerance prunes vendors that cannot hold it. |
| callouts[].name* | string | — |
| callouts[].value* | number | — |
| callouts[].unit* | enum(2) | — one of: "mm", "in" |
| callouts[].tolerance_mm | number | — |
| callouts[].critical | boolean | — |
| max_budget_usd | number | Hard budget cap in USD, all-in |
| min_vendor_stars | number | Only vendors whose displayed review rating is at least this many stars (1-5). Vendors with no reviews yet are excluded — the filter demands demonstrated quality min: 1 · max: 5 |
| min_vendor_reviews | integer | Only vendors with at least this many verified-purchase reviews |
| proven_spec_orders | integer | Only vendors with at least N completed orders for this exact process+material — "a vendor that prints PC reliably" |
Raw schema JSON
{
"name": "get_fabrication_quote",
"description": "Get ranked, purchasable offers (price, ETA, preview image) for fabricating a physical item from a design file. process=fdm_print for 3D printing a model (STL/OBJ/PLY/3MF/AMF/STEP/IGES), process=cnc or process=sheetmetal for machined/bent metal parts (STEP, IGES, DXF), process=decal for stickers/decals from artwork (any common image or design file — PNG/JPG/HEIC/TIFF/GIF/BMP/WEBP/AVIF/SVG/PDF/AI/EPS/PSD/CDR, auto-converted). A .ufp file (UFP part container: the design plus saved spec/constraints in one) is accepted anywhere a design file is — its saved intent applies automatically and anything the user states now wins. If the user just drops a file and asks for a price, omit process — UFP routes it. Provide the design either as design_file (an image/file the user attached or you generated — preferred) or file_url (a public URL). REORDERS: if the user has a UFP part number (from a receipt email or a previous session, looks like UFP-… or part_…), pass it as part_number INSTEAD of any file — the stored design and spec are reused and re-shopped across all current vendors. Locked parts additionally require share_key (from the owner39;s share link). Returns offers across vendors like Google Flights returns flights.",
"inputSchema": {
"type": "object",
"properties": {
"process": {
"type": "string",
"enum": [
"fdm_print",
"resin_print",
"powder_print",
"metal_print",
"elastomer_print",
"cnc",
"sheetmetal",
"laser_cut",
"decal",
"print",
"apparel"
],
"description": "What to fabricate. If the user just drops a file and asks for a price, OMIT this — UFP detects the file type (artwork, mesh — STL/OBJ/PLY/3MF/AMF, BREP — STEP/IGES, DXF) and routes it to every process that can make it; the response39;s routing.also_possible lists processes UFP can39;t quote yet"
},
"part_number": {
"type": "string",
"description": "UFP part number from a previous paid order (UFP-… or part_…). Reorders: replaces design_file/file_url entirely; any other fields provided override the stored spec"
},
"share_key": {
"type": "string",
"description": "Share key for a LOCKED part — the k=… value from the owner39;s share link (…/part/UFP-…?k=KEY). Required with part_number when the part is locked; omit otherwise"
},
"design_file": {
"anyOf": [
{
"type": "object",
"properties": {
"file_id": {
"type": "string"
},
"download_url": {
"type": "string"
},
"mime_type": {
"type": "string"
},
"file_name": {
"type": "string"
}
},
"required": [
"file_id",
"download_url"
],
"additionalProperties": false
},
{
"type": "string"
}
],
"description": "The design file itself (user-attached or generated image/STL). ChatGPT supplies the file reference automatically when the user attached a file — just bind the attachment here. Other clients may pass a data: URL (base64) or a public https URL string. Preferred over file_url."
},
"file_url": {
"type": "string",
"format": "uri",
"description": "Public URL of the design file — only when the design lives at a URL"
},
"attachment_urls": {
"type": "array",
"items": {
"type": "string",
"format": "uri"
},
"maxItems": 10,
"description": "Additional files for the SAME part — the PDF drawing next to the STEP, spec sheets, BOMs. Pass everything the user gave you; UFP works out which file is the part and which are supporting documents."
},
"ship_to_zip": {
"type": "string",
"pattern": "^\\d{5}(-\\d{4})?$",
"description": "Destination US ZIP code, exactly as the user stated it. OMIT if the user has not given one — NEVER guess or invent a ZIP. Without it, prices come back all-in with shipping to an assumed central-US destination, flagged on routing.ship_to"
},
"quantities": {
"type": "array",
"items": {
"type": "integer",
"exclusiveMinimum": 0
},
"maxItems": 5,
"description": "Quantities the user actually wants — pass [1] or [2] if that39;s the ask. Vendors with a higher minimum quote AT their minimum and the offer notes it (requested_quantity). Default: 25 for decals, 1 for prints; a part_number reorder defaults to the quantity last purchased"
},
"material": {
"type": "string",
"description": "ONLY a material the user actually asked for — NEVER guess or default one (a silent \"pla\" on a bare file drop prunes every maker that does not stock it; OMIT instead and each process quotes across its stocked materials so every maker can bid). fdm_print: pla|petg|asa (free-form — \"abs\", \"polycarbonate\" asks resolve to the closest stocked filament with a substitution note); resin_print: standard|tough|high_temp|high_detail resin (free-form asks resolve to the closest supported resin); powder_print: Powder-bed nylon: nylon_12|nylon_12_smooth|nylon_11|nylon_12_gf|nylon_12_esd|nylon_12_white|nylon_pa2200|nylon_12_sls|tpu (free-form — \"PA12\", \"glass filled\" resolve to the closest stocked powder); elastomer_print: Jetted elastomer: tepu_30a|tepu_50a (free-form — \"TPU\", \"soft rubber\" resolve to the closest stocked durometer); cnc: aluminum_6061|aluminum_7075|stainless_304|titanium|brass|acetal|delrin|abs|nylon_pa6|peek|acrylic (free-form asks resolve to the closest supported stock); sheetmetal: mild_steel|aluminum_5052|stainless_304 (free-form — \"steel\", \"5052\", \"stainless\" resolve; unknown asks get closest-match offers). Omit to compare the defaults; laser_cut: acrylic|plywood|mdf|delrin|uhmw|hdpe|g10|carbon_fiber|mild_steel|aluminum_5052|stainless_304 (free-form — \"plexiglass\", \"birch\" resolve; unknown asks get closest-match offers); decal: vinyl|holographic|transparent|glitter (free-form — \"chrome\" etc. gets closest matches)"
},
"color": {
"type": "string",
"description": "ONLY a color the user actually asked for — NEVER pick one for them. fdm_print: Filament color for fdm_print (e.g. black, red); resin_print: Resin color for resin_print (e.g. gray, white, black); powder_print: Powder part color: raw gray/white, or a dye (\"black\", \"dark blue\") — vendor-resolved; elastomer_print: Elastomer part color — VCJ parts ship raw; asks resolve with an honest substitution note; cnc: Colour for cnc: with finish anodized it is the anodize colour, otherwise the stock39;s own colour (black Delrin, clear acrylic). Colour WORDS only; each maker resolves the shade and says what it landed on; laser_cut: Colour of the flat stock for laser_cut (black, clear, natural…). Colour WORDS only; each maker quotes the materials it stocks in that colour and drops the ones that cannot be it; print: Print color ask (\"full color\", \"black and white\"). Vendors that only price full color note the substitution; apparel: Garment color for apparel (\"black\", \"heather gray\") — vendor-resolved"
},
"powder_technology": {
"type": "string",
"description": "Powder process: mjf (HP Multi Jet Fusion) | sls (laser sintering). Omit to let the vendor pick its default lane for the material"
},
"powder_finish": {
"type": "string",
"description": "Powder post-processing: as_printed (raw powder surface) | vapor_polished | polished"
},
"metal_alloy": {
"type": "string",
"description": "Metal AM alloy: stainless_316l|stainless_17_4ph|titanium_ti64|aluminum_alsi10mg|inconel_718|cobalt_chrome|tool_steel_h13|copper (free-form asks like \"Ti-6Al-4V\" resolve to the closest stocked powder)"
},
"metal_technology": {
"type": "string",
"description": "Metal AM process: laser_powder_bed (SLM/DMLS/LPBF)|binder_jet|ebm. Omit to let the vendor pick its default for the alloy"
},
"metal_finish": {
"type": "string",
"description": "Metal AM post-processing: as_printed|bead_blast|machined_critical|polished|heat_treated (as_printed keeps support witness marks)"
},
"elastomer_technology": {
"type": "string",
"description": "Elastomer process: vapor_cure_jetting (VCJ). Omit to let the vendor pick its default lane for the material"
},
"elastomer_finish": {
"type": "string",
"description": "Elastomer post-processing: as_printed (VCJ parts ship raw — the whole lane today)"
},
"shore_a": {
"type": "number",
"exclusiveMinimum": 0,
"description": "Numeric Shore A durometer ask (10-95, e.g. 40). Resolved to the NEAREST stocked durometer with a substitution note — never a silent swap"
},
"finish": {
"type": "string",
"description": "cnc: CNC surface finish: standard|anodized|polished|bead_blasted (default standard); sheetmetal: as_cut (default) | deburred | anodized | powder_coat — anodized is aluminum-only; powder coat protects mild steel for outdoor use"
},
"thickness_in": {
"type": "number",
"exclusiveMinimum": 0,
"description": "sheetmetal: Sheet thickness in inches (e.g. 0.063 = 14 ga aluminum). Quoted at the nearest stocked thickness; omit for ~16 ga default; laser_cut: Nominal thickness in inches; quoted at the vendor39;s nearest stocked thickness. Omit for the material39;s common stock"
},
"bend_count": {
"type": "number",
"exclusiveMinimum": 0,
"description": "Number of bends in the design (bend lines must be in the file). Prices CNC bending; omit for flat parts"
},
"units": {
"type": "string",
"description": "sheetmetal: DXF drawing units: \"mm\" (default) or \"in\". STEP files carry their own units; laser_cut: DXF drawing units: \"mm\" (default) or \"in\""
},
"width_in": {
"type": "number",
"exclusiveMinimum": 0,
"description": "Decal width in inches (default 3)"
},
"height_in": {
"type": "number",
"exclusiveMinimum": 0,
"description": "Decal height in inches (default 3)"
},
"cut": {
"type": "string",
"description": "Decal cut style — pass the user39;s words verbatim (\"triangle\", \"die cut\", \"circle\"). Known: contour|square|oval|kiss_cut; anything else gets closest-match offers with a substitution note. Omit to compare the main options"
},
"product": {
"type": "string",
"description": "print: Print product kind: business_cards|flyers|posters. Omit to quote every kind the artwork fits; apparel: apparel: t_shirt|hoodie|long_sleeve|tank_top (free-form — \"tee\", \"crewneck\" resolve to the closest product)"
},
"size": {
"type": "string",
"description": "Print size — pass the user39;s words verbatim (\"letter\", \"24x36\", \"half letter\"). Cards are 3.5x2; flyers 8.5x5.5|8.5x11|11x17; posters 12x18 through 36x48. Unknown sizes get closest-match offers"
},
"paper": {
"type": "string",
"description": "Paper stock — free-form (\"matte\", \"glossy\", \"recycled\", \"14pt\"). Resolved to the closest stock the vendor runs"
},
"sides": {
"type": "string",
"description": "single|double sided printing (defaults: cards double, flyers/posters single)"
},
"placement": {
"type": "string",
"description": "Print placement for apparel: front (default) | back | front_back"
},
"bends": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"line": {
"type": "object",
"properties": {
"p1": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"p2": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
}
},
"required": [
"p1",
"p2"
],
"additionalProperties": false
},
"angle_deg": {
"type": "number",
"exclusiveMinimum": 0,
"exclusiveMaximum": 180
},
"direction": {
"type": "string",
"enum": [
"up",
"down"
]
},
"radius_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"face_id": {
"type": "integer"
},
"source": {
"type": "string",
"enum": [
"detected",
"user"
]
}
},
"required": [
"line",
"angle_deg",
"direction"
],
"additionalProperties": false
},
"maxItems": 50,
"description": "Sheet-metal bend lines, each as TWO POINTS in the part39;s own mm frame (flat DXF parts use z=0: a bend from (0,12.7) to (76.2,12.7) is p1 [0,12.7,0], p2 [76.2,12.7,0]). angle_deg is the target bend angle (90 = a right-angle flange), direction \"up\"/\"down\" is the fold direction relative to the flat pattern, radius_mm the requested inside radius (omit it — the shop resolves to its tooling and reports what it used). Pass these when the user articulates WHERE the bends go; a bare \"it has 2 bends\" is bend_count, not this."
},
"tapping": {
"type": "array",
"items": {
"type": "object",
"properties": {
"hole": {
"type": "integer",
"minimum": 1
},
"thread": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"face_id": {
"type": "integer"
},
"drilled_diameter_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"located_at_mm": {
"type": "object",
"properties": {
"x": {
"type": "number"
},
"y": {
"type": "number"
},
"z": {
"type": "number"
}
},
"required": [
"x",
"y",
"z"
],
"additionalProperties": false
},
"axis": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"depth_mm": {
"type": "number",
"exclusiveMinimum": 0
}
},
"required": [
"thread"
],
"additionalProperties": false
},
"maxItems": 200,
"description": "Tapped (threaded) holes for a sheet-metal part — one record per hole the user wants threads cut into. `thread` is the callout in the user39;s words (\"M6\", \"M4 x 0.7\", \"1/4-20\") and is all that39;s required; when known, add the hole39;s center in the part39;s own mm frame (located_at_mm), its unit axis, the pre-tap drilled diameter, and depth_mm so the shop taps the right hole. Pass these when the user asks for threaded/tapped holes; vendors with a tapping service price them."
},
"inserts": {
"type": "array",
"items": {
"type": "object",
"properties": {
"hole": {
"type": "integer",
"minimum": 1
},
"insert": {
"type": "string",
"enum": [
"nut",
"flush_nut",
"standoff",
"blind_standoff",
"stud"
]
},
"thread": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"face_id": {
"type": "integer"
},
"points": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"length_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"drilled_diameter_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"located_at_mm": {
"type": "object",
"properties": {
"x": {
"type": "number"
},
"y": {
"type": "number"
},
"z": {
"type": "number"
}
},
"required": [
"x",
"y",
"z"
],
"additionalProperties": false
},
"axis": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"depth_mm": {
"type": "number",
"exclusiveMinimum": 0
}
},
"required": [
"insert",
"thread"
],
"additionalProperties": false
},
"maxItems": 200,
"description": "PEM-style hardware inserts pressed into holes of a sheet-metal part — one record per hole. `insert` is the species (nut | flush_nut | standoff | blind_standoff | stud) and `thread` its size (\"M4\", \"1/4-20\"); both are required. When known, add length_mm (standoff/stud post length), the hole39;s center (located_at_mm, part39;s own mm frame), its axis, the drilled diameter, and `points` — the signed unit vector the insert39;s functional side faces (flip = negate). Pass these when the user asks for press-in nuts/standoffs/studs; vendors with a hardware service price them."
},
"processes": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 8,
"description": "Only quote these fabrication processes — a constraint that narrows the auto-routing fan. Friendly terms accepted (\"sheet metal\", \"3d printing\", \"cnc\", \"laser\"); unmappable terms are reported, never an error. Usually OMIT: auto-routing quotes every process that can make the file. Pass it only when the user explicitly limits the process"
},
"ships_from": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 8,
"description": "Only vendors that ship from these countries/regions (\"only US vendors\", \"keep it domestic\") — an INCLUDE list. Friendly terms accepted (\"US\", \"Europe\", \"Germany\", \"China\", \"UK\"); unmappable terms are reported, never an error. Vendors whose origin is unknown or whose network is worldwide (origin not guaranteed) are excluded, each with a note saying why. Usually OMIT: pass it only when the user explicitly limits where vendors ship from"
},
"vendors": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 16,
"description": "Only these specific vendors/makers (\"just quote Slant 3D\") — an INCLUDE list of vendor names as they appear on offers. Friendly names accepted (\"A3D\", \"slant 3d\"); unmatched names are reported, never an error. Usually OMIT: pass it only when the user explicitly names the vendors they want"
},
"deadline": {
"type": "string",
"description": "Latest acceptable delivery date, ISO YYYY-MM-DD"
},
"outdoor_rated": {
"type": "boolean",
"description": "Must survive outdoor exposure"
},
"submersible": {
"type": "boolean",
"description": "Must survive submersion in water"
},
"high_temp": {
"type": "boolean",
"description": "Must tolerate sustained heat (vendor heat-resistance claim)"
},
"food_safe": {
"type": "boolean",
"description": "Must be vendor-certified food safe"
},
"requirements": {
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 120
},
"maxItems": 20,
"description": "Verbatim context terms from the user — materials, finishes, certifications, tolerances (\"UV resistant\", \"anodized: red\", \"iso 13485\", \"tolerance: 0.1mm\"). UFP applies what it can and reports what it could not; unresolvable terms are logged for vendor sourcing. Do not interrogate the user to fill this — pass what they said."
},
"callouts": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "number"
},
"unit": {
"type": "string",
"enum": [
"mm",
"in"
]
},
"tolerance_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"critical": {
"type": "boolean"
}
},
"required": [
"name",
"value",
"unit"
],
"additionalProperties": false
},
"maxItems": 50,
"description": "Dimensions you read off the user39;s drawing that matter (\"hole_diameter 6.5mm ±0.1\"). The tightest tolerance prunes vendors that cannot hold it."
},
"max_budget_usd": {
"type": "number",
"exclusiveMinimum": 0,
"description": "Hard budget cap in USD, all-in"
},
"min_vendor_stars": {
"type": "number",
"minimum": 1,
"maximum": 5,
"description": "Only vendors whose displayed review rating is at least this many stars (1-5). Vendors with no reviews yet are excluded — the filter demands demonstrated quality"
},
"min_vendor_reviews": {
"type": "integer",
"exclusiveMinimum": 0,
"description": "Only vendors with at least this many verified-purchase reviews"
},
"proven_spec_orders": {
"type": "integer",
"exclusiveMinimum": 0,
"description": "Only vendors with at least N completed orders for this exact process+material — \"a vendor that prints PC reliably\""
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}refine_quote
34 params · 1 required
Narrow an existing quote with new constraints (destination ZIP the user just provided, deadline, outdoor/water…
Narrow an existing quote with new constraints (destination ZIP the user just provided, deadline, outdoor/waterproof/heat/food-safety requirements, budget, vendor reliability, verbatim requirements terms, drawing callouts, a process filter — "no, I meant in sheet metal" → processes — a ship-from country filter — "only US vendors" → ships_from — or a vendor filter — "only show A3D Manufacturing" → vendors) — or CHANGE its spec: material, color, or quantities. Changing material/quantity is a spec change, not a narrowing — pass it via the material/color/quantities args, NOT as a requirements term; the affected lanes re-price with the new spec through warm vendor sessions. For side-by-side comparisons ("how does carbon steel compare?"), add a scenario label — labeled refines coexist instead of replacing each other (max 4). "Organize by" ("sort by cheapest", "soonest arrival on top", "most green first") is also this tool: sort_by for objective orders, sort_order + sort_label for orders you judged yourself from the previews — presentation only, instant, nothing re-prices. GOING BACK is also this tool: undo_last_step ALONE takes back exactly one refine step (the quote's steps[] names each step, newest first — the network restores the previous stored state exactly); clear removes whole constraints ("drop the deadline" → clear ["deadline"]); remove_requirements takes back individual requirements terms. Call with ONLY quote_id to re-read the quote (e.g. to pick up preview images that finished rendering).
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| quote_id* | string | — |
| scenario | string | Comparison lane label. A labeled refine sits SIDE BY SIDE with the quote's other offers instead of replacing them: refines with the same label replace that scenario, different labels coexist (max 4 per quote), and a refine WITHOUT a scenario resets the baseline and supersedes every lane. "How does X compare to Y?" = one labeled refine per scenario (e.g. scenario "carbon steel" + material "carbon steel", then scenario "aluminum" + material "aluminum"). Keep labels short and human, like "carbon steel" minLen: 1 · maxLen: 40 |
| material | string | null | New material for this part ("I need it in PLA" → "pla"). A spec change: lanes requote with this material through warm vendor sessions; an explicit material here replaces the quote's material fan-out. Free-form — unstocked asks resolve to the closest stocked material with a substitution note. Do NOT pass material changes as requirements terms. Pass null to REMOVE a previously asked material ("forget the aluminum ask") — the ask comes off the record and the process-default material fan returns |
| color | string | null | New color for this part (spec change — lanes requote). Colour WORDS only ('black', 'green', 'clear'); the network resolves them to each maker's stocked shades, dyes, filaments or coatings — a family word ('blue') brings back EVERY stocked shade of it, and the quote's color_shades_available lists them — never pass a material or a shade you invented. Pass null to REMOVE a previously asked color — back to vendor defaults |
| color_shades | array<string> | null | Narrow the board to these color SHADES exactly as the quote lists them (color_shades_available / "Colors on this board") — instant, nothing re-prices, the same quote id comes back with only those shades; pass null to show every shade again. Never invent a shade name. |
| finish | string | null | New surface finish ("powder coat", "anodized", "bead blasted") — a spec change: finish-capable lanes (sheet metal, CNC, metal print) requote WITH it; 3D-print lanes have no coating step, so they ignore the finish but keep the COLOR. A colored finish ask ("black powder coat") should set BOTH finish and color, so every lane lands on the buyer's color. Pass null to REMOVE a previously asked finish |
| thickness_in | number | null | New sheet thickness in INCHES ("make it in 1/8" → 0.125) — a spec change: sheet lanes requote at the nearest stocked gauge, flagging the substitution when the match isn't close. Pass null to REMOVE a previously asked thickness — back to the material's default gauge |
| bends | object | array<object> | null | New bend records for this part — a spec change: sheet lanes requote with exactly these bends (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: each bend is two points in the part's own mm frame (flat DXF parts use z=0) plus angle_deg, direction up|down, and an optional requested radius_mm. Pass null to REMOVE every articulated bend |
| tapping | object | array<object> | null | New tapped-hole records for this part — a spec change: sheet lanes requote with exactly these taps (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: thread callout ("M6", "1/4-20") required, hole geometry optional. Pass null to REMOVE every tap |
| inserts | object | array<object> | null | New hardware-insert records for this part — a spec change: sheet lanes requote with exactly these inserts (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: species (nut|flush_nut|standoff|blind_standoff|stud) and thread required, hole geometry optional. Pass null to REMOVE every insert |
| quantities | array<integer> | null | New quantities the user wants (spec change — lanes requote at the new quantity). Same rules as on get_fabrication_quote: pass the real ask, never inflate it. Pass null to REMOVE a previously asked quantity — the quote returns to single-part pricing |
| scale | object | Rescale the DESIGN ITSELF before re-quoting: per-axis stretch factors over the file's current geometry ("make it 2x bigger" = {"x":2,"y":2,"z":2}). Mesh designs are genuinely converted — the child quote prices a rescaled file; STEP/IGES designs keep their original file with the dimensions riding as callouts (pass those too). {1,1,1} is a no-op |
| scale.x* | number | — min: 0.01 · max: 100 |
| scale.y* | number | — min: 0.01 · max: 100 |
| scale.z* | number | — min: 0.01 · max: 100 |
| processes | array<string> | Narrow this quote to specific fabrication processes ("no, I meant in sheet metal" → ["sheet metal"]). A CONSTRAINT, not a new quote: excluded lanes drop while warm vendor sessions survive, and further refines inherit the filter. Friendly terms accepted ("sheet metal", "3d printing", "cnc", "laser"); pass ["any"] to clear the filter and show every process again. When comparison scenarios are open and the user narrows the process, re-refine EVERY active scenario label with this same arg so all columns prune together |
| ships_from | array<string> | Only vendors that ship from these countries/regions ("only US vendors", "just European shops", "keep it domestic") — an INCLUDE list naming where the user DOES want vendors from. A CONSTRAINT like processes: non-matching vendors drop instantly (nothing re-prices), further refines inherit the filter, and ["any"] clears it to show vendors everywhere again. Friendly terms accepted ("US", "Europe", "Germany", "China", "UK"). Vendors whose origin is unknown or whose network is worldwide (a specific origin cannot be guaranteed) are excluded, each with an honest note. For "nothing from X" asks, pass the regions the user does want instead |
| vendors | array<string> | Only these specific vendors/makers ("only show A3D Manufacturing", "just Slant 3D and Fictiv") — an INCLUDE list of vendor names as they appear on offers. A CONSTRAINT like processes: other vendors' offers drop instantly (nothing re-prices), further refines inherit the filter, and ["any"] clears it to show every vendor again. Friendly names accepted ("A3D", "slant 3d"); unmatched names are reported, never an error. This is THE way to answer "show me everything vendor X offers" — the filtered quote lists that vendor's complete lineup |
| ship_to_zip | string | Destination US ZIP code, exactly as the user stated it — use this when the user provides their ZIP after a quote priced to the assumed central-US destination (routing.ship_to); the refined prices become theirs. NEVER guess or invent a ZIP pattern: ^\d{5}(-\d{4})?$ |
| deadline | string | Latest acceptable delivery date, ISO YYYY-MM-DD |
| outdoor_rated | boolean | — |
| submersible | boolean | — |
| high_temp | boolean | — |
| food_safe | boolean | — |
| requirements | array<string> | Verbatim context terms from the user — materials, finishes, certifications, tolerances ("UV resistant", "anodized: red", "iso 13485", "tolerance: 0.1mm"). UFP applies what it can and reports what it could not; unresolvable terms are logged for vendor sourcing. Do not interrogate the user to fill this — pass what they said. |
| callouts | array<object> | Dimensions you read off the user's drawing that matter ("hole_diameter 6.5mm ±0.1"). The tightest tolerance prunes vendors that cannot hold it. |
| callouts[].name* | string | — |
| callouts[].value* | number | — |
| callouts[].unit* | enum(2) | — one of: "mm", "in" |
| callouts[].tolerance_mm | number | — |
| callouts[].critical | boolean | — |
| max_budget_usd | number | — |
| min_vendor_stars | number | Only vendors whose displayed review rating is at least this many stars (1-5); vendors with no reviews yet are excluded min: 1 · max: 5 |
| min_vendor_reviews | integer | Only vendors with at least this many verified-purchase reviews |
| proven_spec_orders | integer | Only vendors with at least N completed orders for this exact process+material — "a vendor that prints PC reliably" |
| clear | array<enum(11)> | REMOVE constraints entirely ("drop the deadline", "forget the budget", "no more food-safe requirement"): list the constraints to clear and each is removed from the quote — the one deliberate widening besides undo. Clearing a deadline or budget answers instantly from held offers (near-misses convert back); clearing an attribute/reliability/requirements demand re-prices honestly. Same effect as ["any"] on the three filter args, extended to every constraint |
| remove_requirements | array<string> | Take back INDIVIDUAL requirements terms ("drop the anodized ask, keep the rest"): each listed term is removed from the quote's requirements by normalized match, the others stay. Unknown terms are ignored, never an error. Re-stating the requirements list can never drop a term (terms merge as a union) — this is the removal channel |
| undo_last_step | boolean | GO BACK EXACTLY ONE STEP ("undo that", "go back", "put it back how it was"): the network restores the previous quote's stored spec and constraints EXACTLY — never reconstructed from conversation — and re-prices where needed. Send it ALONE (no other args besides quote_id); combining it with changes is rejected. The quote's steps[] names what each undo would take back — steps[0] is the newest. Undo resets the baseline like any unlabeled refine, so open comparison scenarios close. Undoing the original quote is rejected with honest wording — relay it |
| sort_by | enum(6) | "Organize by": re-order the quote's offer cards ("sort by cheapest" → "price"; "soonest arrival first" → "arrival"; "best rated" → "rating"; "total_price" = part + cheapest shipping; "recommended" restores the default price+speed rank). PURE PRESENTATION — answers instantly on the same quote, never re-prices or drops offers, and the ordering sticks across re-reads, streaming, and later refines until changed one of: "recommended", "price", "unit_price", "total_price", "arrival", "rating" |
| sort_direction | enum(2) | Flip a sort_by ordering: "desc" reverses the key's natural direction ("most expensive first" = sort_by "price" + "desc"). Only meaningful with sort_by one of: "asc", "desc" |
| sort_order | array<string> | EXPLICIT card order for asks only you can judge ("sort the most green to the top"): look at the offers' preview images, decide the order yourself, and pass the offer ids first-on-top. Offers you leave out (including ones that stream in later) land below the listed ones in the default rank. Pass sort_label with it |
| sort_label | string | Short human wording for a sort_order, displayed on the board ("most green first") — required with sort_order, since only you know what your order means minLen: 1 · maxLen: 60 |
Raw schema JSON
{
"name": "refine_quote",
"description": "Narrow an existing quote with new constraints (destination ZIP the user just provided, deadline, outdoor/waterproof/heat/food-safety requirements, budget, vendor reliability, verbatim requirements terms, drawing callouts, a process filter — \"no, I meant in sheet metal\" → processes — a ship-from country filter — \"only US vendors\" → ships_from — or a vendor filter — \"only show A3D Manufacturing\" → vendors) — or CHANGE its spec: material, color, or quantities. Changing material/quantity is a spec change, not a narrowing — pass it via the material/color/quantities args, NOT as a requirements term; the affected lanes re-price with the new spec through warm vendor sessions. For side-by-side comparisons (\"how does carbon steel compare?\"), add a scenario label — labeled refines coexist instead of replacing each other (max 4). \"Organize by\" (\"sort by cheapest\", \"soonest arrival on top\", \"most green first\") is also this tool: sort_by for objective orders, sort_order + sort_label for orders you judged yourself from the previews — presentation only, instant, nothing re-prices. GOING BACK is also this tool: undo_last_step ALONE takes back exactly one refine step (the quote39;s steps[] names each step, newest first — the network restores the previous stored state exactly); clear removes whole constraints (\"drop the deadline\" → clear [\"deadline\"]); remove_requirements takes back individual requirements terms. Call with ONLY quote_id to re-read the quote (e.g. to pick up preview images that finished rendering).",
"inputSchema": {
"type": "object",
"properties": {
"quote_id": {
"type": "string"
},
"scenario": {
"type": "string",
"minLength": 1,
"maxLength": 40,
"description": "Comparison lane label. A labeled refine sits SIDE BY SIDE with the quote39;s other offers instead of replacing them: refines with the same label replace that scenario, different labels coexist (max 4 per quote), and a refine WITHOUT a scenario resets the baseline and supersedes every lane. \"How does X compare to Y?\" = one labeled refine per scenario (e.g. scenario \"carbon steel\" + material \"carbon steel\", then scenario \"aluminum\" + material \"aluminum\"). Keep labels short and human, like \"carbon steel\""
},
"material": {
"type": [
"string",
"null"
],
"description": "New material for this part (\"I need it in PLA\" → \"pla\"). A spec change: lanes requote with this material through warm vendor sessions; an explicit material here replaces the quote39;s material fan-out. Free-form — unstocked asks resolve to the closest stocked material with a substitution note. Do NOT pass material changes as requirements terms. Pass null to REMOVE a previously asked material (\"forget the aluminum ask\") — the ask comes off the record and the process-default material fan returns"
},
"color": {
"type": [
"string",
"null"
],
"description": "New color for this part (spec change — lanes requote). Colour WORDS only (39;black39;, 39;green39;, 39;clear39;); the network resolves them to each maker39;s stocked shades, dyes, filaments or coatings — a family word (39;blue39;) brings back EVERY stocked shade of it, and the quote39;s color_shades_available lists them — never pass a material or a shade you invented. Pass null to REMOVE a previously asked color — back to vendor defaults"
},
"color_shades": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 48
},
"maxItems": 64
},
{
"type": "null"
}
],
"description": "Narrow the board to these color SHADES exactly as the quote lists them (color_shades_available / \"Colors on this board\") — instant, nothing re-prices, the same quote id comes back with only those shades; pass null to show every shade again. Never invent a shade name."
},
"finish": {
"type": [
"string",
"null"
],
"description": "New surface finish (\"powder coat\", \"anodized\", \"bead blasted\") — a spec change: finish-capable lanes (sheet metal, CNC, metal print) requote WITH it; 3D-print lanes have no coating step, so they ignore the finish but keep the COLOR. A colored finish ask (\"black powder coat\") should set BOTH finish and color, so every lane lands on the buyer39;s color. Pass null to REMOVE a previously asked finish"
},
"thickness_in": {
"anyOf": [
{
"type": "number",
"exclusiveMinimum": 0,
"maximum": 1
},
{
"type": "null"
}
],
"description": "New sheet thickness in INCHES (\"make it in 1/8\" → 0.125) — a spec change: sheet lanes requote at the nearest stocked gauge, flagging the substitution when the match isn39;t close. Pass null to REMOVE a previously asked thickness — back to the material39;s default gauge"
},
"bends": {
"anyOf": [
{
"anyOf": [
{
"not": {}
},
{
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"line": {
"type": "object",
"properties": {
"p1": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"p2": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
}
},
"required": [
"p1",
"p2"
],
"additionalProperties": false
},
"angle_deg": {
"type": "number",
"exclusiveMinimum": 0,
"exclusiveMaximum": 180
},
"direction": {
"type": "string",
"enum": [
"up",
"down"
]
},
"radius_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"face_id": {
"type": "integer"
},
"source": {
"type": "string",
"enum": [
"detected",
"user"
]
}
},
"required": [
"line",
"angle_deg",
"direction"
],
"additionalProperties": false
},
"maxItems": 50
}
],
"description": "Sheet-metal bend lines, each as TWO POINTS in the part39;s own mm frame (flat DXF parts use z=0: a bend from (0,12.7) to (76.2,12.7) is p1 [0,12.7,0], p2 [76.2,12.7,0]). angle_deg is the target bend angle (90 = a right-angle flange), direction \"up\"/\"down\" is the fold direction relative to the flat pattern, radius_mm the requested inside radius (omit it — the shop resolves to its tooling and reports what it used). Pass these when the user articulates WHERE the bends go; a bare \"it has 2 bends\" is bend_count, not this."
},
{
"type": "null"
}
],
"description": "New bend records for this part — a spec change: sheet lanes requote with exactly these bends (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: each bend is two points in the part39;s own mm frame (flat DXF parts use z=0) plus angle_deg, direction up|down, and an optional requested radius_mm. Pass null to REMOVE every articulated bend"
},
"tapping": {
"anyOf": [
{
"anyOf": [
{
"not": {}
},
{
"type": "array",
"items": {
"type": "object",
"properties": {
"hole": {
"type": "integer",
"minimum": 1
},
"thread": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"face_id": {
"type": "integer"
},
"drilled_diameter_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"located_at_mm": {
"type": "object",
"properties": {
"x": {
"type": "number"
},
"y": {
"type": "number"
},
"z": {
"type": "number"
}
},
"required": [
"x",
"y",
"z"
],
"additionalProperties": false
},
"axis": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"depth_mm": {
"type": "number",
"exclusiveMinimum": 0
}
},
"required": [
"thread"
],
"additionalProperties": false
},
"maxItems": 200
}
],
"description": "Tapped (threaded) holes for a sheet-metal part — one record per hole the user wants threads cut into. `thread` is the callout in the user39;s words (\"M6\", \"M4 x 0.7\", \"1/4-20\") and is all that39;s required; when known, add the hole39;s center in the part39;s own mm frame (located_at_mm), its unit axis, the pre-tap drilled diameter, and depth_mm so the shop taps the right hole. Pass these when the user asks for threaded/tapped holes; vendors with a tapping service price them."
},
{
"type": "null"
}
],
"description": "New tapped-hole records for this part — a spec change: sheet lanes requote with exactly these taps (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: thread callout (\"M6\", \"1/4-20\") required, hole geometry optional. Pass null to REMOVE every tap"
},
"inserts": {
"anyOf": [
{
"anyOf": [
{
"not": {}
},
{
"type": "array",
"items": {
"type": "object",
"properties": {
"hole": {
"type": "integer",
"minimum": 1
},
"insert": {
"type": "string",
"enum": [
"nut",
"flush_nut",
"standoff",
"blind_standoff",
"stud"
]
},
"thread": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"face_id": {
"type": "integer"
},
"points": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"length_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"drilled_diameter_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"located_at_mm": {
"type": "object",
"properties": {
"x": {
"type": "number"
},
"y": {
"type": "number"
},
"z": {
"type": "number"
}
},
"required": [
"x",
"y",
"z"
],
"additionalProperties": false
},
"axis": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"depth_mm": {
"type": "number",
"exclusiveMinimum": 0
}
},
"required": [
"insert",
"thread"
],
"additionalProperties": false
},
"maxItems": 200
}
],
"description": "PEM-style hardware inserts pressed into holes of a sheet-metal part — one record per hole. `insert` is the species (nut | flush_nut | standoff | blind_standoff | stud) and `thread` its size (\"M4\", \"1/4-20\"); both are required. When known, add length_mm (standoff/stud post length), the hole39;s center (located_at_mm, part39;s own mm frame), its axis, the drilled diameter, and `points` — the signed unit vector the insert39;s functional side faces (flip = negate). Pass these when the user asks for press-in nuts/standoffs/studs; vendors with a hardware service price them."
},
{
"type": "null"
}
],
"description": "New hardware-insert records for this part — a spec change: sheet lanes requote with exactly these inserts (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: species (nut|flush_nut|standoff|blind_standoff|stud) and thread required, hole geometry optional. Pass null to REMOVE every insert"
},
"quantities": {
"anyOf": [
{
"type": "array",
"items": {
"type": "integer",
"exclusiveMinimum": 0
},
"maxItems": 5
},
{
"type": "null"
}
],
"description": "New quantities the user wants (spec change — lanes requote at the new quantity). Same rules as on get_fabrication_quote: pass the real ask, never inflate it. Pass null to REMOVE a previously asked quantity — the quote returns to single-part pricing"
},
"scale": {
"type": "object",
"properties": {
"x": {
"type": "number",
"minimum": 0.01,
"maximum": 100
},
"y": {
"type": "number",
"minimum": 0.01,
"maximum": 100
},
"z": {
"type": "number",
"minimum": 0.01,
"maximum": 100
}
},
"required": [
"x",
"y",
"z"
],
"additionalProperties": false,
"description": "Rescale the DESIGN ITSELF before re-quoting: per-axis stretch factors over the file39;s current geometry (\"make it 2x bigger\" = {\"x\":2,\"y\":2,\"z\":2}). Mesh designs are genuinely converted — the child quote prices a rescaled file; STEP/IGES designs keep their original file with the dimensions riding as callouts (pass those too). {1,1,1} is a no-op"
},
"processes": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 8,
"description": "Narrow this quote to specific fabrication processes (\"no, I meant in sheet metal\" → [\"sheet metal\"]). A CONSTRAINT, not a new quote: excluded lanes drop while warm vendor sessions survive, and further refines inherit the filter. Friendly terms accepted (\"sheet metal\", \"3d printing\", \"cnc\", \"laser\"); pass [\"any\"] to clear the filter and show every process again. When comparison scenarios are open and the user narrows the process, re-refine EVERY active scenario label with this same arg so all columns prune together"
},
"ships_from": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 8,
"description": "Only vendors that ship from these countries/regions (\"only US vendors\", \"just European shops\", \"keep it domestic\") — an INCLUDE list naming where the user DOES want vendors from. A CONSTRAINT like processes: non-matching vendors drop instantly (nothing re-prices), further refines inherit the filter, and [\"any\"] clears it to show vendors everywhere again. Friendly terms accepted (\"US\", \"Europe\", \"Germany\", \"China\", \"UK\"). Vendors whose origin is unknown or whose network is worldwide (a specific origin cannot be guaranteed) are excluded, each with an honest note. For \"nothing from X\" asks, pass the regions the user does want instead"
},
"vendors": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 16,
"description": "Only these specific vendors/makers (\"only show A3D Manufacturing\", \"just Slant 3D and Fictiv\") — an INCLUDE list of vendor names as they appear on offers. A CONSTRAINT like processes: other vendors39; offers drop instantly (nothing re-prices), further refines inherit the filter, and [\"any\"] clears it to show every vendor again. Friendly names accepted (\"A3D\", \"slant 3d\"); unmatched names are reported, never an error. This is THE way to answer \"show me everything vendor X offers\" — the filtered quote lists that vendor39;s complete lineup"
},
"ship_to_zip": {
"type": "string",
"pattern": "^\\d{5}(-\\d{4})?$",
"description": "Destination US ZIP code, exactly as the user stated it — use this when the user provides their ZIP after a quote priced to the assumed central-US destination (routing.ship_to); the refined prices become theirs. NEVER guess or invent a ZIP"
},
"deadline": {
"type": "string",
"description": "Latest acceptable delivery date, ISO YYYY-MM-DD"
},
"outdoor_rated": {
"type": "boolean"
},
"submersible": {
"type": "boolean"
},
"high_temp": {
"type": "boolean"
},
"food_safe": {
"type": "boolean"
},
"requirements": {
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 120
},
"maxItems": 20,
"description": "Verbatim context terms from the user — materials, finishes, certifications, tolerances (\"UV resistant\", \"anodized: red\", \"iso 13485\", \"tolerance: 0.1mm\"). UFP applies what it can and reports what it could not; unresolvable terms are logged for vendor sourcing. Do not interrogate the user to fill this — pass what they said."
},
"callouts": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "number"
},
"unit": {
"type": "string",
"enum": [
"mm",
"in"
]
},
"tolerance_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"critical": {
"type": "boolean"
}
},
"required": [
"name",
"value",
"unit"
],
"additionalProperties": false
},
"maxItems": 50,
"description": "Dimensions you read off the user39;s drawing that matter (\"hole_diameter 6.5mm ±0.1\"). The tightest tolerance prunes vendors that cannot hold it."
},
"max_budget_usd": {
"type": "number",
"exclusiveMinimum": 0
},
"min_vendor_stars": {
"type": "number",
"minimum": 1,
"maximum": 5,
"description": "Only vendors whose displayed review rating is at least this many stars (1-5); vendors with no reviews yet are excluded"
},
"min_vendor_reviews": {
"type": "integer",
"exclusiveMinimum": 0,
"description": "Only vendors with at least this many verified-purchase reviews"
},
"proven_spec_orders": {
"type": "integer",
"exclusiveMinimum": 0,
"description": "Only vendors with at least N completed orders for this exact process+material — \"a vendor that prints PC reliably\""
},
"clear": {
"type": "array",
"items": {
"type": "string",
"enum": [
"deadline",
"budget",
"outdoor_rated",
"submersible",
"high_temp",
"food_safe",
"reliability",
"requirements",
"processes",
"ships_from",
"vendors"
]
},
"minItems": 1,
"description": "REMOVE constraints entirely (\"drop the deadline\", \"forget the budget\", \"no more food-safe requirement\"): list the constraints to clear and each is removed from the quote — the one deliberate widening besides undo. Clearing a deadline or budget answers instantly from held offers (near-misses convert back); clearing an attribute/reliability/requirements demand re-prices honestly. Same effect as [\"any\"] on the three filter args, extended to every constraint"
},
"remove_requirements": {
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 120
},
"minItems": 1,
"maxItems": 20,
"description": "Take back INDIVIDUAL requirements terms (\"drop the anodized ask, keep the rest\"): each listed term is removed from the quote39;s requirements by normalized match, the others stay. Unknown terms are ignored, never an error. Re-stating the requirements list can never drop a term (terms merge as a union) — this is the removal channel"
},
"undo_last_step": {
"type": "boolean",
"description": "GO BACK EXACTLY ONE STEP (\"undo that\", \"go back\", \"put it back how it was\"): the network restores the previous quote39;s stored spec and constraints EXACTLY — never reconstructed from conversation — and re-prices where needed. Send it ALONE (no other args besides quote_id); combining it with changes is rejected. The quote39;s steps[] names what each undo would take back — steps[0] is the newest. Undo resets the baseline like any unlabeled refine, so open comparison scenarios close. Undoing the original quote is rejected with honest wording — relay it"
},
"sort_by": {
"type": "string",
"enum": [
"recommended",
"price",
"unit_price",
"total_price",
"arrival",
"rating"
],
"description": "\"Organize by\": re-order the quote39;s offer cards (\"sort by cheapest\" → \"price\"; \"soonest arrival first\" → \"arrival\"; \"best rated\" → \"rating\"; \"total_price\" = part + cheapest shipping; \"recommended\" restores the default price+speed rank). PURE PRESENTATION — answers instantly on the same quote, never re-prices or drops offers, and the ordering sticks across re-reads, streaming, and later refines until changed"
},
"sort_direction": {
"type": "string",
"enum": [
"asc",
"desc"
],
"description": "Flip a sort_by ordering: \"desc\" reverses the key39;s natural direction (\"most expensive first\" = sort_by \"price\" + \"desc\"). Only meaningful with sort_by"
},
"sort_order": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"minItems": 1,
"maxItems": 200,
"description": "EXPLICIT card order for asks only you can judge (\"sort the most green to the top\"): look at the offers39; preview images, decide the order yourself, and pass the offer ids first-on-top. Offers you leave out (including ones that stream in later) land below the listed ones in the default rank. Pass sort_label with it"
},
"sort_label": {
"type": "string",
"minLength": 1,
"maxLength": 60,
"description": "Short human wording for a sort_order, displayed on the board (\"most green first\") — required with sort_order, since only you know what your order means"
}
},
"required": [
"quote_id"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}preview_quote
34 params · 1 required
INTERNAL client rail — the routing half of refine_quote with NOTHING committed: takes the same arguments as re…
INTERNAL client rail — the routing half of refine_quote with NOTHING committed: takes the same arguments as refine_quote and answers how many distinct fabricators (and which process lanes) the network WOULD ask for the refined part, plus the exclusion notes, without creating a child quote, asking any vendor, superseding in-flight work, or logging demand. An expectation, never a promise — lanes can still decline once asked. Never call this to look at prices; it carries none. Use refine_quote to actually re-price.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| quote_id* | string | — |
| scenario | string | Comparison lane label. A labeled refine sits SIDE BY SIDE with the quote's other offers instead of replacing them: refines with the same label replace that scenario, different labels coexist (max 4 per quote), and a refine WITHOUT a scenario resets the baseline and supersedes every lane. "How does X compare to Y?" = one labeled refine per scenario (e.g. scenario "carbon steel" + material "carbon steel", then scenario "aluminum" + material "aluminum"). Keep labels short and human, like "carbon steel" minLen: 1 · maxLen: 40 |
| material | string | null | New material for this part ("I need it in PLA" → "pla"). A spec change: lanes requote with this material through warm vendor sessions; an explicit material here replaces the quote's material fan-out. Free-form — unstocked asks resolve to the closest stocked material with a substitution note. Do NOT pass material changes as requirements terms. Pass null to REMOVE a previously asked material ("forget the aluminum ask") — the ask comes off the record and the process-default material fan returns |
| color | string | null | New color for this part (spec change — lanes requote). Colour WORDS only ('black', 'green', 'clear'); the network resolves them to each maker's stocked shades, dyes, filaments or coatings — a family word ('blue') brings back EVERY stocked shade of it, and the quote's color_shades_available lists them — never pass a material or a shade you invented. Pass null to REMOVE a previously asked color — back to vendor defaults |
| color_shades | array<string> | null | Narrow the board to these color SHADES exactly as the quote lists them (color_shades_available / "Colors on this board") — instant, nothing re-prices, the same quote id comes back with only those shades; pass null to show every shade again. Never invent a shade name. |
| finish | string | null | New surface finish ("powder coat", "anodized", "bead blasted") — a spec change: finish-capable lanes (sheet metal, CNC, metal print) requote WITH it; 3D-print lanes have no coating step, so they ignore the finish but keep the COLOR. A colored finish ask ("black powder coat") should set BOTH finish and color, so every lane lands on the buyer's color. Pass null to REMOVE a previously asked finish |
| thickness_in | number | null | New sheet thickness in INCHES ("make it in 1/8" → 0.125) — a spec change: sheet lanes requote at the nearest stocked gauge, flagging the substitution when the match isn't close. Pass null to REMOVE a previously asked thickness — back to the material's default gauge |
| bends | object | array<object> | null | New bend records for this part — a spec change: sheet lanes requote with exactly these bends (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: each bend is two points in the part's own mm frame (flat DXF parts use z=0) plus angle_deg, direction up|down, and an optional requested radius_mm. Pass null to REMOVE every articulated bend |
| tapping | object | array<object> | null | New tapped-hole records for this part — a spec change: sheet lanes requote with exactly these taps (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: thread callout ("M6", "1/4-20") required, hole geometry optional. Pass null to REMOVE every tap |
| inserts | object | array<object> | null | New hardware-insert records for this part — a spec change: sheet lanes requote with exactly these inserts (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: species (nut|flush_nut|standoff|blind_standoff|stud) and thread required, hole geometry optional. Pass null to REMOVE every insert |
| quantities | array<integer> | null | New quantities the user wants (spec change — lanes requote at the new quantity). Same rules as on get_fabrication_quote: pass the real ask, never inflate it. Pass null to REMOVE a previously asked quantity — the quote returns to single-part pricing |
| scale | object | Rescale the DESIGN ITSELF before re-quoting: per-axis stretch factors over the file's current geometry ("make it 2x bigger" = {"x":2,"y":2,"z":2}). Mesh designs are genuinely converted — the child quote prices a rescaled file; STEP/IGES designs keep their original file with the dimensions riding as callouts (pass those too). {1,1,1} is a no-op |
| scale.x* | number | — min: 0.01 · max: 100 |
| scale.y* | number | — min: 0.01 · max: 100 |
| scale.z* | number | — min: 0.01 · max: 100 |
| processes | array<string> | Narrow this quote to specific fabrication processes ("no, I meant in sheet metal" → ["sheet metal"]). A CONSTRAINT, not a new quote: excluded lanes drop while warm vendor sessions survive, and further refines inherit the filter. Friendly terms accepted ("sheet metal", "3d printing", "cnc", "laser"); pass ["any"] to clear the filter and show every process again. When comparison scenarios are open and the user narrows the process, re-refine EVERY active scenario label with this same arg so all columns prune together |
| ships_from | array<string> | Only vendors that ship from these countries/regions ("only US vendors", "just European shops", "keep it domestic") — an INCLUDE list naming where the user DOES want vendors from. A CONSTRAINT like processes: non-matching vendors drop instantly (nothing re-prices), further refines inherit the filter, and ["any"] clears it to show vendors everywhere again. Friendly terms accepted ("US", "Europe", "Germany", "China", "UK"). Vendors whose origin is unknown or whose network is worldwide (a specific origin cannot be guaranteed) are excluded, each with an honest note. For "nothing from X" asks, pass the regions the user does want instead |
| vendors | array<string> | Only these specific vendors/makers ("only show A3D Manufacturing", "just Slant 3D and Fictiv") — an INCLUDE list of vendor names as they appear on offers. A CONSTRAINT like processes: other vendors' offers drop instantly (nothing re-prices), further refines inherit the filter, and ["any"] clears it to show every vendor again. Friendly names accepted ("A3D", "slant 3d"); unmatched names are reported, never an error. This is THE way to answer "show me everything vendor X offers" — the filtered quote lists that vendor's complete lineup |
| ship_to_zip | string | Destination US ZIP code, exactly as the user stated it — use this when the user provides their ZIP after a quote priced to the assumed central-US destination (routing.ship_to); the refined prices become theirs. NEVER guess or invent a ZIP pattern: ^\d{5}(-\d{4})?$ |
| deadline | string | Latest acceptable delivery date, ISO YYYY-MM-DD |
| outdoor_rated | boolean | — |
| submersible | boolean | — |
| high_temp | boolean | — |
| food_safe | boolean | — |
| requirements | array<string> | Verbatim context terms from the user — materials, finishes, certifications, tolerances ("UV resistant", "anodized: red", "iso 13485", "tolerance: 0.1mm"). UFP applies what it can and reports what it could not; unresolvable terms are logged for vendor sourcing. Do not interrogate the user to fill this — pass what they said. |
| callouts | array<object> | Dimensions you read off the user's drawing that matter ("hole_diameter 6.5mm ±0.1"). The tightest tolerance prunes vendors that cannot hold it. |
| callouts[].name* | string | — |
| callouts[].value* | number | — |
| callouts[].unit* | enum(2) | — one of: "mm", "in" |
| callouts[].tolerance_mm | number | — |
| callouts[].critical | boolean | — |
| max_budget_usd | number | — |
| min_vendor_stars | number | Only vendors whose displayed review rating is at least this many stars (1-5); vendors with no reviews yet are excluded min: 1 · max: 5 |
| min_vendor_reviews | integer | Only vendors with at least this many verified-purchase reviews |
| proven_spec_orders | integer | Only vendors with at least N completed orders for this exact process+material — "a vendor that prints PC reliably" |
| clear | array<enum(11)> | REMOVE constraints entirely ("drop the deadline", "forget the budget", "no more food-safe requirement"): list the constraints to clear and each is removed from the quote — the one deliberate widening besides undo. Clearing a deadline or budget answers instantly from held offers (near-misses convert back); clearing an attribute/reliability/requirements demand re-prices honestly. Same effect as ["any"] on the three filter args, extended to every constraint |
| remove_requirements | array<string> | Take back INDIVIDUAL requirements terms ("drop the anodized ask, keep the rest"): each listed term is removed from the quote's requirements by normalized match, the others stay. Unknown terms are ignored, never an error. Re-stating the requirements list can never drop a term (terms merge as a union) — this is the removal channel |
| undo_last_step | boolean | GO BACK EXACTLY ONE STEP ("undo that", "go back", "put it back how it was"): the network restores the previous quote's stored spec and constraints EXACTLY — never reconstructed from conversation — and re-prices where needed. Send it ALONE (no other args besides quote_id); combining it with changes is rejected. The quote's steps[] names what each undo would take back — steps[0] is the newest. Undo resets the baseline like any unlabeled refine, so open comparison scenarios close. Undoing the original quote is rejected with honest wording — relay it |
| sort_by | enum(6) | "Organize by": re-order the quote's offer cards ("sort by cheapest" → "price"; "soonest arrival first" → "arrival"; "best rated" → "rating"; "total_price" = part + cheapest shipping; "recommended" restores the default price+speed rank). PURE PRESENTATION — answers instantly on the same quote, never re-prices or drops offers, and the ordering sticks across re-reads, streaming, and later refines until changed one of: "recommended", "price", "unit_price", "total_price", "arrival", "rating" |
| sort_direction | enum(2) | Flip a sort_by ordering: "desc" reverses the key's natural direction ("most expensive first" = sort_by "price" + "desc"). Only meaningful with sort_by one of: "asc", "desc" |
| sort_order | array<string> | EXPLICIT card order for asks only you can judge ("sort the most green to the top"): look at the offers' preview images, decide the order yourself, and pass the offer ids first-on-top. Offers you leave out (including ones that stream in later) land below the listed ones in the default rank. Pass sort_label with it |
| sort_label | string | Short human wording for a sort_order, displayed on the board ("most green first") — required with sort_order, since only you know what your order means minLen: 1 · maxLen: 60 |
Raw schema JSON
{
"name": "preview_quote",
"description": "INTERNAL client rail — the routing half of refine_quote with NOTHING committed: takes the same arguments as refine_quote and answers how many distinct fabricators (and which process lanes) the network WOULD ask for the refined part, plus the exclusion notes, without creating a child quote, asking any vendor, superseding in-flight work, or logging demand. An expectation, never a promise — lanes can still decline once asked. Never call this to look at prices; it carries none. Use refine_quote to actually re-price.",
"inputSchema": {
"type": "object",
"properties": {
"quote_id": {
"type": "string"
},
"scenario": {
"type": "string",
"minLength": 1,
"maxLength": 40,
"description": "Comparison lane label. A labeled refine sits SIDE BY SIDE with the quote39;s other offers instead of replacing them: refines with the same label replace that scenario, different labels coexist (max 4 per quote), and a refine WITHOUT a scenario resets the baseline and supersedes every lane. \"How does X compare to Y?\" = one labeled refine per scenario (e.g. scenario \"carbon steel\" + material \"carbon steel\", then scenario \"aluminum\" + material \"aluminum\"). Keep labels short and human, like \"carbon steel\""
},
"material": {
"type": [
"string",
"null"
],
"description": "New material for this part (\"I need it in PLA\" → \"pla\"). A spec change: lanes requote with this material through warm vendor sessions; an explicit material here replaces the quote39;s material fan-out. Free-form — unstocked asks resolve to the closest stocked material with a substitution note. Do NOT pass material changes as requirements terms. Pass null to REMOVE a previously asked material (\"forget the aluminum ask\") — the ask comes off the record and the process-default material fan returns"
},
"color": {
"type": [
"string",
"null"
],
"description": "New color for this part (spec change — lanes requote). Colour WORDS only (39;black39;, 39;green39;, 39;clear39;); the network resolves them to each maker39;s stocked shades, dyes, filaments or coatings — a family word (39;blue39;) brings back EVERY stocked shade of it, and the quote39;s color_shades_available lists them — never pass a material or a shade you invented. Pass null to REMOVE a previously asked color — back to vendor defaults"
},
"color_shades": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 48
},
"maxItems": 64
},
{
"type": "null"
}
],
"description": "Narrow the board to these color SHADES exactly as the quote lists them (color_shades_available / \"Colors on this board\") — instant, nothing re-prices, the same quote id comes back with only those shades; pass null to show every shade again. Never invent a shade name."
},
"finish": {
"type": [
"string",
"null"
],
"description": "New surface finish (\"powder coat\", \"anodized\", \"bead blasted\") — a spec change: finish-capable lanes (sheet metal, CNC, metal print) requote WITH it; 3D-print lanes have no coating step, so they ignore the finish but keep the COLOR. A colored finish ask (\"black powder coat\") should set BOTH finish and color, so every lane lands on the buyer39;s color. Pass null to REMOVE a previously asked finish"
},
"thickness_in": {
"anyOf": [
{
"type": "number",
"exclusiveMinimum": 0,
"maximum": 1
},
{
"type": "null"
}
],
"description": "New sheet thickness in INCHES (\"make it in 1/8\" → 0.125) — a spec change: sheet lanes requote at the nearest stocked gauge, flagging the substitution when the match isn39;t close. Pass null to REMOVE a previously asked thickness — back to the material39;s default gauge"
},
"bends": {
"anyOf": [
{
"anyOf": [
{
"not": {}
},
{
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"line": {
"type": "object",
"properties": {
"p1": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"p2": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
}
},
"required": [
"p1",
"p2"
],
"additionalProperties": false
},
"angle_deg": {
"type": "number",
"exclusiveMinimum": 0,
"exclusiveMaximum": 180
},
"direction": {
"type": "string",
"enum": [
"up",
"down"
]
},
"radius_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"face_id": {
"type": "integer"
},
"source": {
"type": "string",
"enum": [
"detected",
"user"
]
}
},
"required": [
"line",
"angle_deg",
"direction"
],
"additionalProperties": false
},
"maxItems": 50
}
],
"description": "Sheet-metal bend lines, each as TWO POINTS in the part39;s own mm frame (flat DXF parts use z=0: a bend from (0,12.7) to (76.2,12.7) is p1 [0,12.7,0], p2 [76.2,12.7,0]). angle_deg is the target bend angle (90 = a right-angle flange), direction \"up\"/\"down\" is the fold direction relative to the flat pattern, radius_mm the requested inside radius (omit it — the shop resolves to its tooling and reports what it used). Pass these when the user articulates WHERE the bends go; a bare \"it has 2 bends\" is bend_count, not this."
},
{
"type": "null"
}
],
"description": "New bend records for this part — a spec change: sheet lanes requote with exactly these bends (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: each bend is two points in the part39;s own mm frame (flat DXF parts use z=0) plus angle_deg, direction up|down, and an optional requested radius_mm. Pass null to REMOVE every articulated bend"
},
"tapping": {
"anyOf": [
{
"anyOf": [
{
"not": {}
},
{
"type": "array",
"items": {
"type": "object",
"properties": {
"hole": {
"type": "integer",
"minimum": 1
},
"thread": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"face_id": {
"type": "integer"
},
"drilled_diameter_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"located_at_mm": {
"type": "object",
"properties": {
"x": {
"type": "number"
},
"y": {
"type": "number"
},
"z": {
"type": "number"
}
},
"required": [
"x",
"y",
"z"
],
"additionalProperties": false
},
"axis": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"depth_mm": {
"type": "number",
"exclusiveMinimum": 0
}
},
"required": [
"thread"
],
"additionalProperties": false
},
"maxItems": 200
}
],
"description": "Tapped (threaded) holes for a sheet-metal part — one record per hole the user wants threads cut into. `thread` is the callout in the user39;s words (\"M6\", \"M4 x 0.7\", \"1/4-20\") and is all that39;s required; when known, add the hole39;s center in the part39;s own mm frame (located_at_mm), its unit axis, the pre-tap drilled diameter, and depth_mm so the shop taps the right hole. Pass these when the user asks for threaded/tapped holes; vendors with a tapping service price them."
},
{
"type": "null"
}
],
"description": "New tapped-hole records for this part — a spec change: sheet lanes requote with exactly these taps (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: thread callout (\"M6\", \"1/4-20\") required, hole geometry optional. Pass null to REMOVE every tap"
},
"inserts": {
"anyOf": [
{
"anyOf": [
{
"not": {}
},
{
"type": "array",
"items": {
"type": "object",
"properties": {
"hole": {
"type": "integer",
"minimum": 1
},
"insert": {
"type": "string",
"enum": [
"nut",
"flush_nut",
"standoff",
"blind_standoff",
"stud"
]
},
"thread": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"face_id": {
"type": "integer"
},
"points": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"length_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"drilled_diameter_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"located_at_mm": {
"type": "object",
"properties": {
"x": {
"type": "number"
},
"y": {
"type": "number"
},
"z": {
"type": "number"
}
},
"required": [
"x",
"y",
"z"
],
"additionalProperties": false
},
"axis": {
"type": "array",
"minItems": 3,
"maxItems": 3,
"items": [
{
"type": "number"
},
{
"type": "number"
},
{
"type": "number"
}
]
},
"depth_mm": {
"type": "number",
"exclusiveMinimum": 0
}
},
"required": [
"insert",
"thread"
],
"additionalProperties": false
},
"maxItems": 200
}
],
"description": "PEM-style hardware inserts pressed into holes of a sheet-metal part — one record per hole. `insert` is the species (nut | flush_nut | standoff | blind_standoff | stud) and `thread` its size (\"M4\", \"1/4-20\"); both are required. When known, add length_mm (standoff/stud post length), the hole39;s center (located_at_mm, part39;s own mm frame), its axis, the drilled diameter, and `points` — the signed unit vector the insert39;s functional side faces (flip = negate). Pass these when the user asks for press-in nuts/standoffs/studs; vendors with a hardware service price them."
},
{
"type": "null"
}
],
"description": "New hardware-insert records for this part — a spec change: sheet lanes requote with exactly these inserts (the list REPLACES the previous one, never patches it). Same shape as on get_fabrication_quote: species (nut|flush_nut|standoff|blind_standoff|stud) and thread required, hole geometry optional. Pass null to REMOVE every insert"
},
"quantities": {
"anyOf": [
{
"type": "array",
"items": {
"type": "integer",
"exclusiveMinimum": 0
},
"maxItems": 5
},
{
"type": "null"
}
],
"description": "New quantities the user wants (spec change — lanes requote at the new quantity). Same rules as on get_fabrication_quote: pass the real ask, never inflate it. Pass null to REMOVE a previously asked quantity — the quote returns to single-part pricing"
},
"scale": {
"type": "object",
"properties": {
"x": {
"type": "number",
"minimum": 0.01,
"maximum": 100
},
"y": {
"type": "number",
"minimum": 0.01,
"maximum": 100
},
"z": {
"type": "number",
"minimum": 0.01,
"maximum": 100
}
},
"required": [
"x",
"y",
"z"
],
"additionalProperties": false,
"description": "Rescale the DESIGN ITSELF before re-quoting: per-axis stretch factors over the file39;s current geometry (\"make it 2x bigger\" = {\"x\":2,\"y\":2,\"z\":2}). Mesh designs are genuinely converted — the child quote prices a rescaled file; STEP/IGES designs keep their original file with the dimensions riding as callouts (pass those too). {1,1,1} is a no-op"
},
"processes": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 8,
"description": "Narrow this quote to specific fabrication processes (\"no, I meant in sheet metal\" → [\"sheet metal\"]). A CONSTRAINT, not a new quote: excluded lanes drop while warm vendor sessions survive, and further refines inherit the filter. Friendly terms accepted (\"sheet metal\", \"3d printing\", \"cnc\", \"laser\"); pass [\"any\"] to clear the filter and show every process again. When comparison scenarios are open and the user narrows the process, re-refine EVERY active scenario label with this same arg so all columns prune together"
},
"ships_from": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 8,
"description": "Only vendors that ship from these countries/regions (\"only US vendors\", \"just European shops\", \"keep it domestic\") — an INCLUDE list naming where the user DOES want vendors from. A CONSTRAINT like processes: non-matching vendors drop instantly (nothing re-prices), further refines inherit the filter, and [\"any\"] clears it to show vendors everywhere again. Friendly terms accepted (\"US\", \"Europe\", \"Germany\", \"China\", \"UK\"). Vendors whose origin is unknown or whose network is worldwide (a specific origin cannot be guaranteed) are excluded, each with an honest note. For \"nothing from X\" asks, pass the regions the user does want instead"
},
"vendors": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 16,
"description": "Only these specific vendors/makers (\"only show A3D Manufacturing\", \"just Slant 3D and Fictiv\") — an INCLUDE list of vendor names as they appear on offers. A CONSTRAINT like processes: other vendors39; offers drop instantly (nothing re-prices), further refines inherit the filter, and [\"any\"] clears it to show every vendor again. Friendly names accepted (\"A3D\", \"slant 3d\"); unmatched names are reported, never an error. This is THE way to answer \"show me everything vendor X offers\" — the filtered quote lists that vendor39;s complete lineup"
},
"ship_to_zip": {
"type": "string",
"pattern": "^\\d{5}(-\\d{4})?$",
"description": "Destination US ZIP code, exactly as the user stated it — use this when the user provides their ZIP after a quote priced to the assumed central-US destination (routing.ship_to); the refined prices become theirs. NEVER guess or invent a ZIP"
},
"deadline": {
"type": "string",
"description": "Latest acceptable delivery date, ISO YYYY-MM-DD"
},
"outdoor_rated": {
"type": "boolean"
},
"submersible": {
"type": "boolean"
},
"high_temp": {
"type": "boolean"
},
"food_safe": {
"type": "boolean"
},
"requirements": {
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 120
},
"maxItems": 20,
"description": "Verbatim context terms from the user — materials, finishes, certifications, tolerances (\"UV resistant\", \"anodized: red\", \"iso 13485\", \"tolerance: 0.1mm\"). UFP applies what it can and reports what it could not; unresolvable terms are logged for vendor sourcing. Do not interrogate the user to fill this — pass what they said."
},
"callouts": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "number"
},
"unit": {
"type": "string",
"enum": [
"mm",
"in"
]
},
"tolerance_mm": {
"type": "number",
"exclusiveMinimum": 0
},
"critical": {
"type": "boolean"
}
},
"required": [
"name",
"value",
"unit"
],
"additionalProperties": false
},
"maxItems": 50,
"description": "Dimensions you read off the user39;s drawing that matter (\"hole_diameter 6.5mm ±0.1\"). The tightest tolerance prunes vendors that cannot hold it."
},
"max_budget_usd": {
"type": "number",
"exclusiveMinimum": 0
},
"min_vendor_stars": {
"type": "number",
"minimum": 1,
"maximum": 5,
"description": "Only vendors whose displayed review rating is at least this many stars (1-5); vendors with no reviews yet are excluded"
},
"min_vendor_reviews": {
"type": "integer",
"exclusiveMinimum": 0,
"description": "Only vendors with at least this many verified-purchase reviews"
},
"proven_spec_orders": {
"type": "integer",
"exclusiveMinimum": 0,
"description": "Only vendors with at least N completed orders for this exact process+material — \"a vendor that prints PC reliably\""
},
"clear": {
"type": "array",
"items": {
"type": "string",
"enum": [
"deadline",
"budget",
"outdoor_rated",
"submersible",
"high_temp",
"food_safe",
"reliability",
"requirements",
"processes",
"ships_from",
"vendors"
]
},
"minItems": 1,
"description": "REMOVE constraints entirely (\"drop the deadline\", \"forget the budget\", \"no more food-safe requirement\"): list the constraints to clear and each is removed from the quote — the one deliberate widening besides undo. Clearing a deadline or budget answers instantly from held offers (near-misses convert back); clearing an attribute/reliability/requirements demand re-prices honestly. Same effect as [\"any\"] on the three filter args, extended to every constraint"
},
"remove_requirements": {
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 120
},
"minItems": 1,
"maxItems": 20,
"description": "Take back INDIVIDUAL requirements terms (\"drop the anodized ask, keep the rest\"): each listed term is removed from the quote39;s requirements by normalized match, the others stay. Unknown terms are ignored, never an error. Re-stating the requirements list can never drop a term (terms merge as a union) — this is the removal channel"
},
"undo_last_step": {
"type": "boolean",
"description": "GO BACK EXACTLY ONE STEP (\"undo that\", \"go back\", \"put it back how it was\"): the network restores the previous quote39;s stored spec and constraints EXACTLY — never reconstructed from conversation — and re-prices where needed. Send it ALONE (no other args besides quote_id); combining it with changes is rejected. The quote39;s steps[] names what each undo would take back — steps[0] is the newest. Undo resets the baseline like any unlabeled refine, so open comparison scenarios close. Undoing the original quote is rejected with honest wording — relay it"
},
"sort_by": {
"type": "string",
"enum": [
"recommended",
"price",
"unit_price",
"total_price",
"arrival",
"rating"
],
"description": "\"Organize by\": re-order the quote39;s offer cards (\"sort by cheapest\" → \"price\"; \"soonest arrival first\" → \"arrival\"; \"best rated\" → \"rating\"; \"total_price\" = part + cheapest shipping; \"recommended\" restores the default price+speed rank). PURE PRESENTATION — answers instantly on the same quote, never re-prices or drops offers, and the ordering sticks across re-reads, streaming, and later refines until changed"
},
"sort_direction": {
"type": "string",
"enum": [
"asc",
"desc"
],
"description": "Flip a sort_by ordering: \"desc\" reverses the key39;s natural direction (\"most expensive first\" = sort_by \"price\" + \"desc\"). Only meaningful with sort_by"
},
"sort_order": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"minItems": 1,
"maxItems": 200,
"description": "EXPLICIT card order for asks only you can judge (\"sort the most green to the top\"): look at the offers39; preview images, decide the order yourself, and pass the offer ids first-on-top. Offers you leave out (including ones that stream in later) land below the listed ones in the default rank. Pass sort_label with it"
},
"sort_label": {
"type": "string",
"minLength": 1,
"maxLength": 60,
"description": "Short human wording for a sort_order, displayed on the board (\"most green first\") — required with sort_order, since only you know what your order means"
}
},
"required": [
"quote_id"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}poll_quote
1 param · 1 required
INTERNAL — the offer board calls this to refresh itself while vendors finish pricing. Never call this yourself…
INTERNAL — the offer board calls this to refresh itself while vendors finish pricing. Never call this yourself. The board you were given is already final for its turn; do not reach for refine_quote to look at it again either, that paints a duplicate board.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| quote_id* | string | Quote id the board is watching |
Raw schema JSON
{
"name": "poll_quote",
"description": "INTERNAL — the offer board calls this to refresh itself while vendors finish pricing. Never call this yourself. The board you were given is already final for its turn; do not reach for refine_quote to look at it again either, that paints a duplicate board.",
"inputSchema": {
"type": "object",
"properties": {
"quote_id": {
"type": "string",
"description": "Quote id the board is watching"
}
},
"required": [
"quote_id"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}finalize_quote
1 param · 1 required
ONLY for the case where a quote response came back with an EMPTY board and told you to call this: waits for th…
ONLY for the case where a quote response came back with an EMPTY board and told you to call this: waits for the vendors to answer (up to ~40s) and returns their offers as a full board. Call with just quote_id, immediately, and say nothing substantive before it. NEVER call it on a response that already listed offers — that board is final, and this would add nothing.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| quote_id* | string | Quote id from the still-quoting response |
Raw schema JSON
{
"name": "finalize_quote",
"description": "ONLY for the case where a quote response came back with an EMPTY board and told you to call this: waits for the vendors to answer (up to ~40s) and returns their offers as a full board. Call with just quote_id, immediately, and say nothing substantive before it. NEVER call it on a response that already listed offers — that board is final, and this would add nothing.",
"inputSchema": {
"type": "object",
"properties": {
"quote_id": {
"type": "string",
"description": "Quote id from the still-quoting response"
}
},
"required": [
"quote_id"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}create_checkout
18 params · 2 required
Create the order and get a hosted payment link for a chosen offer. Call this as soon as the user picks an offe…
Create the order and get a hosted payment link for a chosen offer. Call this as soon as the user picks an offer + shipping speed — do NOT ask for their address first: the secure payment page collects the shipping address and email. Only pass address fields if the user already volunteered them. Returns checkout_url — give it to the user to pay; UFP places the vendor order automatically after payment.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| offer_id* | string | — |
| shipping_option_id* | string | One of the offer's shipping option ids |
| name | string | Recipient full name (only if the user provided it) |
| street1 | string | Street address (only if the user provided it) |
| street2 | string | — |
| city | string | — |
| state | string | Two-letter US state minLen: 2 · maxLen: 2 |
| zip | string | — |
| string | Buyer email (only if the user provided it) format: email |
|
| phone | string | — |
| billing_name | string | Billing address, only when the buyer answered the billing question (e.g. said it differs from shipping, or a checkout UI's 'same as shipping' checkbox — then send the shipping values verbatim). Never ask for it; omit and the payment page handles billing. |
| billing_street1 | string | — |
| billing_street2 | string | — |
| billing_city | string | — |
| billing_state | string | Two-letter US state minLen: 2 · maxLen: 2 |
| billing_zip | string | — |
| return_url | string | Exact URL of the page the user is on right now, IF the client application knows it (a web app embedding this tool passes its own page URL). The post-payment page shows a 'Return to <site>' button pointing here. Omit when unknown — never invent one. format: uri |
| coupon_code | string | Coupon code, only if the user provided one (early-adopter codes from the AFN team). Case-insensitive. The discount appears on the payment page; a 100%-off code makes the total $0 with no card required. Never invent or guess a code. |
Raw schema JSON
{
"name": "create_checkout",
"description": "Create the order and get a hosted payment link for a chosen offer. Call this as soon as the user picks an offer + shipping speed — do NOT ask for their address first: the secure payment page collects the shipping address and email. Only pass address fields if the user already volunteered them. Returns checkout_url — give it to the user to pay; UFP places the vendor order automatically after payment.",
"inputSchema": {
"type": "object",
"properties": {
"offer_id": {
"type": "string"
},
"shipping_option_id": {
"type": "string",
"description": "One of the offer39;s shipping option ids"
},
"name": {
"type": "string",
"description": "Recipient full name (only if the user provided it)"
},
"street1": {
"type": "string",
"description": "Street address (only if the user provided it)"
},
"street2": {
"type": "string"
},
"city": {
"type": "string"
},
"state": {
"type": "string",
"minLength": 2,
"maxLength": 2,
"description": "Two-letter US state"
},
"zip": {
"type": "string"
},
"email": {
"type": "string",
"format": "email",
"description": "Buyer email (only if the user provided it)"
},
"phone": {
"type": "string"
},
"billing_name": {
"type": "string",
"description": "Billing address, only when the buyer answered the billing question (e.g. said it differs from shipping, or a checkout UI39;s 39;same as shipping39; checkbox — then send the shipping values verbatim). Never ask for it; omit and the payment page handles billing."
},
"billing_street1": {
"type": "string"
},
"billing_street2": {
"type": "string"
},
"billing_city": {
"type": "string"
},
"billing_state": {
"type": "string",
"minLength": 2,
"maxLength": 2,
"description": "Two-letter US state"
},
"billing_zip": {
"type": "string"
},
"return_url": {
"type": "string",
"format": "uri",
"description": "Exact URL of the page the user is on right now, IF the client application knows it (a web app embedding this tool passes its own page URL). The post-payment page shows a 39;Return to <site>39; button pointing here. Omit when unknown — never invent one."
},
"coupon_code": {
"type": "string",
"description": "Coupon code, only if the user provided one (early-adopter codes from the AFN team). Case-insensitive. The discount appears on the payment page; a 100%-off code makes the total $0 with no card required. Never invent or guess a code."
}
},
"required": [
"offer_id",
"shipping_option_id"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}get_order_status
1 param · 1 required
Check status, ETA and tracking for a UFP order.
Check status, ETA and tracking for a UFP order.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| order_id* | string | — |
Raw schema JSON
{
"name": "get_order_status",
"description": "Check status, ETA and tracking for a UFP order.",
"inputSchema": {
"type": "object",
"properties": {
"order_id": {
"type": "string"
}
},
"required": [
"order_id"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}list_orders
0 params
List this agent's recent UFP orders (newest first): order id, what was made, vendor, status, total, ETA, creat…
List this agent's recent UFP orders (newest first): order id, what was made, vendor, status, total, ETA, created date. Use it to resolve vague references — "my sticker order", "that order from 6 days ago" — to a concrete order_id before calling get_order_status or leave_review.
Input schema
No parameters.
Raw schema JSON
{
"name": "list_orders",
"description": "List this agent39;s recent UFP orders (newest first): order id, what was made, vendor, status, total, ETA, created date. Use it to resolve vague references — \"my sticker order\", \"that order from 6 days ago\" — to a concrete order_id before calling get_order_status or leave_review.",
"inputSchema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {}
}
}reply_to_maker
2 params · 2 required
Send the user's answer to a question the maker (vendor) asked about a UFP order — get_order_status surfaces an…
Send the user's answer to a question the maker (vendor) asked about a UFP order — get_order_status surfaces an open question when one is waiting. Confirm the answer with the user before sending. The network relays it: the maker sees plain text from the network account with the user's contact details and links stripped, so never include emails, phone numbers, or URLs the answer depends on.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| order_id* | string | The UFP order the maker asked about (ord_…) |
| message* | string | The user's answer, in their words — it is relayed to the maker minLen: 1 · maxLen: 4000 |
Raw schema JSON
{
"name": "reply_to_maker",
"description": "Send the user39;s answer to a question the maker (vendor) asked about a UFP order — get_order_status surfaces an open question when one is waiting. Confirm the answer with the user before sending. The network relays it: the maker sees plain text from the network account with the user39;s contact details and links stripped, so never include emails, phone numbers, or URLs the answer depends on.",
"inputSchema": {
"type": "object",
"properties": {
"order_id": {
"type": "string",
"description": "The UFP order the maker asked about (ord_…)"
},
"message": {
"type": "string",
"minLength": 1,
"maxLength": 4000,
"description": "The user39;s answer, in their words — it is relayed to the maker"
}
},
"required": [
"order_id",
"message"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}leave_review
5 params · 2 required
Record the user's verified-purchase review of how a UFP order turned out. YOUR JOB IS TO STRUCTURE THE FEEDBAC…
Record the user's verified-purchase review of how a UFP order turned out. YOUR JOB IS TO STRUCTURE THE FEEDBACK: turn what the user actually said into stars (1-5 overall) and facet scores — "the cut was sloppy" -> quality, "parts arrived 2 days late" -> timeliness, "wrong color" -> accuracy. Keep the optional comment to a short factual summary of their words; never embellish. ALWAYS draft the review (stars, facets, comment) and confirm it with the user BEFORE calling this tool — e.g. "I'll rate this 2 stars with timeliness 1 because it arrived 2 days late — send it?". One review per order: submitting again updates the existing review. Use list_orders first if you need to resolve which order they mean.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| order_id* | string | The UFP order being reviewed (ord_…) — see list_orders |
| stars* | integer | Overall rating the user confirmed, 1-5 min: 1 · max: 5 |
| comment | string | Short factual summary of the user's feedback, in their spirit — optional maxLen: 2000 |
| facets | object | Score only the facets the user actually spoke to |
| facets.quality | integer | Build/print/cut quality min: 1 · max: 5 |
| facets.timeliness | integer | Delivery speed vs the quoted ETA min: 1 · max: 5 |
| facets.accuracy | integer | How well the item matched the ordered spec/design min: 1 · max: 5 |
| claims | object | CHECKABLE claims from the user's feedback — the network stamps each against its own records (the ordered spec, polled tracking + delivery events) and attaches evidence chips to the review. Only pass what the user actually asserted. |
| claims.received_material | string | Material the user says actually ARRIVED, when they complain it differs from the order ("they sent aluminum") maxLen: 80 |
| claims.received_quantity | integer | Count the user says actually arrived, when it differs from the order |
| claims.delivery_claim | enum(3) | The user's delivery claim ("never showed up" -> not_delivered) one of: "not_delivered", "late", "on_time" |
Raw schema JSON
{
"name": "leave_review",
"description": "Record the user39;s verified-purchase review of how a UFP order turned out. YOUR JOB IS TO STRUCTURE THE FEEDBACK: turn what the user actually said into stars (1-5 overall) and facet scores — \"the cut was sloppy\" -> quality, \"parts arrived 2 days late\" -> timeliness, \"wrong color\" -> accuracy. Keep the optional comment to a short factual summary of their words; never embellish. ALWAYS draft the review (stars, facets, comment) and confirm it with the user BEFORE calling this tool — e.g. \"I39;ll rate this 2 stars with timeliness 1 because it arrived 2 days late — send it?\". One review per order: submitting again updates the existing review. Use list_orders first if you need to resolve which order they mean.",
"inputSchema": {
"type": "object",
"properties": {
"order_id": {
"type": "string",
"description": "The UFP order being reviewed (ord_…) — see list_orders"
},
"stars": {
"type": "integer",
"minimum": 1,
"maximum": 5,
"description": "Overall rating the user confirmed, 1-5"
},
"comment": {
"type": "string",
"maxLength": 2000,
"description": "Short factual summary of the user39;s feedback, in their spirit — optional"
},
"facets": {
"type": "object",
"properties": {
"quality": {
"type": "integer",
"minimum": 1,
"maximum": 5,
"description": "Build/print/cut quality"
},
"timeliness": {
"type": "integer",
"minimum": 1,
"maximum": 5,
"description": "Delivery speed vs the quoted ETA"
},
"accuracy": {
"type": "integer",
"minimum": 1,
"maximum": 5,
"description": "How well the item matched the ordered spec/design"
}
},
"additionalProperties": false,
"description": "Score only the facets the user actually spoke to"
},
"claims": {
"type": "object",
"properties": {
"received_material": {
"type": "string",
"maxLength": 80,
"description": "Material the user says actually ARRIVED, when they complain it differs from the order (\"they sent aluminum\")"
},
"received_quantity": {
"type": "integer",
"exclusiveMinimum": 0,
"description": "Count the user says actually arrived, when it differs from the order"
},
"delivery_claim": {
"type": "string",
"enum": [
"not_delivered",
"late",
"on_time"
],
"description": "The user39;s delivery claim (\"never showed up\" -> not_delivered)"
}
},
"additionalProperties": false,
"description": "CHECKABLE claims from the user39;s feedback — the network stamps each against its own records (the ordered spec, polled tracking + delivery events) and attaches evidence chips to the review. Only pass what the user actually asserted."
}
},
"required": [
"order_id",
"stars"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}get_material_guide
3 params
Honest, cited material intelligence for material-choice / strength / durability / heat / outdoor questions ("m…
Honest, cited material intelligence for material-choice / strength / durability / heat / outdoor questions ("my PLA part broke, what's stronger?", "will this survive outdoors?"). Returns caveats-FIRST facts: published specs (tensile, heat-deflection, UV/outdoor, chemical) each tagged vendor-cited vs general engineering knowledge, "stronger/tougher/hotter than X" ladders (PLA→PETG→ABS/ASA→nylon/PC→metals), and finish/coating options. Call it BEFORE answering such a question, then relay the facts. It supplies FACTS ONLY — comparative specs and vendor-admitted caveats, never a fitness-for-purpose or safety guarantee (that stays your judgment boundary); name express vendor claims "advertised", not "certified".
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| material | string | A material the user named or you are weighing ("PLA", "6061 aluminum", "stainless") — free-form; a family ask like "stainless" returns the whole family |
| process | string | A UFP process to scope to ("fdm_print", "resin_print", "cnc", "sheetmetal", "laser_cut") — lists the materials that process makes |
| question | string | The user's raw question — mined for intent (stronger/tougher, heat/hot, outdoor/UV) so the right ladder is surfaced |
Raw schema JSON
{
"name": "get_material_guide",
"description": "Honest, cited material intelligence for material-choice / strength / durability / heat / outdoor questions (\"my PLA part broke, what39;s stronger?\", \"will this survive outdoors?\"). Returns caveats-FIRST facts: published specs (tensile, heat-deflection, UV/outdoor, chemical) each tagged vendor-cited vs general engineering knowledge, \"stronger/tougher/hotter than X\" ladders (PLA→PETG→ABS/ASA→nylon/PC→metals), and finish/coating options. Call it BEFORE answering such a question, then relay the facts. It supplies FACTS ONLY — comparative specs and vendor-admitted caveats, never a fitness-for-purpose or safety guarantee (that stays your judgment boundary); name express vendor claims \"advertised\", not \"certified\".",
"inputSchema": {
"type": "object",
"properties": {
"material": {
"type": "string",
"description": "A material the user named or you are weighing (\"PLA\", \"6061 aluminum\", \"stainless\") — free-form; a family ask like \"stainless\" returns the whole family"
},
"process": {
"type": "string",
"description": "A UFP process to scope to (\"fdm_print\", \"resin_print\", \"cnc\", \"sheetmetal\", \"laser_cut\") — lists the materials that process makes"
},
"question": {
"type": "string",
"description": "The user39;s raw question — mined for intent (stronger/tougher, heat/hot, outdoor/UV) so the right ladder is surfaced"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}get_network_capabilities
1 param
The LIVE catalog of what the fabrication network can do RIGHT NOW — no quote needed. Returns the services ledg…
The LIVE catalog of what the fabrication network can do RIGHT NOW — no quote needed. Returns the services ledger (tapping, inserts, welding, bending, finishes… with each shop's own size/material/thickness windows), the network's sheet gauge ladder, the stocked hardware combinations (species x thread) with stocked lengths and shop counts — the most-stocked length is the steering default for an unspecified length — the finish options with their stocked color menus, and per-process manufacturability rules. This is live state, not a spec sheet: it changes as connectors join, leave, or have capability branches toggled, so call it fresh when the user asks what's possible (materials, gauges, hardware, colors, services) rather than answering from memory.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| process | string | Advisory scope ("sheetmetal") — v1 returns the whole catalog either way; filter what you relay |
Raw schema JSON
{
"name": "get_network_capabilities",
"description": "The LIVE catalog of what the fabrication network can do RIGHT NOW — no quote needed. Returns the services ledger (tapping, inserts, welding, bending, finishes… with each shop39;s own size/material/thickness windows), the network39;s sheet gauge ladder, the stocked hardware combinations (species x thread) with stocked lengths and shop counts — the most-stocked length is the steering default for an unspecified length — the finish options with their stocked color menus, and per-process manufacturability rules. This is live state, not a spec sheet: it changes as connectors join, leave, or have capability branches toggled, so call it fresh when the user asks what39;s possible (materials, gauges, hardware, colors, services) rather than answering from memory.",
"inputSchema": {
"type": "object",
"properties": {
"process": {
"type": "string",
"description": "Advisory scope (\"sheetmetal\") — v1 returns the whole catalog either way; filter what you relay"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}get_shop_gauges
2 params · 1 required
Every sheet thickness (gauge) ONE named shop stocks right now, per material — read live off the shop's declare…
Every sheet thickness (gauge) ONE named shop stocks right now, per material — read live off the shop's declared catalog, no quote needed. Call it when the user asks what thicknesses/gauges a specific maker carries ("what thicknesses does SendCutSend have in mild steel?"). For the whole network's ladder use get_network_capabilities instead. Never answer a gauge question from memory.
Input schema
| Parameter | Type | Description & constraints |
|---|---|---|
| shop* | string | The shop as the user or the offer cards name it ("SendCutSend", "sendcutsend") minLen: 1 |
| material | string | Advisory: narrow the relayed list to one material ("mild steel", "5052") |
Raw schema JSON
{
"name": "get_shop_gauges",
"description": "Every sheet thickness (gauge) ONE named shop stocks right now, per material — read live off the shop39;s declared catalog, no quote needed. Call it when the user asks what thicknesses/gauges a specific maker carries (\"what thicknesses does SendCutSend have in mild steel?\"). For the whole network39;s ladder use get_network_capabilities instead. Never answer a gauge question from memory.",
"inputSchema": {
"type": "object",
"properties": {
"shop": {
"type": "string",
"minLength": 1,
"description": "The shop as the user or the offer cards name it (\"SendCutSend\", \"sendcutsend\")"
},
"material": {
"type": "string",
"description": "Advisory: narrow the relayed list to one material (\"mild steel\", \"5052\")"
}
},
"required": [
"shop"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}Resources 2
| URI | Name | MIME type | Description |
|---|---|---|---|
| ui://widget/quote-compare-v40.html | quote-compare-widget | text/html;profile=mcp-app |
UFP offer comparison board |
| ufp://materials/guide.md | materials-intelligence | text/markdown |
UFP materials-intelligence pack — honest, cited material facts (caveats first), stronger/hotter/outdoor ladders, and a finishes/inspection glossary |
Prompts 0
No prompts advertised.
Inventory recorded Sep 9, 2026 — 3:40 PM as rev 11. Listing calls only — tools are never invoked.
Canonical contract hash
sha256:60af81a125ec677e23b14a6ec9a6f1ac4be509f3b26938755194ebb00762474c
Computed centrally from the normalized capability inventory (normalizer v1). Scanners submit raw observations; the control plane normalizes and hashes, so every scanner agrees on the same value.
Revisions 11
| Rev | Observed | Hash |
|---|---|---|
| rev 11 | Sep 9, 2026 — 3:40 PM (8 d ago) | |
| rev 10 | Sep 6, 2026 — 12:40 PM (11 d ago) | |
| rev 9 | Sep 3, 2026 — 5:40 AM (15 d ago) | |
| rev 8 | Aug 31, 2026 — 5:15 AM (18 d ago) | |
| rev 7 | Aug 25, 2026 — 5:30 AM (24 d ago) | |
| rev 6 | Aug 19, 2026 — 6:00 AM (30 d ago) | |
| rev 5 | Aug 18, 2026 — 7:10 AM (31 d ago) | |
| rev 4 | Aug 9, 2026 — 9:10 PM (39 d ago) | |
| rev 3 | Aug 9, 2026 — 8:40 AM (39 d ago) | |
| rev 2 | Aug 8, 2026 — 5:35 AM (41 d ago) | |
| rev 1 baseline | Aug 6, 2026 — 5:25 AM (43 d ago) |
Contract changes 10
get_shop_gauges was added.
rev 10 → 11 · 8 d ago
color_shades was added at preview_quote.inputSchema.
rev 9 → 10 · 11 d ago
anyOf) at refine_quote.inputSchema.bends changed.
rev 8 → 9 · 15 d ago
refine_quote.inputSchema.color changed from string to string,null.
rev 7 → 8 · 18 d ago
coupon_code was added at create_checkout.inputSchema.
rev 6 → 7 · 24 d ago
clear was added at refine_quote.inputSchema.
rev 5 → 6 · 30 d ago
ui://widget/quote-compare-v39.html is no longer advertised.
rev 4 → 5 · 31 d ago
ui://widget/quote-compare-v36.html is no longer advertised.
rev 3 → 4 · 39 d ago
powder_finish was added at get_fabrication_quote.inputSchema.
rev 2 → 3 · 39 d ago
ui://widget/quote-compare-v5.html is no longer advertised.
rev 1 → 2 · 41 d ago
Full snapshots are stored only when the canonical hash changes — unchanged observations update freshness without duplicating the contract.
Recent observations latest 30
| Observed | Result | Latency |
|---|---|---|
| Sep 17, 2026 — 7:10 PM (1 h ago) | Reachable | 247 ms |
| Sep 17, 2026 — 5:05 PM (3 h ago) | Reachable | 284 ms |
| Sep 17, 2026 — 3:00 PM (5 h ago) | Reachable | 133 ms |
| Sep 17, 2026 — 12:55 PM (7 h ago) | Reachable | 216 ms |
| Sep 17, 2026 — 10:50 AM (9 h ago) | Reachable | 208 ms |
| Sep 17, 2026 — 8:50 AM (11 h ago) | Reachable | 230 ms |
| Sep 17, 2026 — 6:45 AM (13 h ago) | Reachable | 160 ms |
| Sep 17, 2026 — 4:40 AM (16 h ago) | Reachable | 233 ms |
| Sep 17, 2026 — 2:35 AM (18 h ago) | Reachable | 305 ms |
| Sep 17, 2026 — 12:30 AM (20 h ago) | Reachable | 174 ms |
| Sep 16, 2026 — 10:25 PM (22 h ago) | Reachable | 198 ms |
| Sep 16, 2026 — 8:20 PM (24 h ago) | Reachable | 263 ms |
| Sep 16, 2026 — 6:20 PM (1 d ago) | Reachable | 283 ms |
| Sep 16, 2026 — 4:15 PM (1 d ago) | Reachable | 195 ms |
| Sep 16, 2026 — 2:15 PM (1 d ago) | Reachable | 247 ms |
| Sep 16, 2026 — 12:15 PM (1 d ago) | Reachable | 461 ms |
| Sep 16, 2026 — 10:10 AM (1 d ago) | Reachable | 148 ms |
| Sep 16, 2026 — 8:10 AM (2 d ago) | Reachable | 165 ms |
| Sep 16, 2026 — 6:05 AM (2 d ago) | Reachable | 224 ms |
| Sep 16, 2026 — 4:00 AM (2 d ago) | Reachable | 158 ms |
| Sep 16, 2026 — 2:00 AM (2 d ago) | Reachable | 175 ms |
| Sep 15, 2026 — 11:55 PM (2 d ago) | Reachable | 145 ms |
| Sep 15, 2026 — 9:50 PM (2 d ago) | Reachable | 236 ms |
| Sep 15, 2026 — 7:45 PM (2 d ago) | Reachable | 302 ms |
| Sep 15, 2026 — 5:40 PM (2 d ago) | Reachable | 214 ms |
| Sep 15, 2026 — 3:35 PM (2 d ago) | Reachable | 427 ms |
| Sep 15, 2026 — 1:35 PM (2 d ago) | Reachable | 253 ms |
| Sep 15, 2026 — 11:30 AM (2 d ago) | Reachable | 294 ms |
| Sep 15, 2026 — 9:25 AM (2 d ago) | Reachable | 229 ms |
| Sep 15, 2026 — 7:25 AM (3 d ago) | Reachable | 110 ms |
Latest check — evidence & validation Sep 17, 2026 — 7:10 PM
{
"server": "cloudflare",
"content-type": "application/json"
}{
"name": "ufp",
"version": "0.1.0",
"title": null
}Publisher supplied
unverified| Name | Agent Fabrication Network (UFP) MCP |
| Vendor | Agentic Fabrication Network |
| Category | other |
| Docs | — |
| Repository | — |
| Auth expected | Auth expectations unknown |
Registry and publisher metadata from the deployment seed. Displayed as supplied — MCP Tools does not verify it.
Independently observed
verified| Server name | ufp |
| Server version | 0.1.0 |
| Transport | Streamable HTTP |
| Protocol version | 2025-06-18 |
| First observed | Aug 6, 2026 |
| Last observed | 1 h ago |
| Last successful | 1 h ago |
| Origin | Registry seed |
Facts recorded by scanners during passive observation — initialize and list calls only, never tool invocation.