What we shipped.

We rebranded from Qcrawl to Ollagraph. The reason is honest: "Qcrawl" said we were a scraping API. We aren't. Web scraping is one of eight capability families on the platform. The tagline is now "Web infrastructure for AI agents" because that's what we actually are.

What this means for you:

• Marketing site moves to ollagraph.com
• Dashboard moves to app.ollagraph.com
• API stays on api.qcrawl.com for now — migrating to api.ollagraph.com in a future release with a long deprecation window
• Your API keys (osk_*) still work. No code change needed today.
• Your credit balance, plan, webhook secret, and usage history are unchanged.

Eight capability families, 148 endpoints, one MCP server. See the new capabilities page for the full layout.

Behind the scenes, /v1/scrape and four AEO/SEO endpoints now try an internal browser-render backend before falling back to our existing provider. No customer-facing change. Same response shape. Same credit cost.

What does change: success rates go up on hard-to-fetch sites. The proxy_used field in responses now reports render_backend, isp, or residential so you can see which path served your request.

Four endpoints that accept use_residential_proxy=true (/v1/aeo/citation-readiness, /v1/aeo/schema-coverage, /v1/seo/meta-audit, /v1/seo/snippet-candidates) now auto-refund the +3 credit surcharge when the residential fetch fails.

Previously, a Bloomberg or FT request that came back 403 still charged you 4 credits (1 base + 3 surcharge). Now: 0 credits net. Refund events are logged to your usage history.

Five new endpoints under /v1/convert/: PDF, DOCX, XLSX, PPTX, CSV → Markdown. All MIT-licensed open source under the hood (pdfplumber, python-docx, openpyxl, python-pptx). 1 credit per call. 1 MB body cap.

Image-only PDFs are flagged in the response (likely_scanned_pdf: true) so your agent knows to use a different path. A layout-aware /v1/convert/pdf-to-structured endpoint is shipping next that handles forms, multi-column papers, and scanned docs.