BitBooth
PAGEDELTA · $0.01 PER OBSERVATION · NO BUYER ACCOUNT OR SUBSCRIPTION

What changed on this page? Give your agent the evidence.

PageDelta renders a public page into readable Markdown. The first paid observation saves a private baseline. Later calls by the same payer can show bounded line changes and optional exact-text evidence. Pay $0.01 per observation, with no buyer account or subscription.

ILLUSTRATIVE RESPONSE · NO WALLET OR PAYMENT NEEDED TO VIEW

A policy changes. PageDelta shows the bounded line change.

Before. Saved baseline

# Pricing

Refund policy: 30 days.

After. Next observation

# Pricing

Refund policy: 14 days.

PageDelta returned

{
  "diff": {
    "hasChanged": true,
    "removedLines": 1,
    "addedLines": 1
  }
}

Removed: Refund policy: 30 days.

Added: Refund policy: 14 days.

This shortened example is not a live render, customer delivery, or payment receipt. A first paid call establishes the baseline, so change status is null. Later paid calls for the same payer, URL, and extraction mode can report what changed. Run the guided XRPL Testnet demo →

ZERO-INSTALL AGENT DISCOVERY · FREE · NO WALLET NEEDED
curl 'https://app.heinrichstech.com/discover.json?q=page%20changes&maxPrice=0.01'
Paste that URL into any web-capable agent. It returns ranked, call-ready services and only the payment rails matching the agent's policy. For a compact orientation file, use /llms.txt. No signing occurs during discovery.
OFFICIAL MCP REGISTRY · ACTIVE · LATEST 2.3.1
claude mcp add bitbooth -- npx -y @bitbooth/mcp-fetch@2.3.1
This safe default exposes only free discovery and preflight. Paid PageDelta stays hidden until the operator deliberately configures a dedicated wallet and spend caps. See the agent setup guide or inspect the official Registry record.
FREE CONNECTION CHECK · ECHO, NOT PAGEDELTA · 5 CALLS PER IP PER HOUR
curl -X POST https://app.heinrichstech.com/v1/free/echo   -H 'content-type: application/json'   -d '{"message":"hello from a curious dev"}'
This tests free API delivery, not PageDelta rendering. Use the guided XRPL Testnet demo to create a temporary wallet, establish a baseline, change the demo page, and see the verified difference.
One hero product: PageDelta Each result names its exact price, schema, example, and configured rails Request-bound payment and exact-proof replay controls
PAGEDELTA · $0.01 · BASE, XRPL, AND STELLAR MAINNETS

The web changes. Your agent should not have to rediscover everything.

The first PageDelta observation establishes a private baseline scoped to the payer, canonical URL, and extraction mode. A later observation returns the new rendered page and the bounded change since that payer's latest baseline. It does not claim that a page is true, and it does not access logins, paywalls, CAPTCHAs, or private networks.

Rendered source
bounded Markdown plus an optional 1280×720 JPEG
Exact evidence
case-sensitive focus matches, hashes, warnings, and line changes
Durable identity
payer-scoped baseline, observation ID, and payment receipt
curl -X POST https://app.heinrichstech.com/v1/cdp/render-pro -H 'content-type: application/json' -d '{"url":"https://example.com","focus":"Example Domain"}'

One paid API to start

PageDelta is the one first-party API we're offering to new agents. Send a public URL, inspect its live x402 v2 challenge, then pay only if the advertised (network, asset, payTo) terms fit your policy. The machine-readable offer is at /bazaar.json. Earlier endpoints remain callable for existing integrations, but are no longer promoted. Seller routes are private by default.

DATA

$0.01 · DATA

POST /v1/cdp/render-pro

PageDelta by BitBooth: pay $0.01 once to render a public page, extract bounded Markdown and exact focus evidence, capture an optional visual snapshot, and compare it with this payer's previous observation. Returns hashes, a tracking cursor, a content-bound observation ID, and settled payment identity. No API key or subscription.

curl -X POST https://app.heinrichstech.com/v1/cdp/render-pro

Payment support is route by route.

A paid endpoint advertises its own accepts[] array. A route may expose one configured rail or several; chain-native products can deliberately pin one. The live challenge, not this overview, is the authority for price, asset, recipient, and network.

Base mainnet
mainnet
USDC
eip155:8453
via Coinbase CDP Facilitator
XRPL mainnet
mainnet
RLUSDUSDC IOU
xrpl:0
via T54 Facilitator
Stellar pubnet
mainnet
USDC
stellar:pubnet
via self-hosted Horizon
Solana mainnet
mainnet
USDC
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
via Coinbase CDP Facilitator

BitBooth has adapters for Base, Solana, XRPL, and Stellar. A particular route advertises only the rails whose recipient and issued-asset prerequisites are configured for that route. An agent chooses only from those live requirements.

Native XRP and XLM are not advertised until an expiry-bound FX quote derives a value-correct native amount. Public transaction hashes are bearer proofs, so LINK and XRPL EVM transaction-reference rails also remain disabled until the payment proof is request-bound.

One URL is enough to start

Discovery is free and needs no install. Payment happens only after the agent chooses a service and accepts its live 402 terms.

1

Hosted discovery

