Get your prototype made
Home / For agents

The agent that gets your part made

Describe the part. Your agent writes the request a factory can quote, and after you confirm we send it to matching manufacturers and relay their answers. Factories answer; we introduce. No account and no API key to request quotes; tokens only to follow up on a request or to answer as a manufacturer (see auth.md). Early access: see the real figures on our numbers.

The loop

  1. Your agent writes the part (CadQuery, build123d, OpenSCAD or any CAD) and reads get_rfq_requirements: what a factory needs to quote that process.
  2. check_design tests it against typical manufacturing rules; upload_rfq_file attaches the STEP or STL.
  3. create_rfq with dry_run: true shows what is still missing. After you agree, the same call sends it.
  4. You press Confirm in the e-mail we send. Then up to five matching manufacturers that did not register with us receive it (registered ones get it at once); your e-mail address is not shown to them.
  5. Answers arrive in the thread (get_rfq_thread) and by e-mail. We do not promise prices, lead times or answers.

Prefer a browser? Get your part quoted runs the same loop with a file upload.

Have a whole product rather than one part? plan_prototype splits it into make- and buy-parts with matched factories (read-only, no e-mail); create_project then sends one quote request per make-part after the person confirms by e-mail; get_project reads the state. In a browser: Get your prototype made.

Copy into your CLAUDE.md or skill

For build123d, CadQuery, OpenSCAD or Claude Code projects: the step after "export STEP" is "find a factory". Paste this into the project's CLAUDE.md (or an agent skill):

When the user wants a part made after exporting STEP/STL:
1. Connect the MCP server https://vibe-manufacturing.com/mcp.
2. get_rfq_requirements for the process; check_design where the process is supported; ask the user for missing items.
3. upload_rfq_file with the exported file (or POST the raw bytes to /api/v1/rfq/files?name=part.step for large files).
4. create_rfq with dry_run: true and show the user what is still missing.
5. Only after the user agrees to share the request: create_rfq with their e-mail and user_consent: true.
   Tell them to press Confirm in the e-mail we send; only then does the request go to matching manufacturers.
6. Keep the rfq_id and token; poll get_rfq_thread and get_rfq and relay answers to the user.

Agent to agent, without a marketplace

Trade fairs and marketplaces exist because buyers and manufacturers could not find each other's details. Agents can. A buyer's agent sends one structured request; matched manufacturers, or their agents, answer with quotes. Nobody has to browse a catalogue, and no marketplace sits between the two sides.

  1. Buyer's agent reads what factories need with get_rfq_requirements (or GET /api/v1/rfq-requirements?process=), asks the human for what is missing, and uploads the design files with upload_rfq_file (or POST /api/v1/rfq/files?name=part.step, raw bytes, up to 100 MB).
  2. Buyer's agent checks completeness with create_rfq and dry_run: true (nothing is sent), then sends it with the user's consent. The response says whether the request is ready or incomplete and lists the best matches with contact, quote-form, portfolio and agent endpoint links.
  3. Registered manufacturers get the request by email, with expiring links to the files, and answer by replying, in their inbox, or through the API (submit_quote, send_rfq_message with their supplier token).
  4. Buyer's agent follows the conversation with get_rfq_thread (GET /api/v1/rfq/{id}/messages?since=), reads quotes with get_rfq, asks follow-up questions with send_rfq_message, or receives a signed callback (callback_url) when something arrives.
curl -s https://vibe-manufacturing.com/api/v1/rfq -H 'content-type: application/json' -d '{"process":"welding","quantity":25,"description":"Welded steel frame 800x400x300, powder coated","requester_email":"you@example.com","consent":true,"materials":["steel"],"file_formats":["step"],"ship_to_country":"DE","cad_files":[{"url":"https://example.com/frame.step","format":"step"}]}'

Files you upload stay private on our server, are shared only with the manufacturers matched to that request through links that expire after seven days, and are deleted 60 days after the last activity (you can delete them earlier with DELETE /api/v1/files/{file_id}). You can also pass a public https link in cad_files[].url. Manufacturers that publish llms.txt, an MCP server, an agent card or an OpenAPI file on their own site are marked agent-ready in the data.

Manufacturers: register to get quote requests that match you and an API token to answer them.

MCP server

Streamable HTTP, read-only except one clearly marked write tool, no authentication:

{
  "mcpServers": {
    "vibe-manufacturing": {
      "type": "http",
      "url": "https://vibe-manufacturing.com/api/mcp"
    }
  }
}

Server card: /.well-known/mcp.json

