◎ Discry Score
ic consult.com
auth · API
F
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 93 (A)
Discry your API →
AUTH · RANK #16 OF 16

iC Consult is Not Agent-Ready to agents.

Discry independently scored how well an AI agent can discover and understand the iC Consult API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 26/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Fail
llms.txtAn llms.txt index that points agents to the docs that matter.Partial
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Fail
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Partial

Comprehension

55% of score · 0/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Fail
Realistic examplesRunnable, real-world request/response examples.Fail
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Fail
Error-recovery guidanceDocumented failure modes and how to recover from them.Fail
Answer-first formatThe answer leads; preamble does not bury it.Fail
Capability boundariesClear limits — what the API can and cannot do.Fail
Naming consistencyConsistent, predictable naming across endpoints.Fail
Heading hierarchyClean heading structure agents can navigate.Fail
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Fail
Token efficiencyDocs are concise enough to fit an agent context window.Fail

What we found

  • An agent looking for an iC Consult API would find none — iC Consult is an identity-security consultancy that advises on and implements third-party IAM platforms (Okta, Saviynt, CyberArk, Microsoft, SAP). There is no OpenAPI spec, no developer portal, and no endpoint documentation anywhere on the domain.
  • Positive: the site is not hostile to agents. robots.txt places no restrictions on AI crawlers (no GPTBot/ClaudeBot/CCBot blocks), and a Yoast-generated llms.txt exists at the root, so an agent crawling the domain can enumerate pages cleanly.
  • The llms.txt is a site-wide marketing link dump (webinars, events, and multi-language blog posts), not an API map — it gives an agent nothing about programmatic capabilities because none exist. llms-full.txt and .well-known/mcp.json both 404.
  • No agent-native surface of any kind: no AGENTS.md in public repos, no listing in Glama/Smithery/PulseMCP MCP registries, and no machine-readable capability declaration.
  • Comprehension scores zero because there is nothing to comprehend from an API standpoint — no endpoints, no code examples, no error handling, and no multi-step workflows. The scan measures API agent-readiness, and iC Consult is a services business, not an API.

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01If iC Consult ever exposes a service API (e.g., for its Managed Services / IAM operations offerings), publish a discoverable OpenAPI spec — that single change would raise the discovery score more than any other action.
  2. 02Replace or supplement the auto-generated Yoast llms.txt with an API-focused, right-sized file if developer-facing endpoints ever exist; today's file is a marketing sitemap in disguise and adds no agent value.
  3. 03For the current marketing-only footprint, publish a structured, clean-markdown capabilities page for the AI Security / IAM services offerings so agents can cite iC Consult accurately — the firm already markets AI-agent security, so being legible to agents is on-brand.
  4. 04Add an AGENTS.md to any public GitHub repositories (connectors, tooling, reference implementations) to give coding agents useful context and a discovery signal.

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

✕ Error format documented✕ Rate limits documented✕ Pagination documented✕ Idempotency documented

iC Consult is an identity-security consulting and managed-services firm, not a software vendor. It exposes no public API, so there is no documented authentication, error format, rate limiting, pagination, or idempotency behavior to record.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free