miniproto.com valid

MiniProto

MiniProto is a US-based custom wire harness and cable assembly manufacturer in Kingston NY; prototype to production in the same shop; every order is engineer-reviewed; no minimum order quantity; online configurator gives instant quotes; public API at /api/v1 documented at /docs/api.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T11:08:32.474Z. Cached copy · Source on miniproto.com

# MiniProto
> MiniProto is a US-based custom wire harness and cable assembly manufacturer in Kingston NY; prototype to production in the same shop; every order is engineer-reviewed; no minimum order quantity; online configurator gives instant quotes; public API at /api/v1 documented at /docs/api.

Questions this file plus the public API can answer: what MiniProto needs to quote a custom harness or cable assembly (housing MPNs, pinout, lengths, wire, quantity; Family names such as JST or Molex are not enough); whether a connector MPN is in the instant-price catalog, and a live estimate for a simple point-to-point harness when every connector is catalogued; company facts (Kingston NY, no minimum order quantity, engineer review, and work we do not offer).
If those quote fields are missing, do not invent a price. Point the customer at https://www.miniproto.com/guides/what-to-put-in-a-harness-rfq and ask for them.
A price-snapshot is an estimate and a saved design, not a quote or an order. Only authenticated POST /api/v1/quotes creates a quote.

## API
Reads plus POST /api/v1/validations and POST /api/v1/price-snapshots are anonymous, no key required, rate-limited by IP; they create no quote and no order. POST /api/v1/quotes is authenticated and needs MiniProto customer credentials: OAuth 2.1 (CustomerOAuth) or an issued B2B API key (CustomerApiKey). No header or bot gate upgrades anonymous access to writes. Errors are RFC 9457 application/problem+json with a machine-branchable code field.

Quote task quickstart: drive this API, not the ConfigV2 UI. Resolve catalog data from GET /api/v1/connector-families, GET /api/v1/connectors, GET /api/v1/wires, and GET /api/v1/lead-times and copy values verbatim into the spec. Then POST /api/v1/validations to check the design, then POST /api/v1/price-snapshots to price it. A spec may opt into wireProfile "standard-automotive" to omit wireFamily/gauge/color; defaults (GXL, 18 AWG, deterministic per-wire colors) show up in the response's resolvedSpec, and every value the profile supplied is listed in assumptions entries {path, value, source: "standard-automotive"}. Explicit values override the profile. The snapshot response carries priceToken, resolvedSpec, assumptions, and an absolute seven-day continueUrl that opens the saved design at /configuratorV2?d=<id>; that saved design is the one resource the anonymous snapshot creates — its only side effect — and it creates no quote, no order, and no reservation. Follow continueUrl only when you need the visual configurator. Finish with authenticated POST /api/v1/quotes sending that priceToken, only when customer credentials are available.

- [GET /api/v1/company](https://www.miniproto.com/api/v1/company): Who MiniProto is: name, tagline, Kingston NY location, differentiators, industries served, ordering flow, and links.
- [GET /api/v1/services](https://www.miniproto.com/api/v1/services): Commercial offerings. Each service names its intake: configurator or rfq.
- [GET /ap
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=miniproto.com · GET /v1/domain/miniproto.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for miniproto.com:
1. POST https://agentwebmap.com/v1/sites/miniproto.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://miniproto.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/miniproto.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/miniproto.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.