get_audiobook_recipe
The verified recipe for producing a long-form audiobook with local TTS: casting, per-chapter tagging, chunk sizes, and renderer settings. Settled in USDC on Base.
1 route settlement-verified · $0.005 USDC/request · 1 endpoint / 1 tools · Tools · base network · x402 protocol
Verified routes
POST /api/tools/get_audiobook_recipe· $0.005 · 2026-10-25 · receipt
Other routes are unverified.
Networks: Base (settlement-verified)
Discovery is free. Agents search the catalogue here. Payment happens on the listing 402, not on PayAPI.
url https://payapi.market/mcpListing facts
- Provider
- Quinn's Conveyance
- Hosted at
demo.quinnsconveyance.com- Category
- Tools
- Price
- $0.005 USDC per request
- Endpoints
- 1
- MCP tools
- 1
- Payment networks
- Base
- Settlement-verified
- 1 route, last checked 2026-10-25
- Listed on PayAPI Market
- 2026-10-24
Try get_audiobook_recipe
Call a verified route without paying first. The server should answer HTTP 402 Payment Required with the price, the USDC asset, the network and the wallet to pay. An x402 client pays that amount on Base and retries with the payment header.
curl -i -X POST "https://demo.quinnsconveyance.com/api/tools/get_audiobook_recipe"About this API
get_audiobook_recipe is listed in the Tools category with pricing at $0.005 USDC/request. One route has been settlement-verified by PayAPI Market on 2026-10-25. View receipt on Basescan.
Payments settle on base in USDC via the x402 protocol. AI agents discover this API through the PayAPI Market MCP server and pay per request without API keys or accounts.
This API exposes 1 endpoint.
Questions about this API
What does get_audiobook_recipe do?
The verified recipe for producing a long-form audiobook with local TTS: casting, per-chapter tagging, chunk sizes, and renderer settings. Settled in USDC on Base. It is provided by Quinn's Conveyance.
How much does get_audiobook_recipe cost?
get_audiobook_recipe is priced at $0.005 USDC per request, paid per call with no subscription. PayAPI Market paid 0.005 USDC for one call to /api/tools/get_audiobook_recipe when it verified the listing. The exact amount for each call is in the HTTP 402 response before any money moves.
Do I need an API key or account to use get_audiobook_recipe?
No. get_audiobook_recipe uses the x402 protocol, so an agent pays per request in USDC on Base and gets the response, with no API key, account or signup.
Has get_audiobook_recipe been verified?
Yes, 1 route. PayAPI Market paid for a real call from its own wallet, received real data back and recorded the USDC settlement on-chain, most recently on 2026-10-25.
How does an AI agent find get_audiobook_recipe?
Through the free PayAPI Market MCP server at https://payapi.market/mcp, using search_apis or get_api, or over plain HTTP at https://payapi.market/agent/search. Discovery is free; the agent pays the provider directly on the listing's own 402.
More Tools APIs · Browse the marketplace · List your own API
Related APIs
- Lordevo SEO & Security Checks · 1 of 13 routes verified · Pay-per-call SEO and security checks for AI agents over MCP or HTTP, via x402 in USDC on Base. Quick checks from $0.01; SEO audit $2, safe scan $1.
- Money Reactor Email Validator · 1 route verified · Email syntax check + live MX lookup via DNS-over-HTTPS (?email=user@domain.com) - verify deliverability before sending, filter junk signups, flag disposable domains. Settles in USDC via x402 (Base). Real-time deterministic response, always-deliver guarantee.
- Money Reactor QR Code Generator · 1 route verified · QR code PNG (100-1000px) for any text, URL or payment link (?data=...&size=350) - machine-scannable handoffs from agent output to human phones. Settles in USDC via x402 (Base). Real-time deterministic response, always-deliver guarantee.
- Agent Extraction API: SSL certificate check (CT logs, days left) · 1 route verified · TLS/SSL certificate check from public Certificate Transparency logs (Cert Spotter, crt.sh fallback): currently valid certificates for a hostname, newest first, with issuer, validity dates, days left, SAN names and an expiring-within-14-days flag. For expiry monitoring and phishing/subdomain vetting.
- Agent Extraction API: Domain WHOIS via RDAP (registrar, expiry) · 1 route verified · Domain registration lookup via RDAP (the official whois successor, IANA bootstrap): registered or not, registrar + IANA id + abuse email, created / updated / expiry dates, days to expiry, domain age, EPP status codes, nameservers, DNSSEC. Use it to vet a domain or check expiry.
- Agent Extraction API: DNS + SPF/DMARC mail-auth check · 1 route verified · DNS lookup over DNS-over-HTTPS (Cloudflare, Google fallback): A, AAAA, MX, NS, TXT, CNAME, CAA, SOA, SRV, HTTPS, DS... for one domain in one call, plus a mail-auth check (MX hosts, SPF, DMARC policy, warnings) and the DNSSEC-validated flag.