Part 1 x402blueprint-sdk
How Blueprint SDK Turns x402 Payments into Runnable Jobs
How Blueprint SDK translates x402 HTTP payment headers into standard JobCalls, so you write your handler once and accept payments from any chain.
Blog
Technical deep dives
Real architecture, real code, real problems solved. Organized by series.
x402 Production Runway
From TOML config to paid job execution. How Blueprint SDK integrates x402 payments, restricted invocation, pricing engines, and on-chain settlement.
13 articles
Part 2 x402payments
The x402 Facilitator Problem: How to Remove the Centralized Trust Bottleneck
The x402 protocol lets any HTTP endpoint charge for compute with stablecoin payments. But every payment flows through a single centralized facilitator. Here's why that's a problem, and how to fix it.
Part 3 x402blockchain
Pricing without hand-waving: wei pricing, token conversion, markup, and dynamic price tags
How Tangle's pricing engine lets operators set prices in USD and wei, convert to stablecoins with markup, sign tamper-proof quotes, and evolve from static config to dynamic pricing without redeploying.
Part 4 api-pricingx402
Subscription vs Pay-Per-Request API Pricing: Tradeoffs, Implementation, and When to Use Each
Subscription and pay-per-request are the two dominant API pricing models, and each optimizes for a different kind of business. This post breaks down the economic tradeoffs, implementation costs, and decision framework, with concrete implementation patterns from Blueprint SDK's pricing engine.
Part 5 tangleblueprints
On-Chain RFQ for Compute: How Job Quotes, Verification, and Slashing Work
Tangle's Blueprint SDK turns pricing into cryptographic commitments, layers verification mechanisms per job type, and backs everything with real economic consequences. Here's how the pieces fit together.
Part 6 tangleblueprint
The Signals That Keep Your Blueprint Operator Online
A practical guide to the on-chain heartbeats, quote lifetimes, and health signals that determine whether your Blueprint operator stays in rotation or loses jobs.
Part 7 blueprintx402
Operator Economics After Payment: Distribution, Exposure Weighting, and Fee Routing
When a client pays an x402 Blueprint job, the USDC moves to an operator address. What happens next is decided by the Tangle protocol: ServiceFeeDistributor splits the fee across delegators using USD-weighted exposure scores, with streaming payments for time-bounded services.
Part 8 x402tee
x402 and TEE Together: What Must Pass Before Promotion
x402 handles payment authorization. TEE handles execution integrity. Neither alone is sufficient for production. This post explains the two-gate system: what must pass before a Blueprint service activates and before job results can be trusted.
Part 9 x402blueprint-sdk
Remote Providers, Direct Runtimes, and Where Payment-Native Ingress Belongs in Deployment Architecture
Blueprint jobs can run locally, on remote VMs, on Kubernetes, or serverless. X402Gateway is a BackgroundService that multiplexes payment-gated ingress into BlueprintRunner alongside every other job source. This post maps the decision tree: which deployment target to use, how SecureBridge handles mTLS for remote execution, and where X402 ingress fits in each topology.
Part 11 x402blueprint
RFQ Job Quotes on Tangle: Signed Commitments, Result Enforcement, and Operator Accountability
How Tangle's RFQ system turns operator price quotes into cryptographic commitments, restricts result submission to quoted operators, and slashes non-delivery with a 3.5-day dispute window.
Part 12 tangleblueprint-sdk
Operator Health Monitoring on Tangle: Heartbeats, Quote Lifetimes, and Failure Signals That Matter
A practical guide to monitoring Blueprint operators in production: how the on-chain heartbeat system works, what the off-chain health monitor does differently, how quote TTLs signal service degradation, and which failure states are recoverable versus terminal.
Part 13 blueprintx402
x402 Blueprint production deployment checklist: dev, staging, and mainnet config
Step-by-step rollout sequence for taking an x402-enabled Blueprint from dev to production, with the exact config fields that change at each stage, the ones that will silently lose payments if wrong, and what the validator catches versus what it misses.
Part 14 x402product-strategy
Payment-Native Infrastructure Changes What AI Agent Products Are Worth Building
When payment is baked into infrastructure rather than bolted on top, the product strategy for AI agents shifts fundamentally. This post explains why, and what it means for what to build.
Tangle Re-Introduction
A ground-up walkthrough of Tangle's architecture: from why decentralization matters to how Blueprints, verification, and trusted execution work together.
6 articles
Part 1 infrastructureai
Why AI Infrastructure Needs Decentralization
Centralized AI infrastructure creates single points of failure, censorship risk, and vendor lock-in. Here's why decentralization is the path forward.
Part 2 blueprintsarchitecture
How Blueprints Work
Blueprints are the unit of deployable infrastructure on Tangle. This post explains their architecture, lifecycle, and how operators run them.
Part 3 verificationzk
How Tangle Verifies Work
Tangle supports multiple verification strategies - from optimistic challenges to ZK proofs. Here's how the verification layer works.
Part 4 tutorialsdk
Building on Tangle: From Idea to Production
A practical walkthrough of taking a blueprint from concept to deployment - tooling, testing, and the developer experience.
Part 5 aiinference
Building AI Services on Tangle
How to build AI inference and sandboxed execution services using Tangle's Blueprint SDK - from model loading to job routing.
Part 6 teesecurity
Trusted Execution on Tangle: How TEE Works in the Blueprint SDK
How the Blueprint SDK integrates AWS Nitro, GCP Confidential Space, and Azure CVM for hardware-isolated execution with attestation and sealed secrets.