close
Agent quickstart · L3 reference implementation

Assess, price, clarify, and preserve the decision trail.

The Invention Commons Protocol is an open protocol for expressing a physical requirement precisely enough to review. The live reference implementation is free to use for assessment and pricing; it does not route RFQs, contact suppliers, collect payment, or place orders.

Current boundary: this is L3, not L4. Public calls return model_estimate; the protocol separately defines non-binding provider_estimate and binding provider_quote. One controlled provider estimate is published as evidence. A protected DRAFT-only evidence path additionally requires a fresh runtime verification of the provider's pinned create/read/production-transition contract. None is a fabrication or delivery commitment.

Co-invent with your agent

Agents co-invent physical products with the protocol. Start with an idea and its category, market or space. Read the ordinary web instructions or call open_co_invention_session with idea, domain, agent and a private random open_key. Hand the private follow link to your person; it opens only after they sign in to Invention Commons, and only for the account that first opens it. Follow, feed, decide, steer and end use the same free session contract through MCP or JSON requests. This adapter is tested against a stand-in; deb8's live session doors are disabled. No paid run starts here.

Agent flow

Keep the original design files. Saved JSON contains links, not CAD. If a fresh inspection cannot read or confirm an attachment, the review and supplier package stay below quote-ready. Reattach the original and review again. A format check does not prove engineering correctness or supplier acceptance.

If your agent holds local STL, STEP/STP, DXF, or PDF bytes, call upload_design_file first. It accepts common RFC 4648 base64/base64url transport forms, validates the decoded bytes before storage, and returns a one-hour HTTPS file_reference. This is intake only: it does not create a request, contact a provider, quote, order, charge, or fabricate. MCP accepts up to 2 MiB; POST /api/upload with purpose=manufacturing_design_file accepts up to 8 MiB.

If reliable exporter evidence shows that a temporary binary STL uses metre coordinates, normalize_stl_units can create the actual millimetre derivative. It requires the exact source hash and a separate finished-size check, preserves the original, and returns a newly hashed one-hour file reference. It never guesses units from a filename or plausible size.

  1. Call review_specification or POST /api/review with intent and, if known, specification.
  2. If intake_classification says capability_concept or assembly_or_system, call prepare_domain_solutioning_case or POST /api/domain-solutioning/case. It creates the versioned, privacy-minimized handoff for mechanism selection and decomposition. The public path does not call deb8stack or any model, so the response is an interoperability case—not a proposed design.
  3. If a compatible intelligence system returns candidates, call validate_domain_solutioning_result or POST /api/domain-solutioning/validate with the exact case and result. It verifies the digest and provenance shape, rejects intent/design-file/authority mutation, screens each proposal at quote stage, then runs deterministic review only after an allow verdict. Success content-addresses the exact result and returns the copy-ready simulation source binding. For a deliberately selected supported beam candidate, prepare_reviewed_beam_simulation compiles a fresh explicit load case. For a bounded section derived by the Invention Commons Protocol, prepare_derived_beam_simulation first replays the exact proposal and validation receipt, then requires matching material evidence, an objective, and a physical-validation plan. It records the derivation as its actual typed source rather than inventing a domain handoff. The general prepare_simulation_study path remains fully caller-authored. None of these paths applies a patch, selects a candidate, contacts a supplier, or runs a solver.
  4. Read next_fields, remaining_fields, and CAD accelerators. Apply only facts you know; examples are not defaults.
  5. Follow next_call for the recommended exact binding. Reuse the whole original request and add only the fields named in arguments.allowed_additions. For complete intent without specifications, the optional design_brief continuation prepares a portable agent brief without a model call or stored request. When the specification is complete, inspect continuation_options to choose between budgetary pricing and a supplier handoff; both are stateless and explicitly non-authorizing.
  6. If it points to specification resolution, submit complete intent to derive candidates; intent alone is not a supplier quote.
  7. When it points to pricing, call get_supply_options or POST /api/supply for labeled estimate ranges.
  8. When you need a transport-neutral supplier handoff, call build_supplier_request_package or POST /api/supplier-package. It applies quote-stage screening, names gaps, returns a reproducible artifact_identity.sha256, and says whether the request fits the narrow first funded proof lane. It stores and sends nothing, sets no fee, and grants no payment or supplier-contact authority. If purpose is missing, the rejection's a2a2p.argument-repair tells the agent to ask for the caller's exact purpose, preserve every other argument, and retry; it forbids inferred purpose.
  9. When you need a human-reviewable email handoff, call render_supplier_email_binding or POST /api/supplier-email-artifact. It rebuilds and re-screens the package, validates one explicit envelope, and returns an inert RFC 5322 draft with sendable=false. The plain-language draft offers optional Can quote / Need changes / Decline reply choices and asks for the minimum quote facts; normal prose still works. It cannot verify sender authentication and never sends. Do not send it to a real supplier without bona fide buyer need, purchase authority, genuine conditional intent, and budget—or the supplier's explicit consent to a disclosed test.
  10. When it points to resolution, submit with request_physical_solution or POST /api/requests to preserve immutable revisions.
  11. Use revise_requirement or PATCH /api/requests/{id} to preserve the thread while refining it; its deterministic readiness progress shows what the patch changed.
  12. Poll check_request_status or GET /api/requests/{id}. The a2a2p.resolution-report-delivery receipt distinguishes pending_machine_draft, generation_failed, generation_expired, machine_draft, and operator_published. If generation fails or expires, the old identifier will not retry; create a new request only with confirmation and the caller-held input. No operator-review or publication time is guaranteed. No state is professional engineering certification or a supplier quote.

Optional bounded physics

For an explicit rectangular beam case, add intent.functional_requirements.load_case. Supported models are cantilever_end_load and simply_supported_center_load. The review returns equations, deflection, nominal bending stress, nominal rectangular transverse shear, assumptions, requester-defined criteria, and machine-readable provenance. A supplied allowable_shear_stress_mpa is an independent conditional gate; the protocol never infers it from handbook strength data. Maximum bending and shear are separate extrema, no combined-stress interaction is claimed, and Euler–Bernoulli deflection omits transverse-shear deformation. When deflection depends on the uncited handbook modulus, the estimate and its direction remain visible but the criterion is not_evaluated and reference_only—never a pass, failure, or blocker. Supplied limits, modulus, and strength values remain unverified requester_assertion inputs; any verdict is conditional on those declarations and the bounded model, never engineering validation or design certification.

{
  "model": "cantilever_end_load",
  "load_n": 100,
  "span_mm": 200,
  "section": { "width_mm": 20, "height_mm": 10 },
  "max_deflection_mm": 3,
  "allowable_shear_stress_mpa": 1
}

Live interfaces

Known access issue — measured 2026-08-08

Requests with a User-Agent beginning Python-urllib/ receive HTTP 403 on GET endpoints (measured: /spec, /policy, /profile/supplier) from edge bot protection, before this implementation runs. POSTs from the same client pass, and python-requests, curl, Go, Node and even an empty User-Agent all pass. Until the edge rule is corrected, set any explicit User-Agent string. A protocol promising no-auth machine access should not block a standard library default; this is published rather than hidden while the fix is pending.

Protocol and safety

The schema and behavior specification are CC0 public domain at /spec. The safety policy is machine-readable at /policy; intake screening is live, and any future irreversible action requires stricter order-stage screening, a traceable responsible principal, and an independently verified provider path.

Read the specification → Conformance →