Blueprint Pricing

SDK source (GitHub): https://github.com/tangle-network/blueprint/tree/main/crates/pricing-engine

Operator preferences interface (GitHub): https://github.com/tangle-network/tnt-core/blob/main/src/interfaces/ITangleOperators.sol

As an operator, you get paid based on how a blueprint is configured to charge. Some pricing is fixed on-chain (no quote service required). Other flows require operators to serve signed quotes off-chain (RFQ).

Prerequisites

• Basic understanding of Tangle Network operations
• Familiarity with the Blueprint Manager runtime
• Knowledge of blueprint service lifecycles

Pricing Models (What You Need to Run)

Every blueprint declares a pricing model at registration time. As an operator, your responsibilities depend on the model.

Reference: /developers/blueprints/pricing-and-payments

Fixed On-Chain Pricing (No RFQ)

In most deployments these flows do not require you to run a quote server:

• Subscription: the service is billed on-chain at a fixed subscriptionRate each interval (escrow funded by the owner).
• EventDriven with fixed per-job rates: the job submitter pays a fixed amount at submitJob(), resolved from the blueprint config and optional per-job overrides.

In these models, you still need normal operational hygiene (uptime, heartbeats, QoS, and correct consumer behavior), but you do not need to publish off-chain quotes to get paid.

RFQ Pricing (You Must Serve Quotes)

These flows require operators to generate and sign EIP-712 quotes off-chain:

• PayOnce: users create a service using createServiceFromQuotes(...).
• Job RFQ: users submit jobs using submitJobFromQuote(...).

To participate in RFQ, you need:

• a quote serving endpoint (typically the pricing-engine gRPC server)
• your on-chain operator preferences updated with that endpoint

If your quote server address changes, update it on-chain via updateOperatorPreferences (see ITangleOperators).

Running the Pricing Engine (Recommended)

The simplest path is to run the pricing-engine-server binary and configure:

• operator identity and quote signing key (operator.toml)
• service quote pricing tables (resource pricing TOML)
• job quote pricing tables (job pricing TOML)

Developer and operator details live here:

• /developers/blueprints/pricing-engine

Optional: x402 Settlement (Paid HTTP Jobs)

If you want an HTTP-first paid job interface (stablecoin settlement on EVM chains), you can run the SDK’s x402 gateway. This is separate from on-chain payment collection and is operated as a Blueprint Runner background service.

Reference:

• /developers/blueprint-runner/x402