ToolWhat it does
create_rfqCreate a structured request for quotation (process, quantity, materials, CAD file links, tolerances, deadline). Returns an RFQ id, a token, and the matched manufacturers with direct contact, quote-form and agent links.
get_rfq_requirementsWhat a factory needs to quote a given process (required and recommended items, accepted values). Read it before creating a request.
upload_rfq_fileUpload a design file (STEP, IGES, STL, 3MF, OBJ, DXF, DWG, PDF, ZIP) and get a file_id for create_rfq. Larger files (up to 100 MB): POST /api/v1/rfq/files?name=...
get_rfqRead the matches, files and the quotes received so far (needs the rfq id and token).
get_rfq_threadRead the conversation with the matched manufacturers: answers, quotes, files.
send_rfq_messageAsk the matched manufacturers a question or send an update (buyer token), or answer the buyer (supplier token).
submit_quoteFor a manufacturer's agent: answer an RFQ it was matched to (needs the supplier token issued at registration).
match_manufacturersRank manufacturers for a structured part spec; returns scores and reasons.
find_suppliersList manufacturers by country, process and city.
get_design_rulesDesign-for-manufacturing rules per process: tolerances, file formats, rules with reasons, a pre-RFQ checklist and common mistakes.
check_designCheck a design against typical manufacturing rules (sheet metal, laser cutting, CNC, 3D printing, injection molding, die casting, casting, stamping, PCB) and get pass, warn or fail per check.
find_registered_businessesBusinesses you can contact directly, including official-registry establishments without a website (Mexico: INEGI DENUE; USA: SAM.gov). Contact details are published only for legal entities.
submit_quote_requestSend a quote request for your user (needs their consent). A person reviews and replies by email.
estimate_product_costLanded cost per unit and price for a target margin (USD).
get_playbook_stepOne of the 13 playbook steps with checklist.
search_siteSearch playbook, guides, tools and comparisons.
list_manufacturing_toolsDesign, fabrication, electronics and sourcing tools with pros and cons.

Example call

curl -s https://vibe-manufacturing.com/api/mcp -H 'content-type: application/json' -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "match_manufacturers", "arguments": { "process": "cnc-machining", "materials": [ "aluminium" ], "certifications": [ "iso-9001" ], "country": "DE", "limit": 5 } } }'

REST and open data

Process ids: laser-cutting, cnc-machining, sheet-metal, 3d-printing, injection-molding, pcb-assembly, die-casting, welding, waterjet-cutting, metal-stamping, forging, heat-treatment, grinding-polishing, casting, wire-forming, steel-construction, surface-finishing.

For manufacturers

Answer requests from your AI assistant

Registered manufacturers connect their assistant to our MCP server with their supplier token. The assistant can list your matched requests, read files and messages, draft quotes and send them after you confirm.

Claude Code

claude mcp add --transport http vibe-manufacturing https://vibe-manufacturing.com/mcp --header "Authorization: Bearer st_YOUR_TOKEN"

Clients with an .mcp.json-style config (Claude Code project config, Cursor and others that accept headers)

{
  "mcpServers": {
    "vibe-manufacturing": {
      "type": "http",
      "url": "https://vibe-manufacturing.com/mcp",
      "headers": { "Authorization": "Bearer st_YOUR_TOKEN" }
    }
  }
}

Connectors with sign-in (Claude.ai, ChatGPT): add https://vibe-manufacturing.com/mcp/supplier as a custom connector. You confirm once on our site with your supplier token; the assistant gets its own access token and never sees yours.

The Authorization header is the preferred way. For clients that cannot set custom headers (for example some chat connectors), connect https://vibe-manufacturing.com/mcp without authentication and pass the token as the supplier_token argument instead. The token then appears in that chat; create a new one on your manage page if you share the chat.

First prompt to try: “List my open requests on Vibe Manufacturing, summarise each one, and draft quotes for my review before sending.”

Our crawler reads your public website (see how it works) and lists the processes, materials and certifications you state. State them clearly in plain text on your site and they are picked up. Register your company for a verified, higher-ranked listing, or claim, correct or remove an existing one at any time.

Data and fair use

Data comes from OpenStreetMap contributors (ODbL), Overture Maps Foundation, Wikidata and company websites. Capabilities are detected automatically and may be incomplete; always confirm with the manufacturer. Be kind to the endpoints: cache results and keep requests under a few per second.

Your next build

Something on your screen deserves to exist.

Building your first hardware prototype, a custom enclosure, or a small batch? Describe the product once and get a make-vs-buy plan with matched factories per part.

Free for buyers. Manufacturers set their own prices and reply directly to your request.