Discover BitBooth APIs for free, then buy capped x402 fetch, PageDelta, and wallet checks.
BitBooth's featured product is PageDelta, a paid page observation API for agents.
POST https://app.heinrichstech.com/v1/cdp/render-pro
$0.01 per observation
A buyer does not need a BitBooth account or subscription. Send a page URL, inspect the x402 challenge, pay with a supported stablecoin rail, and receive rendered Markdown plus bounded change evidence.
Live links: PageDelta browser demo | featured catalog | API docs | MCP package
The first paid observation saves a baseline scoped to the payer, canonical URL, and extraction mode. A later paid observation of the same scope compares the new result with that saved baseline.
Each successful response can include:
PAYMENT-RESPONSE receiptThe cursor is not an access token, and returned web content is untrusted input. Agents should still apply their own prompt-injection and data-handling policy.
This request does not pay. It returns HTTP 402 with the current payment requirements in the PAYMENT-REQUIRED header.
curl -i -X POST https://app.heinrichstech.com/v1/cdp/render-pro \
-H 'content-type: application/json' \
-d '{"url":"https://example.com","extract":"article","focus":"Example Domain"}'
For production PageDelta, the advertised rails are:
| Network | Asset |
|---|---|
| Base mainnet | USDC |
| XRPL mainnet | RLUSD |
| XRPL mainnet | USDC IOU |
| Stellar pubnet | USDC |
The fresh 402 challenge is authoritative for the exact network identifier, asset or issuer, amount, recipient, and timeout. PageDelta does not advertise a Solana rail.
Open the PageDelta browser demo. It runs an isolated XRPL Testnet exercise:
Confirmation retries reuse the same signed proof. They do not create additional payments. This demo proves the test flow only. It is not a production payment and does not represent revenue.
The current buyer is @bitbooth/mcp-fetch@2.3.1. Its official MCP registry name is io.github.Drock91/bitbooth-fetch.
For free catalog discovery, no wallet credential is required:
{
"mcpServers": {
"bitbooth": {
"command": "npx",
"args": ["-y", "@bitbooth/mcp-fetch@2.3.1"]
}
}
}
The packaged PageDelta buyer currently automates the XRPL mainnet RLUSD path. Enabling it requires an explicit xrpl-rlusd rail, a dedicated low-balance XRPL wallet, and a per-call limit of at least 0.010000. See the integration guide before adding a seed.
https://app.heinrichstech.com/bazaar.json currently features exactly one resource: PageDelta at /v1/cdp/render-pro.
That featured catalog is a deliberate release surface. It is not a count of everything implemented inside BitBooth. Internal and reference routes may exist outside it, and private seller routes are not automatically published there.
BitBooth already has an XRPL AI merchant listing. It is an existing listing, not a new one. The external profile may lag BitBooth's current release, so the live featured catalog and fresh route challenge are authoritative.
ClawCredit's published docs describe generic x402 compatibility, including XRPL and RLUSD. BitBooth has not completed live ClawCredit interoperability or certification and is not currently a ClawCredit Partner. We do not claim guaranteed support, financing terms, or fees.
BitBooth is built and operated by Heinrichs Software Solutions Company in Tallahassee, Florida.
This repository contains public documentation, MCP package source mirrors, PageDelta integration guidance, and links to the live OpenAPI specifications. The gateway source is operated separately.
MIT. See LICENSE.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @bitbooth/mcp-fetchMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-drock91-bitbooth-fetch": {
"command": "npx",
"args": [
"-y",
"@bitbooth/mcp-fetch"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@bitbooth/mcp-fetchnpmBitBooth Agent Tools works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.