Skip to main content

PrintPrice API & Integration Contracts

This section defines how the core components of the PrintPrice platform exchange structured data.

It covers contracts between:

  • Book Pricing Engine
  • Preflight Engine
  • Production Intelligence
  • Compatibility Engine
  • Matchmaker
  • external integrations

Purpose​

The goal of the integration contract layer is to ensure that all engines in the platform communicate through deterministic and well-defined payloads.

This reduces ambiguity and makes the platform easier to scale and extend.

Main Contract Domains​

The platform currently relies on several types of contracts:

Pricing Contracts​

Used to calculate deterministic production costs.

Document Analysis Contracts​

Used to exchange technical PDF analysis results.

Production Intelligence Contracts​

Used to transfer intent detection, binding feasibility, and cross-check results.

Printer Compatibility Contracts​

Used to evaluate whether a production partner can manufacture a specific job.

Routing Contracts​

Used by the Matchmaker to return an explainable production decision.

Key Principles​

All integration contracts should follow these principles:

  • explicit schema definitions
  • stable field naming
  • deterministic values
  • explainable outputs
  • backwards-compatible evolution where possible

Typical Data Exchange​

A simplified platform exchange looks like this:

Production Specification
→ Pricing Engine
→ Preflight Analysis
→ Production Intelligence
→ Compatibility Engine
→ Matchmaker Decision

Each stage enriches the data rather than replacing it.

Long-Term Direction​

Future contracts may also support:

  • production order creation
  • partner tender workflows
  • print logistics
  • fulfillment and status tracking

These contracts will become increasingly important as PrintPrice evolves toward full manufacturing orchestration.