canonical: https://jentic.com/apis/crewai.com/crewai

# CrewAI Marketing Site Public API

The CrewAI Marketing Site Public API serves the published content of the CrewAI marketing site as paginated JSON. It exposes blog posts, case studies, webinars, and events, each on its own read endpoint, plus a health check. Access is read-oriented with scoped OAuth and API-key roles, so an agent can pull the site's current content to summarise, index, or surface it elsewhere.

## For AI agents

Read paginated CrewAI marketing content: blog posts, case studies, webinars, and events. Endpoints are read-only and accept scoped OAuth or an API key, and the content is also publicly readable.

## Scope

Does not handle content creation, lead capture, or email campaigns. Use for reading CrewAI marketing content such as blog posts, case studies, webinars, and events only.

## Capabilities

- Read paginated blog posts from the CrewAI marketing site
- Read paginated case studies
- Read paginated webinars
- Read paginated events
- Check the service health of the marketing content API

## Use cases

### Marketing Content Sync

An agent pulls the CrewAI blog posts, case studies, webinars, and events as paginated JSON to index them into a knowledge base or summarise them elsewhere. Each content type has its own read endpoint, so the agent can page through just the content it needs and keep its copy current.

Example prompt: Page through GET /blog-posts and GET /case-studies to collect the current marketing content for indexing

### Event and Webinar Lookup

An agent reads the webinars and events endpoints to answer questions about upcoming CrewAI sessions or to post reminders. The endpoints return paginated JSON, so the agent can surface the next few items without scraping the marketing site.

Example prompt: Call GET /events and GET /webinars to list the upcoming CrewAI sessions

### AI Agent Integration via Jentic

An AI agent reaches the CrewAI marketing API through Jentic without handling the token itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the credential injected at run time. This lets an agent fetch current marketing content as a grounding step before it answers a question about CrewAI.

Example prompt: Search Jentic for 'read CrewAI blog posts', load the GET /blog-posts schema, and execute it with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/blog-posts` | Paginated blog posts |
| GET | `/case-studies` | Paginated case studies |
| GET | `/webinars` | Paginated webinars |
| GET | `/events` | Paginated events |
| GET | `/health` | Health check |

## Key resources

- **Blog posts** — Read paginated blog posts via /blog-posts
- **Case studies** — Read paginated case studies via /case-studies
- **Webinars and events** — Read paginated webinars and events via /webinars and /events

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 41 / 100
  - Agent Usability: 94 / 100
  - Security: 70 / 100
  - AI Discoverability: 58 / 100
- **View full report:** https://jentic.com/apis/crewai.com/crewai/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the CrewAI marketing API by hand means handling its scoped OAuth or API key, choosing the right read scope per content type, and paginating each endpoint yourself. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The API is read-only, so a rule bounds which content operations your agent may call rather than any write. You choose the reads it may call, so blog-post and case-study reads can be allowed while the webinar and event reads stay out of reach.
- **Credential handling:** Your CrewAI credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'read CrewAI blog posts' or 'list upcoming webinars', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Contentful** — Headless CMS with APIs for structured content delivery
- **Ghost** — Publishing platform with a content API for posts and pages
- **Sanity** — Structured content platform with a query API

## FAQ

### What authentication does the CrewAI Marketing Site Public API use?

The CrewAI Marketing Site Public API accepts scoped OAuth 2.0 access or an API key sent in the Authorization header, per its OpenAPI spec, with per-content read scopes such as blog and case-study reads. The content endpoints are also publicly readable. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

### Can I read CrewAI blog posts with this API?

Yes. The blog-posts endpoint returns paginated blog posts as JSON, and separate endpoints return case studies, webinars, and events. An agent can page through each content type and index or summarise it without scraping the marketing site.

### What are the rate limits for the CrewAI Marketing Site Public API?

The OpenAPI spec does not publish specific rate-limit numbers; check https://crewai.com/developers for current details. Because the endpoints are paginated reads, an agent fetches pages in sequence rather than issuing a burst of requests.

### Is there a CrewAI MCP server?

You don't need an MCP server to give your agent the CrewAI marketing content. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the content-read operations. Nothing extra is loaded into the agent's context until an operation is actually invoked.

### Can I limit what my agent is allowed to do with the CrewAI Marketing Site Public API?

Yes. The API is read-only, so a rule bounds which content operations your agent may call rather than any mutation. Allow only the reads it needs, for example blog posts and case studies, and the webinar and event reads stay out of reach, with every call logged by your own Jentic One instance.

### How do I read CrewAI blog posts through Jentic?

Search Jentic for 'read CrewAI blog posts', and it returns the blog-posts operation with its input schema. Load the schema and execute GET /blog-posts with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.