Skip to main content
GUIDES

Long-form guides with working code.

Eight flagship guides. Each one walks you from prerequisites through deployment, with copy-paste code in TypeScript and Python and the common pitfalls called out explicitly.

WHAT A GUIDE LOOKS LIKE

Every guide has the same shape.

We chose a strict template because the inconsistent shape of competitor tutorials is what makes them hard to use. Every Blockchain0x guide starts with a 60-word answer paragraph (what AI search engines extract for citations), then prerequisites, then numbered steps with code, then common pitfalls, then a next-steps section that links to relevant glossary entries and product pages.

Word count target per guide is 1800+. That is on the long end of what most readers actually skim through, but it is deliberate: shallow tutorials make you debug your way through the missing detail. Our guides spell out the edge cases so you do not have to.

Every guide is code-tested against current Blockchain0x API behavior. When the API ships a breaking change, we update the guides in the same release. Each entry has a "last reviewed" date visible at the top.

THE 8 FLAGSHIP GUIDES

Pick the one that matches today's task.

How to add payments to your AI agent

The end-to-end guide. Create your wallet, install the SDK, request your first USDC payment, handle the webhook. Works with LangChain, CrewAI, AutoGen, LlamaIndex, OpenAI Agents SDK, MCP servers.

10 minutes read

Monetize your MCP server in 10 minutes

Turn a free-traffic MCP server into a paid service. Install requirePayment middleware, wrap your tools, deploy. Includes the cache architecture and Redis setup for production.

10 minutes read

Set up agent spend controls that survive prompt injection

Per-payment caps, daily caps, allowlists. Why API-layer enforcement beats agent-code rules. Worked examples of an agent hitting a cap, plus the policy evaluation algorithm in detail.

8 minutes read

Earn the GitHub and domain verification badges

Walk through both verification flows. GitHub OAuth setup, DNS TXT record format, monthly re-check behavior. Shows what counterparties see when they hover the badge on your agent's public page.

8 minutes read

The webhook patterns developers ask about most

Signature verification (HMAC-SHA256 constant time), idempotency under retry, handling payment.failed cleanly, resume-after-payment via job queues. Includes patterns for Celery, arq, and Bull.

15 minutes read

Test agent payments without real money

Using test keys and the Base Sepolia sandbox. How to generate test USDC, simulate the full payment lifecycle, and validate webhook delivery before going to production. Plus the differences between test and live behavior.

12 minutes read

Migrate from Stripe to Blockchain0x for agent-driven API access

Run Stripe alongside Blockchain0x: humans pay via Stripe Checkout; agents pay via 402 Payment Required. Includes the decorator pattern that gates the same API endpoint behind both auth methods.

20 minutes read

Secure your agent wallet before going live

Pre-flight security checklist. Wallet provider choice (smart wallet vs EOA), spend cap defaults, API key rotation cadence, webhook signing-secret hygiene, audit-log review, and incident-response runbook setup.

15 minutes read

Guides publish weekly, prioritized by what customers ask about in support. If a topic you need is missing, the fastest path is to start using Blockchain0x and tell us what stumped you - that becomes the next guide.

PICK BY SHAPE

Which guide first.

  • First time using Blockchain0x: "How to add payments to your AI agent" - the end-to-end flow.
  • Running an MCP server: "Monetize your MCP server in 10 minutes" - the middleware setup.
  • About to go to production: "Secure your agent wallet before going live" - the pre-flight checklist.
  • Worried about safety: "Set up agent spend controls that survive prompt injection" - policy evaluation.
  • Migrating from Stripe: "Migrate from Stripe to Blockchain0x for agent-driven API access" - the dual-checkout pattern.

Guides cross-link generously: most of them reference at least one glossary entry (for vocabulary), one product page (for feature detail), and at least one other guide (for the next logical step). You can read through 2-3 guides as a coherent path rather than treating each as isolated.

OTHER SHELVES

Vocabulary first, then guides, then comparisons.

If a term in a guide is unfamiliar, the glossary defines it canonically. If you are picking Blockchain0x vs alternatives, the comparisons walk through the trade-offs honestly.

See the glossary See the comparisons

Read while you build.

Every guide ships with copy-paste code. Sign up for free and apply it directly.