Rosentic is a developer-tools company whose product checks the open branches in a git repository against each other before merge, catching the function-signature mismatches, HTTP route contract breaks, GraphQL/typed-schema conflicts and Protobuf/gRPC changes that pass CI on every branch individually and break main when parallel AI coding agents land together. The engine is deterministic tree-sitter AST analysis across 13 languages with no LLM in the scan path, shipped as a GitHub Action that runs on the consumer's own runner and as rosentic-mcp on PyPI, a local MCP server and CLI with nine tools. Hosted surfaces on api.rosentic.com: Rosentic Remote, an MCP endpoint behind OAuth 2.1 with PKCE and dynamic client registration; an A2A 0.3.0 agent card with five skills and a live JSON-RPC endpoint; and a Bearer-key REST feed. Detection is free at every tier; paid plans buy stored history and quotas. No OpenAPI is published.
Rosentic is listed with 3 APIs on the APIs.io network. Tagged areas include Developer Tools, CI/CD, Version Control, Static Analysis, and Merge Safety.
Rosentic’s developer surface includes documentation, API reference, getting-started guide, pricing, engineering blog, changelog, support, and 24 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/rosentic-com/"><img src="https://apis.io/badge/rosentic-com/card.svg" alt="Rosentic on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Typed Event Surface+6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
Documented Reversibility+6 pts — a reversal operation in the contract, graded up when a window is documented too
4 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Hosted Model Context Protocol endpoint at https://api.rosentic.com/mcp (Streamable HTTP, POST), live since 2026-07-23, exposing three read tools over stored scan snapshots — run...
Agent2Agent protocol surface: an agent card served from https://api.rosentic.com/.well-known/agent-card.json (protocolVersion 0.3.0, version 1.0.0, streaming true, stateTransiti...
The Bearer-key REST surface documented on the orchestrator-integration page for wiring Conductor, Claude Squad, LangGraph and other agent orchestrators to a Rosentic workspace: ...
Rosentic ships MCP two ways and they are different products. (1) Rosentic Remote — a hosted Streamable-HTTP endpoint at https://api.rosentic.com/mcp, live since 2026-07-23 per t...
aid: rosentic-com
name: Rosentic
description: 'Rosentic is a developer-tools company whose product checks the open branches in a git repository against each
other before merge, catching the function-signature mismatches, HTTP route contract breaks, GraphQL/typed-schema conflicts
and Protobuf/gRPC changes that pass CI on every branch individually and break main when parallel AI coding agents land together.
The engine is deterministic tree-sitter AST analysis across 13 languages with no LLM in the scan path, shipped as a GitHub
Action that runs on the consumer''s own runner and as rosentic-mcp on PyPI, a local MCP server and CLI with nine tools.
Hosted surfaces on api.rosentic.com: Rosentic Remote, an MCP endpoint behind OAuth 2.1 with PKCE and dynamic client registration;
an A2A 0.3.0 agent card with five skills and a live JSON-RPC endpoint; and a Bearer-key REST feed. Detection is free at
every tier; paid plans buy stored history and quotas. No OpenAPI is published.'
url: https://raw.githubusercontent.com/api-evangelist/rosentic-com/refs/heads/main/apis.yml
image: https://raw.githubusercontent.com/Rosentic/cursor-plugin/main/assets/logo.png
x-type: company
x-source: harvest:a2a-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-09-19 (local-v3; was a2a-registry harvest stub)
specificationVersion: '0.20'
created: '2026-09-19'
modified: '2026-09-19'
tags:
- Developer Tools
- CI/CD
- Version Control
- Static Analysis
- Merge Safety
- AI Coding Agents
- MCP
- A2A
- GitHub Actions
- Agent-Native
tags_raw:
- Developer Tools
- CI/CD
- Git
- Static Analysis
- Merge Safety
- AI Coding Agents
- MCP
- A2A
- GitHub Actions
- agent-native
apis:
- aid: rosentic-com:rosentic-remote-mcp-server
name: Rosentic Remote MCP Server
image: https://raw.githubusercontent.com/Rosentic/cursor-plugin/main/assets/logo.png
description: 'Hosted Model Context Protocol endpoint at https://api.rosentic.com/mcp (Streamable HTTP, POST), live since
2026-07-23, exposing three read tools over stored scan snapshots — run_status (every lane in a run: branch, head, merged
or not, sequence position, what is clear to land next), which_lane (which lane owns a set of paths per the run manifest)
and get_verdict (the recorded gate decision for a commit SHA). Every answer carries the scan SHA and its age and returns
RESCAN_REQUIRED past the staleness window; reads are workspace-scoped and cross-org reads return NOT_FOUND. Access is
OAuth 2.1 authorization-code with PKCE S256 and RFC 7591 dynamic client registration (scope rosentic:remote:read; an anonymous
tools/list returns HTTP 401 with an RFC 9728 WWW-Authenticate challenge) or a Rosentic API key as a Bearer token, so the
live tool schemas are auth-gated. The same provider ships rosentic-mcp, a local stdio server on PyPI with nine tools,
six of them fully offline.'
humanURL: https://rosentic.com/mcp/
baseURL: https://api.rosentic.com/mcp
tags:
- MCP
- Agent-Native
- Merge Safety
tags_raw:
- MCP
- agent-native
- Merge Safety
properties:
- type: MCPServer
url: mcp/rosentic-com-mcp.yml
- type: MCPServer
name: Rosentic Remote endpoint (Streamable HTTP, OAuth 2.1)
url: https://api.rosentic.com/mcp
- type: Documentation
url: https://rosentic.com/mcp/
- type: OAuthScopes
url: scopes/rosentic-com-scopes.yml
- type: Authentication
url: authentication/rosentic-com-authentication.yml
- aid: rosentic-com:rosentic-a2a-agent
name: Rosentic A2A Agent
image: https://raw.githubusercontent.com/Rosentic/cursor-plugin/main/assets/logo.png
description: 'Agent2Agent protocol surface: an agent card served from https://api.rosentic.com/.well-known/agent-card.json
(protocolVersion 0.3.0, version 1.0.0, streaming true, stateTransitionHistory true; also byte-identical at the legacy
/.well-known/agent.json) advertising five skills — assess_integration_posture, check_conflicts, explain_conflict, list_branches
and the key-gated merge_index — served by a live JSON-RPC 2.0 endpoint at https://api.rosentic.com/a2a (tasks/get for
an unknown id answers "Task not found"). Four skills are anonymous on public repositories at 3 requests per hour per IP
with a 250MB repo cap; a Bearer API key unlocks private repos, higher limits and Merge Index. The skills serve STORED
scan results produced by the GitHub Action or local MCP; the A2A endpoint does not itself run the engine. Graded near-conformant
against A2A 1.0.0 (no preferredTransport; legacy authentication block).'
humanURL: https://rosentic.com/docs/
baseURL: https://api.rosentic.com/a2a
tags:
- A2A
- Agent-Native
- Merge Safety
tags_raw:
- A2A
- agent-native
- Merge Safety
properties:
- type: AgentCard
url: a2a/rosentic-com-a2a.yml
- type: AgentCard
name: A2A Agent Card (provider-hosted)
url: https://api.rosentic.com/.well-known/agent-card.json
- type: RateLimits
url: rate-limits/rosentic-com-rate-limits.yml
- aid: rosentic-com:rosentic-dashboard-feed-api
name: Rosentic Dashboard Feed API
image: https://raw.githubusercontent.com/Rosentic/cursor-plugin/main/assets/logo.png
description: 'The Bearer-key REST surface documented on the orchestrator-integration page for wiring Conductor, Claude Squad,
LangGraph and other agent orchestrators to a Rosentic workspace: GET /v1/feed/rules returns fleet-learned merge-safety
rules (id, layer, severity, confidence, category) for prompt injection and task routing — documented as "Available Now"
— while GET /v1/feed/hotspots (repo risk score and hot surfaces) and POST /v1/scan (hosted sibling scan) are documented
as Coming Soon, with a published error table (400 invalid_request, 401 unauthorized, 403 plan_required, 404 repo_not_found,
408 scan_timeout, 429 rate_limit_exceeded, 500 internal_error, 503 scan_unavailable). Authentication is a workspace API
key (ros_live_ prefix, issued once at https://api.rosentic.com/onboard) as Authorization: Bearer. On 2026-09-19 an anonymous
GET of /v1/feed/rules returned the host''s generic 404 ({"error":"not_found"}) rather than the documented 401, so the
endpoint could not be confirmed live without a key. No OpenAPI is published; the API root https://api.rosentic.com/ answers
a JSON descriptor naming auth, share, scan-upload, observations and agent-card URLs.'
humanURL: https://rosentic.com/docs/integrations/
baseURL: https://api.rosentic.com
tags:
- Developer Tools
- AI Coding Agents
- Merge Safety
properties:
- type: APIReference
url: https://rosentic.com/docs/integrations/
- type: Documentation
url: https://rosentic.com/docs/
- type: ErrorCatalog
url: errors/rosentic-com-problem-types.yml
- type: Authentication
url: authentication/rosentic-com-authentication.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: DomainSecurity
url: security/rosentic-com-domain-security.yml
- type: Website
url: https://rosentic.com/
- type: Documentation
url: https://rosentic.com/docs/
- type: APIReference
url: https://rosentic.com/docs/integrations/
- type: GettingStarted
url: https://rosentic.com/install/
- type: Pricing
url: https://rosentic.com/pricing/
- type: Plans
url: plans/rosentic-com-plans-pricing.yml
- type: Blog
url: https://rosentic.com/blog/
- type: ChangeLog
url: https://rosentic.com/changelog/
- type: ChangeLog
name: Changelog (structured, from the provider's JSON feed)
url: changelog/rosentic-com-changelog.yml
- type: GitHubOrganization
url: https://github.com/Rosentic
- type: Support
url: https://github.com/Rosentic/rosentic-action/issues
- type: SignUp
url: https://api.rosentic.com/onboard
- type: LinkedIn
url: https://www.linkedin.com/company/rosentic/
- type: Twitter
url: https://x.com/RosenticHQ
- type: LLMsTxt
url: llms/rosentic-com-llms.txt
- type: LLMsTxt
name: llms.txt (provider-hosted)
url: https://rosentic.com/llms.txt
- type: WellKnown
url: well-known/rosentic-com-well-known.yml
- type: AgentCard
url: a2a/rosentic-com-a2a.yml
- type: MCPServer
url: mcp/rosentic-com-mcp.yml
- type: OAuthScopes
url: scopes/rosentic-com-scopes.yml
- type: Authentication
url: authentication/rosentic-com-authentication.yml
- type: Packages
url: packages/rosentic-com-packages.yml
- type: CLI
url: cli/rosentic-com-cli.yml
- type: AgentSkill
url: skills/_index.yml
- type: Sandbox
url: sandbox/rosentic-com-sandbox.yml
- type: RateLimits
url: rate-limits/rosentic-com-rate-limits.yml
- type: ErrorCatalog
url: errors/rosentic-com-problem-types.yml
- type: Lifecycle
url: lifecycle/rosentic-com-lifecycle.yml
- type: Conventions
url: conventions/rosentic-com-conventions.yml
- type: Conformance
url: conformance/rosentic-com-conformance.yml
x-enrichment:
date: '2026-09-19'
status: enriched
artifacts_added: 25
pass: local-v3
x-a2a:
verified: true
probed: '2026-09-26'
url: https://api.rosentic.com/.well-known/agent-card.json
grade: near-conformant
protocol_version: 0.3.0
control: 404
Rosentic API — frequently asked questions
Does Rosentic have an API?
Yes. APIs.io lists 3 APIs from Rosentic, including Rosentic Remote MCP Server, Rosentic A2A Agent and Rosentic Dashboard Feed API.
How do I authenticate with the Rosentic API?
Rosentic documents its authentication (oauth2/http-bearer/none · 4 schemes). The details are profiled on APIs.io as Rosentic Com Authentication.
How much does the Rosentic API cost?
APIs.io lists 4 pricing plans for Rosentic, with each plan's price, limits and inclusions under Pricing Plans on this page.
Does Rosentic have an MCP server?
Yes. APIs.io lists 1 MCP server for Rosentic: Rosentic ships MCP two ways and they are different products. (1) Rosentic Remote — a hosted Streamable-HTTP endpoint at https://api.rosentic.com/mcp, live since 2026-07-23 per the provider's changelog
Is the Rosentic API ready for AI agents?
Rosentic has a Kin Score of 43.8 out of 100 (developing) and an Agent Readiness score of 34.6 (agent-ready), scored by API Evangelist on 2026-11-01.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: