Skip to content

[firecrawl-ui] Complete Firecrawl v2 API coverage (deep research, llms.txt, billing, batch/crawl/extract controls)#85

Open
obeone wants to merge 14 commits into
mainfrom
worktree-feat+billing-view
Open

[firecrawl-ui] Complete Firecrawl v2 API coverage (deep research, llms.txt, billing, batch/crawl/extract controls)#85
obeone wants to merge 14 commits into
mainfrom
worktree-feat+billing-view

Conversation

@obeone

@obeone obeone commented Jun 18, 2026

Copy link
Copy Markdown
Owner

Summary

Completes UI + service-adapter coverage for the remaining Firecrawl v2 API surface. Every v2 operation now has a wired adapter in src/services/firecrawl.ts and a corresponding UI.

New views:

  • Deep Research (/research) — POST /v2/deep-research + status polling, live activities, sources, final analysis, Markdown/JSON download.
  • LLMs.txt (/llmstxt) — POST /v2/llmstxt + status polling, renders llmstxt/llmsfulltxt with downloads.
  • Billing (/billing) — credit usage + Extract token usage (GET /v2/team/credit-usage, GET /v2/team/token-usage).

Extended existing views:

  • Batch Scrape — multi-URL batch job, polling, cancel (DELETE /v2/batch/scrape/{id}) and error reporting (.../errors).
  • Crawl — list active crawls (GET /v2/crawl/active), cancel, crawl error report.
  • Extract — resume an extract job by ID (GET /v2/extract/{id}).

Wiring: routes added in src/router/index.ts, feature cards added to src/views/HomeView.vue.

Test plan

  • npx prettier --check "src/**/*.{ts,vue}" — clean
  • npx eslint src — clean
  • npm run build — succeeds (138 modules transformed)
  • Manual: each new route (/research, /llmstxt, /billing) and the cancel/errors/active/resume controls with a valid API key in localStorage.

Note: no automated tests exist in this project (npm test is a no-op); type-checking relies on eslint + the Vite build, as elsewhere in the repo.

@obeone

obeone commented Jun 18, 2026

Copy link
Copy Markdown
Owner Author

@claude Please verify in the official documentation if these endpoints exists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant