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.