Login

u/karkibigyan

r/thedriveai r/docusign r/VibeCodeDevs r/DropboxOfficial r/gsuite r/PptyMgmtSoftware r/googleplayconsole r/GeminiNotebookAI r/MicrosoftTeams r/chrome_extensions r/SideProject r/Rag r/ChatGPT r/AppStoreOptimization r/LangChain r/googleworkspace r/vibecoding r/FreeAppReviews r/automation
Automatically organize files with AI
▲ 2 r/FreeAppReviews

Automatically organize files with AI

Hi everyone, we are building The Drive AI, a file intelligence platform where all files get automatically organized. Would love for you to give it a try, and let me know what you think. Also a rating and a review would go a long way. Feel free to leave your app link below and I will do the same.

Site: https://thedrive.ai
Android: https://play.google.com/store/apps/details?id=com.bigyankarki.thedriveai
iOS: https://apps.apple.com/us/app/the-drive-ai/id6758524851

u/karkibigyan — 3 days ago
▲ 1 r/DropboxOfficial

Built a browser extension that lets you organize dropbox files with plain English

I got tired of manually renaming and sorting files, so I built a Chrome extension that does it with plain English commands instead of clicking through folders.

Things like:

  • "rename all these to [ClientName][Date][Type]"
  • "move invoices from last month into the Q3 folder"
  • "find every file related to the Acme project across my drive"

It works directly on top of OneDrive, Google Drive, and Dropbox — no need to download anything or change how you already work. Type what you want done, it figures out the files and does it.

The part I spent the most time on isn't the "type a command" bit — it's getting the file agent to actually understand messy, ambiguous naming and folder structures well enough to act on them correctly instead of guessing.

Still early, would genuinely appreciate people trying it and telling me where it breaks: thedrive.ai/extension

reddit.com
u/karkibigyan — 3 days ago
▲ 8 r/thedriveai+1 crossposts

Introducing The Drive AI browser extension

We just released The Drive AI Chrome Extension.

It opens as a side panel while you browse your files. No new tabs, no desktop app. Just tell it what you need in plain English: "Move last week's reports into a new Q3 folder and share it with the team". It does the rest.

Works across Google Drive, OneDrive, and Dropbox - from one panel.

This is just a step towards a larger goal. More on this soon. For now, install the extension and let me know what you think.

Link to extension: link
More info: https://thedrive.ai/extension

u/karkibigyan — 3 days ago
▲ 3 r/chrome_extensions

I built a Chrome extension that lets you manage Google Drive/OneDrive/Dropbox files with plain English commands

Hey all - I've been building an AI file assistant (https://thedrive.ai) for a while now, and I just shipped a Chrome extension version that sits on top of Google Drive, OneDrive, and Dropbox.

The idea: instead of clicking through menus to search, organize, rename, move, or share files, you just type what you want in plain English and it does it. A few examples:

  • "Find all the invoices from Q1 with unpaid status"
  • "Move all screenshots from this month into a new folder called Screenshots - June"
  • "Remove duplicate files, and share the report with [email]"

It works directly in your existing Drive/OneDrive/Dropbox tabs — no new app to learn, no migrating files anywhere.

What it's not (yet):

  • It's not a full file management replacement — for now it's best for search, organize, and share actions, not heavy editing. Its available at https://thedrive.ai
  • It's not perfect at ambiguous requests - if you're vague, it'll sometimes ask for clarification rather than guess wrong.
  • OneDrive and Dropbox support is newer than Google Drive, so there may be more rough edges there.

Would genuinely love feedback, bug reports, or just "this is dumb because X" — trying to make it actually useful, not just impressive in a demo.

Link: https://chromewebstore.google.com/detail/dielhikhcaoicomkojmkaebadghicngm?utm_source=item-share-cb

u/karkibigyan — 17 days ago
▲ 11 r/LangChain

We built a document reasoning API — curious if it solves a real pain for agent devs

I'm the founder of The Drive AI. We built this internally because our own agents needed to reason over documents — not just extract fields, but compute answers, verify numbers, cross-reference sections.

We kept rebuilding the same pipeline: pdfplumber for parsing, sandbox for math, tesseract for scans, tool-use loops, retry logic. Eventually productized it as a single API call.

You send a file + a schema describing what to figure out:

result = client.analyze(
    file="invoice.pdf",
    schema={
        "math_checks_out": {"type": "boolean", "description": "Do line items sum to total?"},
        "growth_rate": {"type": "number", "description": "YoY revenue growth"},
        "still_active": {"type": "boolean", "description": "Is this contract currently in effect?"},
    }
)

It navigates the document, computes answers in a sandbox (no LLM mental math), and returns reasoning traces + citations. Works on 107+ formats including scanned docs and websites.

Genuinely curious: are agent devs here building custom document tools for this kind of reasoning, or just stuffing PDFs into context? Is this a real pain point or are existing solutions good enough?

Free tier if anyone wants to poke at it: https://dev.thedrive.ai

u/karkibigyan — 1 month ago
▲ 21 r/automation

I built an API that turns any file or URL into structured data — 107 formats, one endpoint

Hey everyone - I've been building a file intelligence API, and wanted to share it.

The problem: If you're building an AI agent, RAG pipeline, or any app that needs to understand documents, you end up duct-taping together 5-6 different libraries — one for PDFs, one for screenshots, one for Office docs, one for markdown conversion, one for OCR. Each breaks differently and none give you structured output.

What this does:

  • Send any file or URL, get structured JSON back. Define a schema of what you need, and the API extracts it with typed fields, confidence scores, and citations pointing to where in the document the data came from.
  • 107+ file formats — PDFs, Office docs (Word, Excel, PPT), 40+ code languages, images, videos, websites. One API handles all of them.
  • Not just extraction. You can also:
    • Convert anything to clean markdown
    • Generate screenshots of URLs (with device presets, dark mode, full-page capture)
    • Ask analytical questions about documents and get reasoned, step-by-step answers
    • Get Open Graph images for link previews

What makes it different from competitor?

Most "file to X" APIs do one thing — thumbnails OR markdown OR extraction. This handles the full pipeline. And the extraction isn't just OCR-and-dump — you define a JSON schema, and it returns typed data with confidence scores. Think of it as "SQL for documents."

Would love feedback from anyone building with documents or doing AI agent work. What's missing? What would make you switch from your current setup?

reddit.com
u/karkibigyan — 1 month ago
▲ 0 r/VibeCodeDevs

I built an API that turns any file or URL into structured data — 107 formats, one endpoint

Hey everyone — I've been building The Drive AI, a file intelligence API, and wanted to share it.

The problem: If you're building an AI agent, RAG pipeline, or any app that needs to understand documents, you end up duct-taping together 5-6 different libraries — one for PDFs, one for screenshots, one for Office docs, one for markdown conversion, one for OCR. Each breaks differently and none give you structured output.

What this does:

  • Send any file or URL, get structured JSON back. Define a schema of what you need, and the API extracts it with typed fields, confidence scores, and citations pointing to where in the document the data came from.
  • 107+ file formats — PDFs, Office docs (Word, Excel, PPT), 40+ code languages, images, videos, websites. One API handles all of them.
  • Not just extraction. You can also:
    • Convert anything to clean markdown
    • Generate screenshots of URLs (with device presets, dark mode, full-page capture)
    • Ask analytical questions about documents and get reasoned, step-by-step answers
    • Get Open Graph images for link previews

What makes it different from competitor?

Most "file to X" APIs do one thing — thumbnails OR markdown OR extraction. This handles the full pipeline. And the extraction isn't just OCR-and-dump — you define a JSON schema, and it returns typed data with confidence scores. Think of it as "SQL for documents."

The simple path-based API is also something I haven't seen elsewhere: GET /md/example.com/report.pdf gives you markdown. GET /example.com gives you a screenshot. No auth needed for basic usage.

Free tier: 100 credits/month, no card required. There's also an interactive playground where you can test every endpoint without writing code.

Would love feedback from anyone building with documents or doing AI agent work. What's missing? What would make you switch from your current setup?

Give it a try at https://dev.thedrive.ai

reddit.com
u/karkibigyan — 2 months ago
▲ 3 r/Rag

I built an API that turns any file or URL into structured data — 107 formats, one endpoint

Hey everyone — I've been building The Drive AI, a file intelligence API, and wanted to share it.

