www.kondevs.com
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
www.kondevs.com
Preparing the stored Is Agentic score
www.kondevs.com
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Strong
Weighted across 17 applicable checks
Strong
Weighted across 12 applicable checks
Ready with gaps
Weighted across 3 applicable checks
Strong
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
No material issues were found in the applicable checks.
Checks are grouped by relevance for Business sites.
5241 chars, semantic headings (1 H1 + 9 H2s + 17 H3s), 23.5% content ratio
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 6 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
kondevs.com ranks #3 for "KONDEVS IT Consulting"
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://www.kondevs.com/sitemap.xml with 58 entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block)
All metadata signals present: canonical URL, lang="en", og:image, og:type
Organization schema complete with contactPoint and address
All trust anchor pages verified: About, Contact, Privacy
All 7 measured pages fit an agent context budget (largest ~5K tokens)
ARD catalog valid at /.well-known/ard.json (spec 1.0) - 4/4 entries
Valid AI Catalog at /.well-known/ai-catalog.json (spec 1.0) - 4/4 entries
All 4 entries valid with domain-anchored urn:air identifiers (catalog at /.well-known/ard.json)
Agent discovered 1 developer-resource type by name (developer portal) across 2 pages
Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 3 skill(s)
Index v0.2.0 conformant; verified SHA-256 of "content-hub" (skill-md); 2 other skills present; not fetched
A2A Agent Card found: "KONDEVS Content Hub Agent"
MCP server discoverable via server-card.json at /.well-known/mcp/
RFC 8288 Link header advertises: describedby, service-desc, api-catalog
Found the llms.txt at https://kondevs.com/llms.txt.
The llms.txt is well-formatted: 51 lines with markdown links, 7,115 characters in total.
API/docs link found on homepage and resolves: /developers/
Agent Skill "content-hub" says when to use it at /.well-known/agent-skills/index.json - description: "Use when researching enterprise integration (EAI), BPM, SAP or AI consulting topics, or wh..."
Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub)
How to pass
Add sameAs links in your JSON-LD structured data pointing to your Wikipedia page, Wikidata entry, GitHub org, and social profiles. This helps AI disambiguate your brand from similarly named entities.
Some extended schema types found: LocalBusiness - add 2 more types, such as FAQPage, Service, or AggregateRating, for full coverage
How to pass
Add 2 more JSON-LD types that fit your page, such as FAQPage, Service, or AggregateRating.
All 5 probed llms.txt links resolve to real content
Code fences balanced across 2 markdown documents
OpenAPI spec found at https://www.kondevs.com/openapi.json (version: 3.1.0)
Developer portal found at /developers
api-catalog linkset[0] has no 'item' entries
How to pass
Publish an API catalog at /.well-known/api-catalog per RFC 9727. Serve it with Content-Type: application/linkset+json;profile="https://www.rfc-editor.org/info/rfc9727" and include a 'linkset' array with item entries pointing to your OpenAPI specs and service descriptions.
Path-suffix markdown docs served with text/markdown content-type: /auth.md
All 4 tools on docs MCP have detailed descriptions (>= 30 chars)
4/4 tools on docs MCP have parameter schemas
docs MCP identifies as "kondevs-content-hub" v1.0.0 with instructions
docs MCP exposes 4 tools - consider consolidating to keep agent attention focused on retrieval
How to pass
Expose your tools via your MCP server's tools/list endpoint. A product MCP server scores on breadth: 3 or more tools that cover read, write, and search. A docs MCP server scores on focus: 3 tools or fewer, such as one search tool and one fetch tool. Keep every outputSchema valid and self-contained: a $ref that points outside the schema, such as #/components/schemas/... copied from an OpenAPI file, makes clients built on the official TypeScript SDK 1.x reject your whole tool list.
All 4 tool names follow consistent convention, descriptive, and non-generic
REST API documentation found at https://www.kondevs.com/developers/. Best-of-protocols score: 7/7.
OAuth authorization server metadata at https://www.kondevs.com (issuer=https://www.kondevs.com)
OAuth security scheme "oauth2" declares 2 named scope(s) in the OpenAPI spec (e.g. content:read, content:write)
docs MCP is public - correct posture for documentation surface
Verified live: GET https://www.kondevs.com/api/ answered 200 without credentials (zero-auth access). Described but not verified live: free tier available
How to pass
Offer a free tier or trial, self-serve API key generation, and a sandbox environment. Agents can't fill out 'contact sales' forms.
RFC 9728 metadata: resource=https://www.kondevs.com, authorization_servers (1), scopes_supported (2), bearer_methods_supported
auth.md at https://kondevs.com/auth.md served as text/markdown; charset=utf-8 (4747 chars)
auth.md at https://kondevs.com/auth.md - 2/8 walkthrough sections (found Discover and Use credential; missing Pick a method, Register, Claim, Exchange, Errors, and Revocation); anchors: oauth-protected-resource and oauth-authorization-server
How to pass
Structure /auth.md as the WorkOS spec prescribes: sections for Discover, Pick a method, Register, Claim, Exchange, Use the access_token, Errors, and Revocation, with spec anchor keywords (agent_auth, identity_endpoint, identity_assertion, service_auth, id-jag, WWW-Authenticate). Reference https://github.com/workos/auth.md.
Static fallback (deep check disabled): PRM + AS metadata both reachable with agent_auth.identity_endpoint (https://www.kondevs.com/api/oauth/register) (advertised under the pre-v0.2 register_uri key); walkthrough discoverable end-to-end
PRM + AS metadata present with agent_auth.identity_endpoint (https://www.kondevs.com/api/oauth/register) (advertised under the pre-v0.2 register_uri key) (AS metadata fetched from advertised origin https://www.kondevs.com) but identity_types_supported [client_credentials] contains no spec-valid values (expected one of: anonymous, identity_assertion, service_auth; the assertion variant, the ID-JAG URN, lives in identity_assertion.assertion_types_supported)
How to pass
Publish RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource on your resource server (the host that actually serves the API, e.g. api.<apex>) with resource and authorization_servers. Publish RFC 8414 authorization-server metadata at /.well-known/oauth-authorization-server on the AS origin, and include the WorkOS auth.md agent_auth block with identity_endpoint, identity_types_supported drawn from the spec enum (anonymous, identity_assertion, service_auth - the assertion variant, the ID-JAG URN urn:ietf:params:oauth:token-type:id-jag, belongs inside identity_assertion.assertion_types_supported, not at the top level), and the identity_assertion.assertion_types_supported block when you advertise that type, so agents can check their assertion shape is accepted before minting. Cross-link by listing the AS origin in PRM authorization_servers, and point agent_auth.skill back at your published /auth.md. Spec: https://github.com/workos/auth.md.
agent_auth endpoints reachable (source: AS metadata agent_auth block) - identity_endpoint: HTTP 405, claim_endpoint: not advertised, events_endpoint: not advertised
MCP server connected via Streamable HTTP - kondevs-content-hub v1.0.0 (protocol 2025-06-18)
docs MCP returns structured JSON-RPC errors with code and message
docs MCP uses modern Streamable HTTP transport
Imperative WebMCP API detected (document.modelContext.registerTool in script bundle /js/main.js).
REST rate-limit headers documented in OpenAPI spec, but not observed on a live response.
How to pass
Return standard rate-limit headers on your API responses (the RFC RateLimit headers, plus Retry-After on a 429) so agents can self-throttle in real time, and document the conventions alongside your API.
REST Idempotency-Key header referenced on POST /api/content/ via #/components/parameters/IdempotencyKey
API returns JSON error responses (404 at https://www.kondevs.com/api/v1/orank-probe-test)
OpenAPI defines a typed error schema in components.schemas and 4xx/5xx responses reference it
API versioning strategy found (header versioning) with Deprecation and Sunset headers documented at https://www.kondevs.com/openapi.json
Offset/page-based pagination found in OpenAPI spec - consider migrating to cursor-based pagination for agent friendliness
How to pass
Use a consistent, documented pagination shape on your list endpoints (cursor-based preferred) and define the pagination fields in your OpenAPI response schemas, so agents can page through results without guessing the shape.
202 Accepted responses found but no clear polling pattern (Location header, /jobs path, or job_id schema)
How to pass
For long-running operations, return 202 Accepted and point agents at where to poll for the result (a status/location reference plus a job identifier in the body), documented in your OpenAPI spec, so work that does not finish in one request is still followable.
82% of operations define typed response schemas, 82% use application/json
docs MCP: 4/4 tools have behavioral annotations
MCP server card found at https://www.kondevs.com/.well-known/mcp/server-card.json but missing fields: name, version
How to pass
Publish a server card for each MCP server (draft MCP server-card extension). List each card in /.well-known/ai-catalog.json, or serve it at <server URL>/server-card. /.well-known/mcp/server-card.json is still read for a site with one server, but the extension does not recommend it. Include name, description, and version, and put the server's exact address in remotes[].url (serverUrl is also read) so agents match each card to the right server before connecting. Follow the extension schema for full credit: $schema set to https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json, a reverse-DNS name such as com.example/mcp, and no tools[] (agents always trust the live tools/list). Keep the description to 100 characters or fewer, as the schema requires. A card without that $schema is still read, and then an optional tools[] list completes it.
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
41 native controls, 0 non-native div-soup affordances (100% native).
41/41 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
REST: agent-friendly schema (17 operations, 100% with operationIds, 100% documented by description or summary)
Compatible: 17/17 ops with IDs, 11/17 with typed schemas
What does www.kondevs.com do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does www.kondevs.com do and who is it for? Explain it back to me.
9 steps2 reasoning steps1 search
The agent successfully assembled a comprehensive overview of KONDEVS's business model, target customers, and competitive positioning from the site's core pages. The site proved navigable but deliberately opaque on pricing and engagement scope—the agent had to fill those gaps by inferring from missing information rather than retrieved facts.