kensa.sh valid
Kensa
Kensa detects agent issues in production traces, gives coding agents evidence to investigate and fix them, and monitors later production traffic for recurrence after a fix is deployed.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://kensa.sh/llms.txt
- llms-full.txt
- https://kensa.sh/llms-full.txt
- Sections
- 5
- Links
- 23
- Size
- 4493 bytes
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Interface: a documented API or declared MCP endpoint an agent can call
- First seen
- 2026-10-27T13:26:59.244Z
- Last checked
- 2026-10-27T13:27:01.277Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T13:26:59.250Z. Cached copy · Source on kensa.sh
# Kensa
> Kensa detects agent issues in production traces, gives coding agents evidence to investigate and fix them, and monitors later production traffic for recurrence after a fix is deployed.
This site serves the hosted Kensa product. Its integrations use the `kensa-sdk` package and a project-scoped MCP connection.
Resolve the relative links below against the origin serving this file. Use that same origin for the web application, setup instructions, and MCP endpoint. The trace-ingestion endpoint can use a different origin; obtain it from `get_setup_status` rather than inferring it from the website URL.
## Start here
- [Agent setup instructions](/install): The setup skill for connecting a coding agent, configuring tracing, and verifying that a specific application trace arrived.
- [Sign in](/login): Access projects, issues, trace evidence, and fix monitoring.
- [Home](/home): Open an accessible project or the project picker; requires sign-in.
- [Pricing](/pricing): Current plans and usage information.
## Docs
Each page is also served as markdown at the link below. [All docs in one file](/llms-full.txt) joins every page.
- [Introduction](/docs/introduction.md): Kensa finds and fixes issues in your agents.
- [Quickstart](/docs/quickstart.md): Connect Kensa, check the connection, and explore your issues.
- [Concepts](/docs/concepts.md): The few terms you need to use Kensa.
- [Issues](/docs/issues.md): Look at issues and know what to do next.
- [Agent workflow](/docs/agent-workflow.md): Give your coding agent an issue, deploy the change, and report the fix.
- [Connect your coding agent](/docs/mcp/connect.md): Give your coding agent access to Kensa through MCP.
- [Tool reference](/docs/mcp/tools.md): Inputs and behavior for Kensa's MCP tools.
- [Python SDK](/docs/sdk/python.md): Send traces to Kensa from a Python app.
- [TypeScript SDK](/docs/sdk/typescript.md): Send traces to Kensa from a Node.js app.
- [Tracing](/docs/tracing.md): Send traces to Kensa from Langfuse, the Kensa SDK, or OpenTelemetry.
- [Privacy](/docs/privacy.md): How Kensa handles your keys and trace data.
- [Changelog](/docs/changelog.md): What's new in Kensa.
## Production workflow
1. Connect an existing Langfuse source or export OpenTelemetry traces over OTLP/HTTP protobuf. The optional `kensa-sdk` packages on npm and PyPI help configure tracing for TypeScript/Node and Python applications.
2. Kensa normalizes and redacts trace data before persistence, then detects issues and groups repeated occurrences with supporting trace and span evidence.
3. Review issues in the web application or let a coding agent read them through MCP. The coding agent investigates and changes the application's repository using its own tools.
4. After a fix is deployed, report its deployed revision and environment through MCP. Kensa checks later production traces for recurrence; reporting a fix alone does not prove it worked.
## Coding-agent integration
- [MCP endpoint](/api/mcp): HTTP MCP with
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| agentops.ai | AgentOps | documentation DevOps and observability AI agents and MCP +1 | US | 53 | ✓ | ✓ | |
| traces.com | Traces | interface AI agents and MCP Developer tools +1 | US | 56 | ✓ | ✓ | |
| comet.com | Opik Documentation | documentation Developer tools AI and machine learning +2 | US | 63 | ✓ | ✓ | |
| telemetry.dev | telemetry.dev | interface AI and machine learning Developer tools +1 | US | 45 | ✓ | ✓ | |
| kapa.ai | kapa.ai | documentation Developer tools Community +2 | CA | 59 | ✓ | ||
| sentry.dev | Sentry | documentation DevOps and observability | US | 60 | ✓ | ||
| latitude.so | Latitude | interface AI and machine learning AI agents and MCP +2 | US | 51 | ✓ | ||
| datadoghq.com | Datadog | interface DevOps and observability | US | 70 | ✓ |
Machine-readable: GET /v1/resolve?q=kensa.sh · GET /v1/domain/kensa.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage kensa.sh, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for kensa.sh:
1. POST https://agentwebmap.com/v1/sites/kensa.sh/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://kensa.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/kensa.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/kensa.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.