Documentation Index
Fetch the complete documentation index at: https://docs.dumplingai.com/llms.txt
Use this file to discover all available pages before exploring further.
Unified API
The Unified API is DumplingAI’s/api/v2 surface.
It is the recommended default for new focused data integrations. Direct Endpoints under /api/v1 remain supported for legacy request shapes and Make.com compatibility.
Use it when you want:
capabilitieslikesearch_news,extract_document,extract_audio, orscrape_page- exact
endpointslikefirecrawl.scrapeordataforseo.dataforseo_labs_google_keyword_ideas - one API key and one control surface for multiple managed providers
How it differs from Direct Endpoints
Direct Endpoints (/api/v1)
Use /api/v1 when you want the existing endpoint-oriented Dumpling product:
- direct endpoint access
- the Direct Endpoint Playground
- legacy endpoint docs and request shapes
- current Make.com compatibility
Unified API (/api/v2)
Use /api/v2 when you want the capability- and provider-oriented platform model:
- simple capabilities for common jobs
- provider-native endpoints when the exact upstream API matters
- shared logging, policy, and spend controls across those lanes
Two main lanes
Capabilities
Capabilities are the default lane. Examples:google_searchsearch_newssearch_placesget_google_reviewscrawl_sitescreenshotextract_webextract_documentextract_imageextract_audioextract_videoscrape_pageget_youtube_transcript
Providers and endpoints
Providers are vendor overview pages, and endpoints are the provider-native operations under them. Examples:firecrawlserper.searchserper.newsserper.placesserper.mapsserper.autocompleteserper.imagesserper.videosserper.shoppingserper.scholarserper.patentsperplexity.searchfirecrawl.scrapedataforseo.dataforseo_labs_google_keyword_ideas
Best next steps
- Browse the Workbench
- Try a live request in Workbench
- Read the API Reference
- See Migrating from Direct Endpoints
- Use the MCP Server if you want to connect from Claude Code, Codex, or Cursor