Firecrawl API
/v1/llmstxt* endpoint removal
Deprecated, no dateSubscribe to Firecrawl APIShare
Firecrawl API has deprecated /v1/llmstxt* without a shutdown date, noting that the feature is being deprecated in favor of our main endpoints. Requests sent to /v1/llmstxt* fail. This change impacts any callers targeting the /v1/llmstxt* routes.
Calls it hits
/v1/llmstxt*
What to use instead of these calls
Generate the llms.txt from POST /v2/map and POST /v2/scrape, as the create-llmstxt-py example repository does.
In Firecrawl API's words
This API is being deprecated in favor of our main endpoints.
Facts
- API
- Firecrawl API
api.firecrawl.dev - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Firecrawl API's own pages
Questions
When does this change take effect?
Firecrawl API deprecated /v1/llmstxt* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Firecrawl API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Firecrawl API 5
-
No date
/v0/*Endpoint removal Deprecated, no date -
No date
/v1/deep-research*Endpoint removal Deprecated, no date -
No date
/v1/extract*Endpoint removal Deprecated, no date -
No date
/v2/extract*Endpoint removal Deprecated, no date -
No date
/v2/research/*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.