The problem: If you're building an AI agent, RAG pipeline, or any app that needs to understand documents, you end up duct-taping together 5-6 different libraries — one for PDFs, one for screenshots, one for Office docs, one for markdown conversion, one for OCR. Each breaks differently and none give you structured output.

What this does:

  • Send any file or URL, get structured JSON back. Define a schema of what you need, and the API extracts it with typed fields, confidence scores, and citations pointing to where in the document the data came from.
  • 107+ file formats — PDFs, Office docs (Word, Excel, PPT), 40+ code languages, images, videos, websites. One API handles all of them.
  • Not just extraction. You can also:
    • Convert anything to clean markdown
    • Generate screenshots of URLs (with device presets, dark mode, full-page capture)
    • Ask analytical questions about documents and get reasoned, step-by-step answers
    • Get Open Graph images for link previews

What makes it different from competitor?

Most "file to X" APIs do one thing — thumbnails OR markdown OR extraction. This handles the full pipeline. And the extraction isn't just OCR-and-dump — you define a JSON schema, and it returns typed data with confidence scores. Think of it as "SQL for documents."

The simple path-based API is also something I haven't seen elsewhere: GET /md/example.com/report.pdf gives you markdown. GET /example.com gives you a screenshot. No auth needed for basic usage.

Free tier: 100 credits/month, no card required. There's also an interactive playground where you can test every endpoint without writing code.

Would love feedback from anyone building with documents or doing AI agent work. What's missing? What would make you switch from your current setup?

Give it a try at https://dev.thedrive.ai

reddit.com
u/karkibigyan — 2 months ago
▲ 1 r/vibecoding

I built an API that turns any file or URL into structured data — 107 formats, one endpoint

Hey everyone — I've been building The Drive AI, a file intelligence API, and wanted to share it.

The problem: If you're building an AI agent, RAG pipeline, or any app that needs to understand documents, you end up duct-taping together 5-6 different libraries — one for PDFs, one for screenshots, one for Office docs, one for markdown conversion, one for OCR. Each breaks differently and none give you structured output.

What this does:

  • Send any file or URL, get structured JSON back. Define a schema of what you need, and the API extracts it with typed fields, confidence scores, and citations pointing to where in the document the data came from.
  • 107+ file formats — PDFs, Office docs (Word, Excel, PPT), 40+ code languages, images, videos, websites. One API handles all of them.
  • Not just extraction. You can also:
    • Convert anything to clean markdown
    • Generate screenshots of URLs (with device presets, dark mode, full-page capture)
    • Ask analytical questions about documents and get reasoned, step-by-step answers
    • Get Open Graph images for link previews

What makes it different from competitor?

Most "file to X" APIs do one thing — thumbnails OR markdown OR extraction. This handles the full pipeline. And the extraction isn't just OCR-and-dump — you define a JSON schema, and it returns typed data with confidence scores. Think of it as "SQL for documents."

The simple path-based API is also something I haven't seen elsewhere: GET /md/example.com/report.pdf gives you markdown. GET /example.com gives you a screenshot. No auth needed for basic usage.

Free tier: 100 credits/month, no card required. There's also an interactive playground where you can test every endpoint without writing code.

Would love feedback from anyone building with documents or doing AI agent work. What's missing? What would make you switch from your current setup?

Give it a try at https://dev.thedrive.ai

reddit.com
u/karkibigyan — 2 months ago
▲ 1 r/LangChain

Open question: how are you handling document intake in your AI pipelines?

I kept running into the same problem building agent workflows: the agent needs to understand a document (PDF, spreadsheet, webpage, image) and every format needs different processing. Unstructured is one option but it's heavy and self-hosted. LangChain loaders exist but they're inconsistent across formats.

I built an API (The Drive AI) that takes any file/URL and returns:

  • Structured extraction — you define a JSON schema, it returns typed fields with confidence scores and source citations
  • Markdown conversion — clean markdown from 107+ formats
  • Analysis — ask a question about a document, get a reasoned answer with computation traces

The extraction endpoint is what I think is genuinely novel: instead of getting a blob of text and hoping your LLM parses it correctly, you get pre-structured, typed, cited data. Saves a round-trip and reduces hallucination.

Has anyone found a good solution for this? Curious what others are using for the "document → structured data" step in their pipelines.

reddit.com
u/karkibigyan — 2 months ago
▲ 1 r/SideProject

I built an API that turns any file or URL into structured data — 107 formats, one endpoint

Hey everyone — I've been building The Drive AI, a file intelligence API, and wanted to share it.

The problem: If you're building an AI agent, RAG pipeline, or any app that needs to understand documents, you end up duct-taping together 5-6 different libraries — one for PDFs, one for screenshots, one for Office docs, one for markdown conversion, one for OCR. Each breaks differently and none give you structured output.

What this does:

  • Send any file or URL, get structured JSON back. Define a schema of what you need, and the API extracts it with typed fields, confidence scores, and citations pointing to where in the document the data came from.
  • 107+ file formats — PDFs, Office docs (Word, Excel, PPT), 40+ code languages, images, videos, websites. One API handles all of them.
  • Not just extraction. You can also:
    • Convert anything to clean markdown
    • Generate screenshots of URLs (with device presets, dark mode, full-page capture)
    • Ask analytical questions about documents and get reasoned, step-by-step answers
    • Get Open Graph images for link previews

What makes it different from competitor?

Most "file to X" APIs do one thing — thumbnails OR markdown OR extraction. This handles the full pipeline. And the extraction isn't just OCR-and-dump — you define a JSON schema, and it returns typed data with confidence scores. Think of it as "SQL for documents."

The simple path-based API is also something I haven't seen elsewhere: GET /md/example.com/report.pdf gives you markdown. GET /example.com gives you a screenshot. No auth needed for basic usage.

Free tier: 100 credits/month, no card required. There's also an interactive playground where you can test every endpoint without writing code.

Would love feedback from anyone building with documents or doing AI agent work. What's missing? What would make you switch from your current setup?

Give it a try at https://dev.thedrive.ai

reddit.com
u/karkibigyan — 2 months ago
▲ 0 r/MicrosoftTeams

Teams files are notoriously messy to find later. We built an auto-organizer and want your feedback.

Hey r/MicrosoftTeams,

Finding files inside Teams channels or chat tabs can be a nightmare once a project gets busy. They get buried fast, and SharePoint's backend structure isn't always intuitive for everyone on the team.

We built an integration for the drive ai to bridge this gap.

It automatically monitors your designated Teams channels. When a file is uploaded, it instantly pulls it into your drive and uses AI to organize it based on your folder setup or plain English commands (e.g., "Move all design mockups from the Marketing channel to the Q2 Assets folder").

We’re looking for input from daily Teams users:

  • How do you keep your Teams files from turning into total chaos?
  • Would you prefer files sorted automatically by channel topic, or by file type?

Appreciate any brutal feedback you have on this concept!

reddit.com
u/karkibigyan — 2 months ago
▲ 1 r/gsuite

Built a tool to stop the "downloading and sorting email attachments" nightmare. Looking for feedback.

Hey everyone,

Our team was spending hours every week downloading invoices, PDFs, and project assets from Gmail and manually dragging them into the right cloud folders. It felt like a massive waste of time, and things always got missed.

To fix this, we built an integration for our tool, the drive ai.

Whenever an email attachment hits your inbox, it automatically syncs to your drive. The AI looks at your existing folder structure (or plain English rules you write out, like "Put all PDF invoices into the 2026 Expenses folder"), and neatly files it away.

We are trying to perfect the rules engine right now.

  • What is your biggest headache when managing email attachments?
  • Do you find yourself sorting by client, project, or date?

Would love to hear how you currently handle this or what features we should add next!

reddit.com
u/karkibigyan — 2 months ago
▲ 2 r/SideProject

Submit Your AI Tool, We’ll Handle the Rest

Hi everyone, we just launched an AI tools directory where you can submit your tool/site, and we’ll handle the rest. Also, anyone who submits their tool and DMs me will get a free blog post on the site featuring their product as well. Cheers.

withaitools.com

reddit.com
u/karkibigyan — 3 months ago
▲ 9 r/GeminiNotebookAI+6 crossposts

Hi there,

I am the founder of an agentic file management tool called The Drive AI, and we recently launched our mobile apps for both iOS, and Android, but having difficulty with visibility. What would you suggest we should optimize for? Any insights would be helpful

Cheers!

u/karkibigyan — 3 days ago