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.
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.
- Call
review_specificationorPOST /api/reviewwith intent and, if known, specification. - If
intake_classificationsayscapability_conceptorassembly_or_system, callprepare_domain_solutioning_caseorPOST /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. - If a compatible intelligence system returns candidates, call
validate_domain_solutioning_resultorPOST /api/domain-solutioning/validatewith 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_simulationcompiles a fresh explicit load case. For a bounded section derived by the Invention Commons Protocol,prepare_derived_beam_simulationfirst 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 generalprepare_simulation_studypath remains fully caller-authored. None of these paths applies a patch, selects a candidate, contacts a supplier, or runs a solver. - Read
next_fields,remaining_fields, and CAD accelerators. Apply only facts you know; examples are not defaults. - Follow
next_callfor the recommended exact binding. Reuse the whole original request and add only the fields named inarguments.allowed_additions. For complete intent without specifications, the optionaldesign_briefcontinuation prepares a portable agent brief without a model call or stored request. When the specification is complete, inspectcontinuation_optionsto choose between budgetary pricing and a supplier handoff; both are stateless and explicitly non-authorizing. - If it points to specification resolution, submit complete intent to derive candidates; intent alone is not a supplier quote.
- When it points to pricing, call
get_supply_optionsorPOST /api/supplyfor labeled estimate ranges. - When you need a transport-neutral supplier handoff, call
build_supplier_request_packageorPOST /api/supplier-package. It applies quote-stage screening, names gaps, returns a reproducibleartifact_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'sa2a2p.argument-repairtells the agent to ask for the caller's exact purpose, preserve every other argument, and retry; it forbids inferred purpose. - When you need a human-reviewable email handoff, call
render_supplier_email_bindingorPOST /api/supplier-email-artifact. It rebuilds and re-screens the package, validates one explicit envelope, and returns an inert RFC 5322 draft withsendable=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. - When it points to resolution, submit with
request_physical_solutionorPOST /api/requeststo preserve immutable revisions. - Use
revise_requirementorPATCH /api/requests/{id}to preserve the thread while refining it; its deterministic readiness progress shows what the patch changed. - Poll
check_request_statusorGET /api/requests/{id}. Thea2a2p.resolution-report-deliveryreceipt distinguishespending_machine_draft,generation_failed,generation_expired,machine_draft, andoperator_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
https://a2a2p.com/mcp— Streamable HTTP MCP, no auth for review and pricing; finalized MCP2026-07-28uses statelessserver/discover, with the legacy2025-03-26initialize path retained.POST /api/upload— bounded temporary manufacturing-file intake; explicit purpose, strict byte identification, one-hour expiry, no downstream action.POST /api/review— deterministic engineering review, including bounded explicit beam load cases; no record stored.GET /schema/engineering-evaluationandGET /profile/engineering-evaluation— closed receipt contract and executable coverage vectors. They prove output interoperability, not physics correctness or engineering authority.GET /schema/resolution-report-delivery— closed status-delivery receipt separating pending, machine-draft, and operator-published artifacts from supplier quotes and physical authority.POST /api/domain-solutioning/case— privacy-minimized, digest-bound interoperability case; no model or external call.POST /api/domain-solutioning/validate— stateless candidate return validation; screening precedes deterministic review, no patch is applied, and invalid case shape returnsa2a2p.domain-solutioning-recovery@1.0.0with the exact preparation prerequisite.GET /profile/domain-solutioning— CC0 canonical case/result/validation fixture plus adversarial safety vectors, generated by the same live boundary and safe to replay without external action.GET /profile/domain-scaffold— CC0 executable target for deb8stack/DevAid manufacturing scaffolds: six stages, fourteen mandatory core dimensions, bounded namespaced domain extensions, typed evidence, hard-gate semantics, adversarial vectors, and an explicit link to the separate physical-domain pattern library. It makes no model call and grants no physical authority.GET /profile/domain-patterns— CC0 physical-problem contracts separated from deb8 evaluation frameworks. Registered patterns cover bounded rectangular-beam evaluation and one constant-thickness flat laser-cut supplier-fit decision. Robot design remains an explicit multi-pattern composition example, not a claimed universal capability.GET /profile/agent-swarm-interoperability— a runtime-neutral six-step map for agent teams to read patterns and evaluation rules, prepare a case, return candidates for validation, and prepare declared simulation. The companion schema describes an offline framework-improvement proposal; no public contribution endpoint, deb8 runtime, or physical authority is active.GET /profile/supplier-response-observation— a read-only, supplier-neutral map for recording what a supplier actually stated after an ordinary-prose, portal, or structured response. The companion schema stores no reply text or supplier identity, requires evidence, and grants no follow-up, quote, order, payment, or fabrication authority.GET /profile/supplier-capability— a read-only, evidence-bound description of one observed or stated supplier operating envelope. The companion schema identifies suppliers only by an opaque alias and treats each lane as partial evidence, not a live catalog, availability, a quote, supplier acceptance, or permission to contact or buy.POST /api/supplier-fit/assess— compares one package projection with every lane in one evidence-bound capability declaration. Each fact stays match, conflict, or unknown; no score, supplier selection, contact, quote, order, payment, or fabrication authority is created.supplier_selection_evidence_spine— a portable selected conformance group that checks the exact package, capability, import, fit, flat-part pattern, and empty response boundary together. It certifies no cumulative level and creates no external authority.GET /profile/supplier-import-observation— two dated supplier checks recognized the same drawing as 120 × 80 mm. Each result links to immutable evidence. The dates are known; the exact upload times are not. The package hash is local context: the second supplier received only the DXF, not the JSON request. These checks do not prove general capability, a quote, an order or a physical result. Reading them sends nothing to a supplier.GET /evidence/deb8-domain-run— privacy-minimized, machine-validated evidence from the first actual held-out deb8stack Domain Mode development run; it preserves framework, criteria, model-role, dissent, decision-effect, and calibration provenance while fixing every physical authority to false.GET /evidence/decision-lift-study— immutable prospective registration for one isolated Codex-alone versus deb8-assisted artifact comparison.GET /schema/decision-lift-study— machine-checkable registration envelope; semantic validation remains required for digest, isolation, evaluator, claim-ceiling, invalidation, and authority rules.GET /evidence/decision-lift-result— the captured two-artifact pair. Current state:artifact_comparison_unlabeled. No qualified winner or system-level lift is claimed; provenance conflicts make system-bundle attribution ineligible.GET /evidence/engineering-intelligence-baseline— exact-byte registration for a six-case developer-visible intent-to-spec calibration corpus. It tests pipeline mechanics but is ineligible for system-lift claims; it records no quality or physical claim.GET /evidence/materials/nasa-6061-t6-sheet— content-addressed observation of the NASA NTRS PDF and embedded MAPTIS page that report a 68.3 GPa longitudinal modulus for 6061-T6 sheet. It verifies document bytes and transcription, while explicitly leaving temperature, process state, actual-lot identity, physical truth, design allowable, simulation eligibility, and engineering authority unestablished.GET /profile/material-source-observation— reusable CC0 canonical and adversarial vectors proving digest/page binding, applicability consistency, verification support, and the permanent non-authority boundary.POST /api/material-evidence/plan-promotion— deterministic source/target gap plan with exact digests. It creates no material-property evidence or simulation authority.GET /profile/material-evidence-promotion— CC0 canonical and adversarial fixtures for the non-promoting gap planner.POST /api/material-evidence/validate-property— validates one independently authored material-property evidence envelope against the canonical closed schema, freshness rules, and source-class boundary. It creates a digest-bound receipt, not physical evidence or engineering authority.GET /profile/material-property-evidence-validation— CC0 canonical, computed-crystal reference-only, and adversarial validation vectors generated by the same live boundary.POST /api/material-evidence/from-materials-project— translates one exact caller-supplied Materials Project elasticity response into source-bound computed-crystal reference evidence, checks VRH bounds and Poisson consistency, and grants no engineering-product authority. The public adapter makes no upstream call.GET /profile/materials-project-elasticity— CC0 synthetic canonical, noncommercial-license, and fail-closed adapter vectors; it asserts no live Materials Project value.GET /evidence/fulfillment-containment— machine-readable proof that dormant legacy supplier, RFQ, auction, bid, order, and rating handlers are independently fail-closed behind the public route gate.GET /schema/decision-lift-result— machine-checkable pair, provenance, evaluation, claim-ceiling, and false-authority envelope.POST /api/simulation-study/prepare— binds explicit objectives, hard constraints, units, source references, solver settings, and a physical validation plan to existing candidate IDs; no solver call.POST /api/simulation-study/from-reviewed-beam— compiles one caller-selected, explicitly reviewed beam candidate into a prepared study; requires an explicit modulus, objective, source freshness, and physical validation. Optional source-bound engineering material evidence must match that modulus and carries explicit false source-verification and design-allowable claims. Computed-crystal evidence remains reference-only. The operation preserves supported acceptance limits as hard gates and runs no solver.POST /api/simulation-study/from-derived-beam— replay-validates one bounded rectangular-section proposal, requires exact validation and simulation-eligible material evidence plus objective and physical validation, and compiles it into the bounded study contract with a typed derivation source. It runs no solver and grants no engineering, supplier, purchase, or fabrication authority.POST /api/beam-section/derive— derives one proposal-only rectangular section height from screened purpose and explicit caller physics, rounds upward to a declared manufacturing increment, then re-verifies it with the bounded evaluator. It performs no general optimization, material selection, external call, or physical action.POST /api/beam-section/explore— evaluates 2–12 caller-declared widths through that same derivation and returns the exact height/idealized-volume Pareto frontier. It never invents a width, assigns an aggregate score, estimates cost, or selects a candidate.POST /api/beam-section/explore/validate— replays the entire caller-held finite design-space receipt, including every embedded derivation and Pareto disposition. It validates content identity only and never selects or promotes a candidate.POST /api/beam-section/validate— replays an exact caller-held derivation receipt and rejects candidate, screening, authority, effects, or undeclared-field mutation. Success proves content identity only; simulation and supplier eligibility remain false.POST /api/simulation-study/run— executes the versioned bounded rectangular-beam adapter only when every required physical input, unit, boundary condition, setting, and requested output is explicit; then validates hard constraints and Pareto dispositions.POST /api/simulation-study/validate— rejects masked simulation failures, recomputes hard constraints, and returns order-independent Pareto dispositions without selecting a candidate.GET /profile/simulation-study— CC0 executable preparation/run/validation fixture proving the bounded local path, not physical correctness.GET /profile/reviewed-beam-simulation— CC0 request/result and negative-vector fixture for the source-bound reviewed-load-case compiler.GET /profile/derived-beam-simulation— CC0 replay-gated derivation-to-simulation fixture with exact mutation vectors.GET /profile/beam-section-derivation— CC0 canonical and fail-closed vectors for the bounded intent-to-section bridge.GET /profile/beam-section-design-space— CC0 finite-width, order-normalization, dominance, and no-selection vectors.GET /profile/beam-section-design-space-validation— CC0 complete-replay and receipt-mutation vectors.GET /profile/beam-section-derivation-validation— CC0 canonical replay plus candidate, authority, effect, and undeclared-field mutation vectors for the independent validation boundary.POST /api/supply— labeled price and lead-time estimates; no record stored.POST /api/specification-exchange/qualify— privately qualifies one complete, unaffiliated low-voltage outdoor sensor enclosure need for a ten-submission cohort. Incomplete requests and marked probes consume no slot. It charges nothing, contacts no supplier, places no order, and grants no fabrication authority. The matching MCP tool isqualify_specification_exchange_need.POST /api/supplier-package— deterministic supplier-request package; screened at quote stage, no record stored, no supplier contact or order action.POST /api/supplier-email-artifact— deterministic RFC 5322 supplier-email draft; only an allow-screened requirement renders,sendable=false, no record stored, and no message transmitted.GET /schema/supplier-package— versioned machine-checkable output contract, including non-order, screening, and exact-package SHA-256 identity constraints.POST /api/requests,GET/PATCH /api/requests/{id}— resolution, immutable revisions, and persisted readiness progress.GET /api/providers— provider status, the raw most recent probe, a measured 24-hour reliability window, and gated pricing capability. A single failed probe reportsdegraded, neverdown.GET /evidence/providers— privacy-safe evidence from controlled provider interactions.GET /profile/supplier— the supplier request profile (spec §7.1), schema link, and canonical test vectors, so a third party can verify conformance without reading this source.GET /evidence/market-access— dated, sourced survey of whether a new entrant can obtain programmatic manufacturing access at all. CC0.GET /evidence/outcomes— CC0 aggregate provider-estimate outcomes, published only after the fixed privacy minimum is reached.GET /evidence/public-entry-activation— a digest-bound, content-free settlement of the frozen entry-path cohort after its predeclared review boundary. Before settlement it returns no provisional counts.
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.
