thekrew.ai APIthekrew.ai ↗
Access theKrew.ai website content via 6 endpoints. Retrieve blog posts, case studies, FAQs, and page metadata including JSON-LD, Open Graph, and full text.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/7e946b30-46d5-44dd-a12b-a1ed3239b09d/list_pages' \ -H 'X-API-Key: $PARSE_API_KEY'
List all pages on thekrew.ai from the sitemap. Returns URLs, paths, last modified dates, and priority values for all 118+ pages including blog posts, case studies, playbooks, and static pages.
No input parameters required.
{
"type": "object",
"fields": {
"pages": "array of page objects with url, path, last_modified, priority",
"total": "integer"
},
"sample": {
"pages": [
{
"url": "https://thekrew.ai/",
"path": "/",
"priority": 1,
"last_modified": "2026-06-08"
},
{
"url": "https://thekrew.ai/blog/",
"path": "/blog/",
"priority": 0.8,
"last_modified": "2026-06-08"
}
],
"total": 118
}
}About the thekrew.ai API
The theKrew.ai API exposes 6 endpoints covering the full content of thekrew.ai, including 118+ indexed pages, blog posts with category metadata, case studies, and structured FAQ sections. Use list_pages to retrieve every URL with last-modified dates and priority values, or get_blog_post to fetch a single article's full text, read time, author, and publication dates directly.
Page and Blog Content
list_pages returns every URL on thekrew.ai sourced from the sitemap — each entry includes url, path, last_modified, and priority, with a total count of 118+ pages. get_page accepts any path (e.g. /pricing/, /about/, /how-it-works/) and returns title, content, description, keywords, og_data, and a structured_data array of JSON-LD objects. This makes it straightforward to pull Open Graph metadata or schema.org markup for any page on the site without traversing them individually.
Blog Posts and Case Studies
list_blog_posts returns post summaries including title, category, excerpt, read time, and date. An optional category parameter filters results by a case-insensitive partial match against known categories like AI for Business and Growth Strategy. get_blog_post takes a slug (e.g. ai-content-marketing-drives-sales) and returns the full article text alongside article_meta — a structured object with headline, date_published, date_modified, author, and author_url. list_case_studies returns titles, subtitles describing the business type and location, and URLs for all available case studies.
FAQ Data
get_faq returns all FAQ content grouped into named sections such as "Getting started", "How theKrew works", "Control and safety", "Pricing and billing", and "For tech-savvy users". Each section object contains a questions array, and the response also provides total_sections and total_questions counts for quick validation.
- Build a content aggregator that surfaces theKrew.ai blog posts filtered by category using
list_blog_postswith thecategoryparameter - Populate a knowledge base with FAQ content from
get_faq, organized by the returned section names - Index all 118+ site pages for search by iterating
list_pagesresults and fetching full text withget_page - Extract JSON-LD structured data from any page via the
structured_datafield returned byget_page - Display a case study directory by mapping titles and subtitles from
list_case_studies - Track content freshness across the site using
last_modifieddates fromlist_pages - Pull article authorship and publication dates from
article_metainget_blog_postfor citation or content audits
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does theKrew.ai have an official developer API?+
What does `get_blog_post` return beyond the article text?+
get_blog_post returns title, description, keywords, read_time, the full content string, and an article_meta object containing headline, date_published, date_modified, author, and author_url. The slug parameter is required and must match a valid blog post slug.Can I get the full text of case studies, not just their listing metadata?+
list_case_studies returns titles, subtitles, and URLs for all case studies, but does not return full case study body text directly. You can pass a case study path to get_page to retrieve its full content. If you need a dedicated get_case_study endpoint with structured fields, you can fork this API on Parse and revise it to add that endpoint.Does `list_blog_posts` support pagination or a limit parameter?+
total count. Pagination and per-page limits are not currently supported. The API covers all posts available from the blog listing page combined with sitemap entries. You can fork it on Parse and revise to add offset or limit parameters.How current is the page data returned by `list_pages`?+
last_modified field sourced from the sitemap, so you can compare timestamps to detect stale entries. However, the API does not expose a separate refresh timestamp or guarantee a specific update cadence for the underlying data.