brownsmithdynamics.com
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
brownsmithdynamics.com
Preparing the stored Is Agentic score
brownsmithdynamics.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
Ready with gaps
Weighted across 12 applicable checks
Blocked
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.
5706 chars, semantic headings (1 H1 + 9 H2s + 16 H3s), 11.0% 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
brownsmithdynamics.com ranks #1 for "Brownsmith Dynamics Lead Generation"
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://brownsmithdynamics.com/sitemap.xml with 85 entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (4 blocks)
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 6 measured pages fit an agent context budget (largest ~4K tokens)
Name search surfaced no pages on brownsmithdynamics.com, although developer resources exist on the site (API docs, OpenAPI spec) - 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.
99% of 85 sampled sitemap entries carry lastmod; newest is 0 day(s) old
Found the llms.txt at https://brownsmithdynamics.com/llms.txt.
The llms.txt is well-formatted: 66 lines with markdown links, 10,901 characters in total.
Pricing page found at /pricing
API/docs link found on homepage and resolves: /docs
When-to-use guidance found in llms.txt
Strong entity linking via sameAs: linkedin.com, github.com
Some extended schema types found: ItemList, Service - add 1 more type, such as FAQPage, AggregateRating, or Review, for full coverage
How to pass
Add 1 more JSON-LD type that fits your page, such as FAQPage, AggregateRating, or Review.
All 5 probed llms.txt links resolve to real content
Code fences balanced across 1 markdown document
OpenAPI spec found at https://brownsmithdynamics.com/openapi.json (version: 3.1.1)
Developer portal found at /docs
Returns markdown when requested via Accept header
REST API documentation found at https://brownsmithdynamics.com/docs. Best-of-protocols score: 7/7.
Verified live: GET https://brownsmithdynamics.com/api/public-business-information answered 200 without credentials (zero-auth access). Described but not verified live: free tier available, self-serve key generation, sandbox/test environment
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 redirects to an HTML page (https://mcp.brownsmithdynamics.com/), not an MCP endpoint
How to pass
Build an MCP (Model Context Protocol) server exposing your API as tools. Use Streamable HTTP transport for full score. This lets Claude, ChatGPT, and other AI agents call your product natively.
API returns JSON error responses (404 at https://brownsmithdynamics.com/api/v1/orank-probe-test)
OpenAPI defines a typed error schema in components.schemas and 4xx/5xx responses reference it
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.
100% of operations define typed response schemas, 71% use application/json
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
90 native controls, 3 non-native div-soup affordances (97% native).
90/90 interactive elements have a computable accessible name (100%).
4/4 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
REST: agent-friendly schema (7 operations, 100% with operationIds, 100% documented by description or summary)
Partial compatibility: 7/7 operationIds, 2/7 typed schemas
How to pass
Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
What does brownsmithdynamics.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 brownsmithdynamics.com do and who is it for? Explain it back to me.
7 steps2 reasoning steps
The agent successfully gathered enough information to explain Brownsmith Dynamics' core business model, target market, and positioning. The site was moderately navigable but lacked pricing transparency and concrete examples of AI/automation results; the agent had to work around incomplete case study relevance.