tidbit.legios.com.ar
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
tidbit.legios.com.ar
Preparing the stored Is Agentic score
tidbit.legios.com.ar
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
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 Docs & content sites.
2074 chars, semantic headings (1 H1 + 5 H2s + 7 H3s), 14.7% 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
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://tidbit.legios.com.ar/sitemap.xml with 236 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 ~2K tokens)
Name search surfaced no pages on tidbit.legios.com.ar, although developer resources exist on the site (API docs, OpenAPI spec, MCP server) - weak search indexing or transient search noise
How to pass
Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
NPM package found: @legios/quartermaster - "Cuánta cuota te queda en TODOS los perfiles de Claude Code de la máquina, más Codex y los proveedores de opencode. Sin red y sin credenciales: el número sale del cache que Claude Code deja en disco."
MCP manifest has name and description but no icon at /.well-known/mcp/server-card.json
How to pass
Give your MCP server-card (at /.well-known/mcp/server-card.json) a display name, an icon or logo, and a description - all three together are what reads as a complete, branded listing agents can present.
Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 1 skill(s)
Index missing $schema field - treated as v0.1.0; add "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json" to upgrade
How to pass
Upgrade /.well-known/agent-skills/index.json to the v0.2.0 schema: add "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json", and give every entry a type (skill-md or archive), url, and digest. Use "digest": "sha256:<64 lowercase hex chars>" (e.g. "digest": "sha256:a3f1...") - a bare "sha256": "<hex>" field is also accepted. Compute the value from the artifact's raw bytes. For archives, hash the ZIP or tar.gz download itself; a separate skill-md entry is not required.
MCP server discoverable at standard path https://tidbit.legios.com.ar/.well-known/mcp.json
Agent mode view found at ?mode=agent (3 signals: llms.txt, api, agent)
How to pass
Add a ?mode=agent query parameter to your homepage that returns a structured, machine-readable view with API endpoints, authentication info, and key capabilities instead of marketing HTML.
RFC 8288 Link header advertises: sitemap, describedby, api-catalog, alternate(markdown)
Partial markdown fallback support. Homepage (https://tidbit.legios.com.ar/index.md) returns markdown, but 1 of 1 sampled content page do not: https://tidbit.legios.com.ar/developers.md. To earn full credit, serve a .md twin for each content page (e.g. /docs/auth -> /docs/auth.md) with text/markdown content-type or a heading-led non-HTML body.
How to pass
Let agents fetch markdown by appending .md to page URLs. Required for any credit: serve a markdown homepage at /index.md. For full credit (2/2): also serve a .md twin for each content page (e.g. /docs/auth -> /docs/auth.md). Content-Type should be text/markdown and the body should start with a top-level heading (not HTML).
100% of 236 sampled sitemap entries carry lastmod; newest is 0 day(s) old
Found the llms.txt at https://tidbit.legios.com.ar/llms.txt.
The llms.txt is well-formatted: 132 lines with markdown links, 17,657 characters in total.
API/docs link found on homepage and resolves: /developers/
Agent Skill "tidbit" says when to use it at https://tidbit.legios.com.ar/skills/tidbit/SKILL.md - description: "Use when a non-technical user asks what a tech term means (API, token, data lake, VPN, Kub..."
Entity linking to github.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.
All 5 probed llms.txt links resolve to real content
Markdown alternate advertised and verified: https://tidbit.legios.com.ar/index.md serves markdown
Code fences balanced across 2 markdown documents
OpenAPI spec found at https://tidbit.legios.com.ar/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: /index.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 "io.github.legiosai/tidbit" 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://tidbit.legios.com.ar/developers/. Best-of-protocols score: 7/7.
docs MCP is public - correct posture for documentation surface
Verified live: GET https://tidbit.legios.com.ar/v1/terms.json answered 200 without credentials (zero-auth access). Described but not verified live: free tier available, self-serve key generation
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.
MCP server connected via Streamable HTTP - io.github.legiosai/tidbit v1.0.0 (protocol 2025-11-25)
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 /app.js).
The live API operation https://tidbit.legios.com.ar/v1/terms.json returns IETF RateLimit headers: ratelimit, ratelimit-policy.
API returns JSON error responses (404 at https://tidbit.legios.com.ar/v1/orank-probe-test)
OpenAPI uses application/problem+json (RFC 7807) for 4xx/5xx responses
API versioning found (URL versioning (servers or paths)) but no deprecation or sunset policy detected - add Sunset/Deprecation headers or a deprecation policy page
How to pass
Declare a versioning policy agents can rely on: version your API (in the URL path or a version header) and publish how you signal deprecation (a Sunset/Deprecation header or a documented timeline). Agents avoid integrating against a surface that can change without warning.
CLI package found on npm: @legios/quartermaster
SDK package found only in npm
How to pass
Publish official SDK packages across multiple language ecosystems (npm, PyPI, Go modules, RubyGems). Auto-generate them from your OpenAPI spec using tools like openapi-generator. For each package set the project URL or homepage to your product domain (package.json repository/homepage, PyPI Home-Page or project_urls, RubyGems homepage_uri) - this is how agents verify the package is your official SDK.
100% of operations define typed response schemas, 100% use application/json
docs MCP: 4/4 tools have behavioral annotations
MCP server card found at https://tidbit.legios.com.ar/.well-known/mcp/server-card.json (server-card extension, all required fields) (note: description is 147 characters; the server-card schema allows 100)
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
66 native controls, 0 non-native div-soup affordances (100% native).
66/66 interactive elements have a computable accessible name (100%).
1/1 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
REST: agent-friendly schema (2 operations, 100% with operationIds, 100% documented by description or summary)
Partial compatibility: 2/2 operationIds, 1/2 typed schemas
How to pass
Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
What does tidbit.legios.com.ar 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 tidbit.legios.com.ar do and who is it for? Explain it back to me.