Provider-neutral
Build once against Commonset's capability model rather than a single model provider.
DEVELOPER ACCESS
Commonset is the control plane for reusable AI capabilities. Your applications, scripts, coding agents, and internal systems can use the same trusted versions and access decisions without adopting our UI as a runtime.
Use our hosted MCP endpoint, or call the versioned HTTP API to discover and retrieve capabilities, create drafts, submit them for review, and build a custom MCP server for your environment.
API access is being introduced in stages. Contact support if your organization needs access to an endpoint that is not yet available. Capability review and approval remain governed in Commonset.
Build once against Commonset's capability model rather than a single model provider.
Permissions, tenant boundaries, active grants, and trusted versions are evaluated on each request.
Pin an immutable version by semantic version or ID instead of accepting a silent fallback.
HTTP API · V1
API base: https://app.commonset.ai/api/v1/. Authenticate with a Commonset developer token generated for your organization. Requests are JSON over HTTPS. API usage limits apply to reads and draft submissions. A valid bearer token is bound to an active user and organization.
Browse searchable endpoints, required fields, exact-version identifiers, status codes, and JSON examples in the API reference. It is rendered directly from Commonset's OpenAPI contract, so the technical details stay in one place.
The detail and package endpoints accept ?version=1.0.0 or an immutable version ID. Unauthorized and nonexistent versions return the same unavailable response. Creating or updating a capability produces a draft, not an approved or published version. New drafts are private by default.
YOUR OWN INTEGRATION
You may use Commonset as a governed registry while exposing only the tools your organization needs. A reference implementation shows how to list, retrieve, draft, version, and submit capabilities for review from a custom MCP server.
Keep credentials in your server-side environment. Creating drafts or requesting review requires the appropriate Commonset permissions and should be initiated deliberately.
View Python exampleGenerate a developer tokenDeveloper access is bound to a Commonset user and organization.
Call the REST APISearch and retrieve capabilities, then use exact-version draft and review writes when your integration is authorized.
Expose the tools you needConnect the example MCP server to a compatible agent or build your own client.
HOSTED MCP
Commonset also operates a remote MCP endpoint at https://app.commonset.ai/mcp. Compatible AI clients can authenticate and use governed discovery, retrieval, and permitted drafting tools directly. You don't need to build your own server unless you want custom behavior.
API BOUNDARIES
No. A developer token is tied to one organization, an active user, and current membership. Browser organization switching does not expand that scope.
Not necessarily. A creator can retrieve their own trusted draft. Check organization_approved and availability.scope before distributing to teammates.
Yes, through the package endpoint when the exact version is authorized. The response includes verified contents and per-file SHA-256 digests.
Yes, when writes are enabled. Create a private draft, propose a version using the exact current base UUID, and submit a version to the governed review workflow. The API cannot approve, publish, or execute it.