crowd.dev API
68
AI ReadinessAI-Aware (B+)68/100
Agent-ready OpenAPI document · curated by JenticCRMContact Managementbearer32 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Create, query, and update members, activities, organizations, tasks, notes, tags, and automations inside a crowd.dev tenant.
Use for: I need to create a new member in crowd.dev for a contributor, Query all activities for a specific member, Update an organization record with new details, Create a task to follow up with a high-value contributor
Not supported: Does not handle raw GitHub, Discord, or Slack ingestion, sentiment scoring, or billing - use for crowd.dev tenant data CRUD and automation only.
Jentic publishes the only available OpenAPI specification for crowd.dev API, keeping it validated and agent-ready. crowd.dev is a developer-first community and go-to-market data platform that unifies member, activity, and organization data across GitHub, Discord, Slack, and other community surfaces. The API exposes 32 endpoints with consistent CRUD plus query patterns for members, activities, organizations, tasks, notes, tags, and automations. Calls are tenant-scoped via the {tenantId} path variable and authenticated with a bearer token.
Install Jentic One Beta
Connect the crowd.dev API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the crowd.dev API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcrowd.dev%2Fcrowd-dev" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcrowd.dev%2Fcrowd-dev" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with crowd.dev API.
Create and update community members and query the full member set with POST /member/query
Log activities (commits, posts, replies) against members and organizations
Manage organization records that members are associated with, including bulk querying
Create tasks and notes against community records to drive go-to-market follow-up
Tag members, organizations, and activities for segmentation and reporting
Configure automations that trigger downstream workflows on community events
Use Cases
Patterns agents use crowd.dev API for, with concrete tasks.
★ Community Member Sync from External Sources
Maintain a unified view of community members by upserting them through POST /member and PUT /member/{id} from GitHub, Discord, and Slack ingestion pipelines. Teams use POST /member/query with filter expressions to pull members for outreach lists and to detect duplicates. The tenant-scoped base URL keeps multi-workspace deployments cleanly separated.
Create a crowd.dev member with GitHub username octocat and email octocat@example.com, then verify it appears in POST /member/query
Activity Stream Ingestion
Push every relevant community event into crowd.dev's activity stream by calling POST /activity with type, member ID, and source platform. Devrel teams use POST /activity/query to slice the stream by date, type, or member to surface trends and identify the most active contributors. Updates and deletes are available for correcting bad ingest.
Log a crowd.dev activity of type pull-request-merged for member ID m_42 with timestamp 2026-06-10T10:00:00Z
Automated Task Creation from High-Value Signals
Convert high-value community signals into follow-up tasks by calling POST /task with assignee and due-date, then querying open tasks via POST /task/query. Devrel and field-engineering teams use this to make sure no high-intent contributor gets dropped, and to keep follow-up evidence inside crowd.dev rather than a separate task tracker.
Create a crowd.dev task assigned to user u_7 with title 'Follow up on Stripe integration question' due in 3 days
AI Agent Community Insights
An AI agent surfaces a weekly summary of high-value community activity by querying crowd.dev through Jentic. The agent searches for the crowd_query_activities operation, executes against the team's vaulted bearer token, and joins the results with member and organization records. Jentic isolates the bearer token and tenant ID so the agent only ever holds a scoped capability.
Use the Jentic SDK to query crowd.dev activities for the last 7 days and group them by source platform and activity type
Key Endpoints
32 endpoints — jentic publishes the only available openapi specification for crowd.
METHOD
PATH
DESCRIPTION
POST
/member
Create a member
POST
/member/query
Query members with filters
POST
/activity
Create an activity
POST
/activity/query
Query activities with filters
POST
/organization
Create an organization
POST
/task
Create a task
POST
/automation
Create an automation
POST
/member
Create a member
POST
/member/query
Query members with filters
POST
/activity
Create an activity
POST
/activity/query
Query activities with filters
POST
/organization
Create an organization
POST
/task
Create a task
POST
/automation
Create an automation
Jentic AI Readiness Score
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.
C
crowd.dev API
- AI-Aware (B+)68/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
45%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
64%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring crowd.dev by hand means setting its bearer auth, substituting your tenant id into the base path (/api/tenant/{tenantId}), and posting member, activity, organization, and automation payloads yourself. Through Jentic you install once, import crowd.dev from the API Directory, store the token and tenant id once, and your agent calls it.
Permission scoping
crowd.dev carries the tenant id in the server base path (/api/tenant/{tenantId}), so a rule can pin your agent to one tenant. You choose the operations it may call, so create-automation or organization writes are not included unless you add them.
Credential isolation
Your crowd.dev bearer token and tenant id are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'query crowd.dev members' or 'log a community activity', and Jentic returns the matching crowd.dev operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using crowd.dev API through Jentic.
Why is there no official OpenAPI spec for crowd.dev API?
crowd.dev does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call crowd.dev API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the crowd.dev API use?
The crowd.dev API uses bearer-token authentication - clients send their token as Authorization: Bearer. Through Jentic, the bearer token is held encrypted in the vault and injected at request time so the raw token never reaches the agent.
Why does the base URL include a {tenantId}?
crowd.dev is multi-tenant, so every API call is scoped to a specific tenant via the path variable. You substitute your tenant ID into https://app.crowd.dev/api/tenant/{tenantId} so a single workspace can host multiple isolated communities.
How do I query members with filters through Jentic?
Search Jentic for 'query crowd.dev members', load the operation schema for POST /member/query, and execute with a filter expression. Jentic handles bearer-token injection and tenant ID configuration.
How many endpoints does the crowd.dev API expose?
Thirty-two endpoints with a consistent CRUD-plus-query shape across members, activities, organizations, tasks, notes, tags, and automations.
Can I configure automations through the API?
Yes. POST /automation creates an automation, GET /automation/{id} retrieves one, and PUT and DELETE /automation/{id} update or remove it, so the same automations you build in the UI can be managed programmatically.
Can I limit what my agent is allowed to do with the crowd.dev API?
Yes. Jentic One is self-hosted, so you run it and your own rules decide which crowd.dev operations and credentials the agent can use. Because crowd.dev carries the tenant ID in the server base path (/api/tenant/{tenantId}), a rule can pin the agent to a single tenant, and you choose exactly which operations it may call. That means read-and-query calls like POST /member/query or POST /activity/query can be allowed while writes such as POST /automation or organization changes stay out of reach unless you add them.
GET STARTED