Ask for a job in plain text and filter by network, asset, or maximum price. The response contains call-ready URLs, schemas, examples, and matching rails.

GET /discover.json?q=watch+wallet
2

Direct HTTP from any language

Hit a listed endpoint with curl, Node, Python, or Go. Decode and validate its PAYMENT-REQUIRED challenge, choose one advertised signed stablecoin rail within policy, and retry the identical request with PAYMENT-SIGNATURE.

curl -X POST .../v1/cdp/echo
3

MCP buyer

The official Registry-active, clean-install-verified 2.3.1 buyer adds free discovery and spend-policy preflight inside MCP. Paid tools stay hidden until the operator explicitly configures a dedicated wallet and caps.

@bitbooth/mcp-fetch@2.3.1

How it works

The agent calls a paid endpoint, decodes the route-specific x402 v2 PAYMENT-REQUIRED header, validates its accepts[] array, chooses one advertised requirement, signs, and retries the identical request with PAYMENT-SIGNATURE. A successful delivery includes a PAYMENT-RESPONSE receipt for the buyer to validate.

Agent BitBooth Facilitator (chain-specific) │ │ │ │── POST /v1/cdp/render-pro ──►│ │ │◄── 402 + PAYMENT-REQUIRED ───│ accepts[]: configured signed│ │ │ (network, asset, payTo) │ │ │ tuples │ │ │ │ │ pick chain + sign payment │ │ │── retry w/ PAYMENT-SIGNATURE ►│ │ │ │── route by network ─────────►│ │ │ eip155:8453 → CDP │ │ │ solana:* → CDP │ │ │ xrpl:* → T54 │ │ │ stellar:* → self-hosted │ │ │── verify ──────────────────► │ │ │◄── confirmed ─────────────── │ │ │── settle ──────────────────► │ │ │◄── on-chain settlement ───── │ │ │── execute handler │ │◄── 200 + PAYMENT-RESPONSE ───│ │

The first-party Base flow has a receipt-verified mainnet run. A seller rail is included in a production scope only after that seller route passes fresh settlement, receipt, paid-retry, and replay acceptance. Funds settle directly from the buyer to the seller's configured recipient.

Simple per-call pricing

No minimum and no subscription. PageDelta has one published price. Check the live 402 challenge for the exact asset, network, recipient, and amount before signing.

PageDelta

$0.01 / observation

Rendered Markdown, bounded evidence, an optional snapshot, and a payer-scoped comparison with a prior observation. The first paid call establishes a baseline and cannot report a prior change.

Read the request and receipt contract

This is the current first-party offer, not a seller plan or a revenue claim. Agents should enforce per-call and daily spend limits.

Why x402

The payment terms travel with the HTTP request, so an agent can inspect the exact requirement before signing.

Buyer access without signup

First-party paid calls do not require a buyer account. A compatible x402 client and funded wallet are still needed to authorize payment.

Bounded autonomy

Use a low-balance wallet plus client-enforced per-call and cumulative limits. The wallet balance is a durable ceiling, not a replacement for spend policy.

Request-bound delivery

The payment proof is checked against the advertised route, amount, recipient, network, and replay controls before the paid result is delivered.

One product first. The platform stays underneath.

Agents buy PageDelta observations one at a time, with no plan or subscription. BitBooth is the non-custodial payment, delivery, replay, discovery, and receipt engine underneath. Earlier first-party routes remain callable for existing integrations but are not part of the 1-product public shelf. Seller accounts are available, but route suitability and acceptance are reviewed manually. There is no active seller subscription or Launch Sprint offer, and no traffic guarantee.

$0.01
per delivered PageDelta observation
No subscription
pay only when the agent needs a fresh observation
Request-bound
settlement, replay protection, receipt, and delivery
2.3.1 MCP
public, Registry-active, and clean-install verified

Public source at github.com/Drock91/bitbooth-docs · self-hosted catalog at /bazaar.json · listed in awesome-x402

LIVE PRODUCT DEMO · XRPL TESTNET · TEST XRP HAS NO VALUE

Watch PageDelta notice a real change.

The guided demo creates a temporary XRPL Testnet wallet in your browser, funds it from the official faucet, saves a PageDelta baseline, changes an isolated demo page, and checks again. You see the actual diff and Testnet receipts. No signup, seed entry, subscription, or real money is required.

Ready to integrate?

Start with PageDelta. Teams can also create seller accounts for the wider platform. Do not rely on a route in production until its payment, delivery, retry, and replay behavior has been acceptance-tested.

Try PageDelta

Send a public URL, inspect the live 402, and authorize only an advertised $0.01 requirement that fits the agent's wallet and spend policy.

Open the PageDelta contract →

Monetize your API

Create a seller account to configure an existing public, allowlisted, Bearer-authenticated, or safe custom-header API route, its price, and payout wallets. Credential values stay in AWS Secrets Manager. Before production use, qualify and acceptance-test the route.

Create a seller account →

Seller platform status

Seller accounts can configure private pay-per-call routes and direct payout destinations. A live route is not an operator-verified listing: review route fit, settlement, receipt, paid retry, and replay behavior before relying on it in production.

There is no active seller subscription or Launch Sprint offer, and no promise of catalog placement or traffic.

Create a seller account → Inspect the receipt + replay proof →