Dedica offers robust REST API access and OpenAPI documentation, but lacks brand name search visibility for agent discovery.
DiscoveryCan agents discover and fetch your site?
12/20points
AccessCan agents get the answer from what they fetch?
28/30points
UsabilityCan agents complete a task through an interface?
34/40points
PaymentsCan agents complete a payment?
—not scored
All checks
Group by
01Can an agent discover and trust you?Can agents reach your pages, find them, and confirm they belong to you?ROBOTSSITEMAPSKILLSDISCOVERY65/1005 shown · 5 in the fix kit
Brand name discoverabilityFailedbrand-search-accuracyRequiredVerifiedgetdedica.com was not in the top 10 for "Dedica AI agents"+3.9est. points
Scan result
getdedica.com was not in the top 10 for "Dedica AI agents"
What this checks
When people search for your brand together with your main product, your domain should be in the top results. If it is not, agents cannot reliably tell you apart from lookalikes and resellers.
Suggested change
Make sure your own domain ranks in the top results when people search your brand together with your main product (for example "Acme payments API"). If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen it by describing your main product clearly in your homepage title and headings, earning press mentions that link to your domain, and avoiding redirect chains that mask your main domain in search results.
Check the result
Rescan getdedica.com after the change, then inspect the affected public page or endpoint directly.
Developer resource discoverabilityWarningagentic-search-specificRecommendedVerifiedName search surfaced no pages on getdedica.com, although developer resources exist on the site (API docs, OpenAPI spec, MCP server) - weak search indexing or transient search noise+2.6est. points
Scan result
Name search surfaced no pages on getdedica.com, although developer resources exist on the site (API docs, OpenAPI spec, MCP server) - weak search indexing or transient search noise
What this checks
Can an agent that knows your name find your developer resources by searching: API docs, OpenAPI spec, MCP server, auth docs, developer portal, SDK documentation? Any one recognized resource type earns full marks. Missing resources refer to
Listed in MCP registriesFailedmcp-registry-listedRecommendedVerifiedNo bi-directionally verified MCP registry entry found. To pass, either publish the server from a package whose homepage, repository or maintainer email names your domain, get a verified Smithery listing with non-zero usage, or link the registry entry from your homepage or docs.+1.3est. points
Scan result
No bi-directionally verified MCP registry entry found. To pass, either publish the server from a package whose homepage, repository or maintainer email names your domain, get a verified Smithery listing with non-zero usage, or link the registry entry from your homepage or docs.
What this checks
Agents find MCP servers through registries the way people find apps through app stores. We check the major ones (Smithery, mcp.so) for an entry verified against your domain.
NPM/PyPI SDK packageFailednpm-sdk-packageRecommendedVerifiedNo NPM or PyPI SDK package found+1.3est. points
Scan result
No NPM or PyPI SDK package found
What this checks
An official SDK or CLI on NPM or PyPI gives agents and the developers steering them a ready-made way in, instead of hand-rolling every API call.
Wikipedia / Wikidata entity presenceFailedwikipedia-presenceRecommendedVerifiedBonusNo Wikipedia article or Wikidata entity found for "dedica" - creating a Wikipedia page and a Wikidata item with P856 = getdedica.com is the highest-impact step for AI search citation coverage+1.7est. points
Scan result
No Wikipedia article or Wikidata entity found for "dedica" - creating a Wikipedia page and a Wikidata item with P856 = getdedica.com is the highest-impact step for AI search citation coverage
What this checks
A Wikipedia article and Wikidata entry that link to your domain. Wikipedia is the largest single source of citations in AI answers (~48% of ChatGPT citations), so presence there decides whether AIs can verify who you are.
5 more issues in this goal, each with a fix promptGet the fix kit
02Do you welcome agents?Do your crawler rules and security checks let legitimate agents through?ROBOTSCRAWLBOT AUTH100/1001 issue
Web Bot Auth directoryFailedweb-bot-auth-directoryEmergingEmergingBonusNo /.well-known/http-message-signatures-directory found
Scan result
No /.well-known/http-message-signatures-directory found
What this checks
A public key directory (RFC 9421) that lets agents cryptographically sign their requests, so you know exactly who is calling and can let the good ones through.
03Does an agent understand who you are and what you do?Can an agent explain your business using the content and facts on your site?HTMLJSON-LDNLWEBLLMS.TXTSKILLSDOCS86/1003 issues
JSON-LD entity linking (sameAs)Failedjson-ld-entity-linkingRecommendedVerifiedNo sameAs entity linking in JSON-LD - agents cannot disambiguate your brand+1est. points
Scan result
No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand
What this checks
sameAs links from your structured data to your official profiles (GitHub, LinkedIn, app stores). They let AIs confirm that every mention of you is actually you.
Organization schema completenessWarningorg-schema-completenessRecommendedVerifiedOrganization schema found but missing: address+0.5est. points
Scan result
Organization schema found but missing: address
What this checks
Company details (contact, address) in your structured data. AIs use them to verify you are a real business before recommending you.
Schema type breadthWarningschema-type-breadthRecommendedVerifiedSome extended schema types found: Service - add 2 more types that match what the homepage shows, for full coverage+0.5est. points
Scan result
Some extended schema types found: Service - add 2 more types that match what the homepage shows, for full coverage
What this checks
The more kinds of content you mark up with schema.org (FAQs, reviews, services, events, videos), the more kinds of questions an AI can answer about you with confidence.
04Can an agent integrate with you?Can an agent connect through a documented API, tool server, or software kit?LINKSSKILLSDOCSAPIOPSSDKMCP83/1003 issues
An official CLI. Coding agents live in the terminal, so a CLI makes your product directly operable by the fastest-growing class of agents.
Multi-language SDK packagesFailedrest-sdk-packagesRecommendedVerifiedNo SDK packages found across language ecosystems+1.3est. points
Scan result
No SDK packages found across language ecosystems
What this checks
Official SDKs across ecosystems (npm, PyPI, Go). Each one is an integration an agent does not have to hand-roll, in the language it is already working in.
Sandbox / test environmentWarningsandbox-environmentRecommendedVerifiedBonusSandbox/test environment mentioned at https://getdedica.com/developers.md but no sandbox surface verified+0.1est. points
Scan result
Sandbox/test environment mentioned at https://getdedica.com/developers.md but no sandbox surface verified
What this checks
A sandbox or test mode where agents can build an integration without touching production data. It lowers the stakes of every first call.
05Is your integration well-built?Can an agent tell what your software tools do and how to call them?APIMCP97/1001 issue
MCP tool listingWarningmcp-tool-listingRecommendedVerifiedBonusproduct MCP exposes 2 tool(s) - consider adding more for comprehensive agent coverage+0.1est. points
Scan result
product MCP exposes 2 tool(s) - consider adding more for comprehensive agent coverage
What this checks
Your MCP server actually returns tools when asked. We call tools/list and grade the surface: product servers earn on breadth, docs servers on focus.
Agent interface
producthttps://getdedica.com/api/mcp
06Can an agent use you reliably in production?Does your API handle errors, usage limits, more results, and retries predictably?APIOPSMCP64/1003 shown · 2 in the fix kit
Idempotency-Key supportFailedidempotency-key-supportRecommendedVerifiedNo REST Idempotency-Key support detected+1.3est. points
Scan result
No REST Idempotency-Key support detected
What this checks
Networks fail mid-request. Idempotency keys let an agent retry a payment or an order safely, without doubling it. We check that write endpoints accept the header.
REST versioning / deprecation policyWarningapi-versioning-policyRecommendedVerifiedDeprecation or versioning policy mentioned in prose at https://getdedica.com/developers.md - formalize in OpenAPI spec for full credit+0.9est. points
Scan result
Deprecation or versioning policy mentioned in prose at https://getdedica.com/developers.md - formalize in OpenAPI spec for full credit
What this checks
Agents integrate once and then run unattended. A versioning and deprecation policy is your promise about when things will break and how much warning they get.
Long-running operations should return 202 Accepted with a way to poll for the result. Otherwise agents time out and retry work that was still running.
2 more issues in this goal, each with a fix promptGet the fix kit
07Can an agent authenticate to you?Can an agent sign in with limited permission without asking a person every time?SDKMCPOAUTHAUTH.MDPAP90/1003 shown · 4 in the fix kit
Agent onboarding frictionWarningonboarding-frictionRecommendedVerifiedVerified live: GET https://getdedica.com/ask answered 200 without credentials (zero-auth access). Described but not verified live: self-serve key generation, sandbox/test environment+0.4est. points
Scan result
Verified live: GET https://getdedica.com/ask answered 200 without credentials (zero-auth access). Described but not verified live: self-serve key generation, sandbox/test environment
What this checks
Can an agent go from discovering you to a first successful API call with no human in the loop? Every manual step is a place automated integrations quietly die.
Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: getdedica.com, api.getdedica.com.
What this checks
The machine-readable half of agent auth: discovery documents (RFC 9728 and 8414) with an agent_auth block that round-trips to your auth.md, so agents can look up the exact request shape for each supported identity type.
agent_auth endpoints reachableFailedagent-auth-endpoints-reachableRecommendedVerifiedBonusNo agent_auth endpoint URIs found in AS metadata or /auth.md prose; nothing to probe+0.1est. points
Scan result
No agent_auth endpoint URIs found in AS metadata or /auth.md prose; nothing to probe
What this checks
The registration, claim, and revocation surfaces your auth docs advertise actually respond. Stale discovery data is worse than none: it sends agents to doors that no longer exist.
4 more issues in this goal, each with a fix promptGet the fix kit
08Can an agent transact with you?Can an agent find your prices and pay through a supported payment method?PRICINGX402MPPUCPACPAP2100/1000 issues
No free check summaries in this goal.
09Can an agent operate your website directly?If there is no API, can an agent read and use your website directly?HTMLNLWEBLLMS.TXTWEBMCPMARKDOWNA11Y100/1001 issue
Agent mode viewWarningagent-mode-viewEmergingEmergingBonusAgent mode view found at ?mode=agent (5 signals: openapi, mcp, api, endpoint, agent)
Scan result
Agent mode view found at ?mode=agent (5 signals: openapi, mcp, api, endpoint, agent)
What this checks
A stripped-down, structured view of your site at ?mode=agent, built for machine readers: plain content and direct endpoint links.
Fix prompts for all 31 issues
You can see 20 of them above. The fix kit lists all 31 in priority order and gives each one a prompt for Claude Code, Cursor or another coding agent. Each prompt says what to change and how to check it worked.
# Fix "Brand name discoverability" on getdedica.com
## Goal
Improve getdedica.com's agent readiness by resolving the finding below in the connected codebase. Implement the change; do not return advice alone.
## Finding
- Check ID: brand-search-accuracy
- Layer: Discovery
- Status: fail
- Check points: 0/3
- Estimated overall score gain: +3.9 points
- Finding: getdedica.com was not in the top 10 for "Dedica AI agents"
- Why it matters: When people search for your brand together with your main product, your domain should be in the top results. If it is not, agents cannot reliably tell you apart from lookalikes and resellers.
- Recommended change: Make sure your own domain ranks in the top results when people search your brand together with your main product (for example "Acme payments API"). If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen it by describing your main product clearly in your homepage title and headings, earning press mentions that link to your domain, and avoiding redirect chains that mask your main domain in search results.
## Work instructions
1. Inspect the repository first. Identify its framework, relevant routes or configuration, and existing conventions; do not assume file paths or implementation details from the finding alone.
2. Confirm how the finding maps to the current code and make the smallest correct change that addresses the recommendation. Keep unrelated behavior intact.
3. If a recommendation does not fit this product or requires unavailable credentials, policy, or backend access, explain the blocker instead of inventing details or making an unrelated change.
4. Run the relevant checks already available in the repository and report exactly which commands passed or failed. Do not claim a check passed unless you ran it.
## Verification
- Test the affected page or API behavior directly for getdedica.com.
- After changes are deployed, rescan getdedica.com in Dedica and confirm the check's result. If the site is not live yet, say that a public rescan is still needed.
- Report the files changed, checks run, remaining issues, and any assumptions.
## Site context
- Domain: getdedica.com
- Scan date: 2026-10-23
- Score: 82/100 (B)
- Summary: Dedica offers robust REST API access and OpenAPI documentation, but lacks brand name search visibility for agent discovery.
- Layer breakdown:
- Discovery: 12/20
- Access: 28/30
- Usability: 34/40
- Payments: Not scored
Score gains are estimates, not guarantees. A passing scan check is not a substitute for testing the real user task.
Checks reference the AgentReady open specification. The numeric score is separate and is not a conformance result or certification.