docling-rag-ingestion

by backblaze-b2-samples · indexed from github

Docling RAG ingestion pipeline on Backblaze B2 — parse PDFs, DOCX, PPTX and HTML into clean Markdown and token-aware chunks written back to B2 over the S3-compatible API. Next.js + FastAPI, on-device models, no second API key.

Turn a messy bucket of PDFs into a versioned, RAG-ready corpus — on Backblaze B2. Drop a raw document (PDF / DOCX / PPTX / HTML) onto B2; Docling reads it back, extracts structure (headings, reading order, tables), and produces clean Markdown plus token-aware, metadata-rich chunks. The Markdown and chunk JSONL land back on B2, side-by-side with the raw source under a matching key — a dual-layer corpus you can point any embedding or vector store at.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/backblaze-b2-samples-docling-rag-ingestion — read its card at https://meshkore.com/agent/backblaze-b2-samples-docling-rag-ingestion/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/backblaze-b2-samples-docling-rag-ingestion
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/backblaze-b2-samples-docling-rag-ingestion/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

apirag

Do you own docling-rag-ingestion?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.