www.faire.com/blog
Finalizing the report
Preparing the stored Is Agentic score
www.faire.com/blog
Preparing the stored Is Agentic score
www.faire.com/blog
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.
Needs work
Weighted across 15 applicable checks
Ready with gaps
Weighted across 12 applicable checks
Blocked
Weighted across 3 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup. Inner pages need their main text in the raw HTML too, not only after JavaScript runs.
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
Implement OAuth 2.0 for API authentication. Publish your authorization server metadata at /.well-known/oauth-authorization-server.
Declare scoped API permissions where machines can read them: named OAuth scopes in your OpenAPI security schemes, or scopes_supported in RFC 9728 protected-resource metadata. Prose descriptions of roles help humans, but agents need the machine-readable declaration to request least-privilege access.
Make sure a web search for your product's API docs returns your own docs page, and a search for your MCP server, SDK or CLI returns your own pages for those tools. Keep docs on your own domain or a subdomain, or link your docs site from your homepage or llms.txt, give each tool its own page (for example /mcp) with the tool name in the title, put your product name and "API" in the docs title and main heading, and link your GitHub org from your homepage.
Checks are grouped by relevance for Commerce sites.
Homepage: 6612 chars of readable text, but no H1 tag. No inner pages checked: the 5 sampled pages were skipped (forms, login pages, bot challenges, error pages, non-HTML pages and pages over 1 MB are skipped).
How to pass
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup. Inner pages need their main text in the raw HTML too, not only after JavaScript runs.
Site accessible to 3 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User). Can't verify PerplexityBot. Your site also blocked a normal browser visit, so we can't tell if agents get in.
No meta-refresh or JavaScript-redirect stubs across 1 checked page
All 5 sampled pages are publicly readable (0 with substantive content)
OpenAPI spec found at https://faire.com/.well-known/openapi.json (version: 3.0.3)
Homepage https://faire.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html;charset=utf-8; Vary header missing Accept (got "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, accept-encoding")
How to pass
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
OAuth mentioned on homepage but no standard endpoints found
How to pass
Implement OAuth 2.0 for API authentication. Publish your authorization server metadata at /.well-known/oauth-authorization-server.
OpenAPI declares security schemes but no named OAuth scopes - agents get all-or-nothing access. Declare per-scope grants (e.g. read:*, write:*) in the spec.
How to pass
Declare scoped API permissions where machines can read them: named OAuth scopes in your OpenAPI security schemes, or scopes_supported in RFC 9728 protected-resource metadata. Prose descriptions of roles help humans, but agents need the machine-readable declaration to request least-privilege access.
API returns JSON error responses (401 at GET https://www.faire.com/external-api/v2/product-inventory/by-product-variant-ids, an operation in the OpenAPI spec)
In a search for your API docs, none of the 10 results is your official docs
How to pass
Make sure a web search for your product's API docs returns your own docs page, and a search for your MCP server, SDK or CLI returns your own pages for those tools. Keep docs on your own domain or a subdomain, or link your docs site from your homepage or llms.txt, give each tool its own page (for example /mcp) with the tool name in the title, put your product name and "API" in the docs title and main heading, and link your GitHub org from your homepage.
faire.com ranks #7 for "Faire" (searched your brand name alone: no main product term from your homepage qualified)
How to pass
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"). Ora first reads product terms from your homepage's JSON-LD keywords or knowsAbout, or its meta keywords tag. If none qualifies, it checks the main service's serviceType in JSON-LD, then a short product phrase in the page title. If those do not qualify, it checks product names in the homepage business's JSON-LD offers. Use clear product terms that also appear on the page. If no term qualifies, Ora searches your brand name alone. If your domain does not rank, 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.
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.faire.com/sitemap-index.xml.gz with multiple sitemaps entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (2 blocks)
No pricing page or pricing data found
How to pass
Put price data in each product page's JSON-LD or microdata. Use a schema.org/Product whose offers is a schema.org/Offer with price, priceCurrency, and availability, or AggregateOffer for a variant price range, so agents can read prices without scraping a marketing page.
Documentation site found at https://developers.faire.com
No agent instruction file with when-to-use guidance found
How to pass
Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases and how an agent should call you. Be specific about the jobs you are right for - generic marketing copy does not read as guidance.
2/4 metadata signals present - missing: canonical URL, og:image
How to pass
Add all four signals to your homepage: <link rel="canonical"> pointing to the page on your own site, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
Organization schema found but missing: contactPoint
How to pass
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
No trust anchor pages found with sufficient content (About, Contact, Privacy)
How to pass
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
All 1 measured page fit an agent context budget (largest ~2K tokens)
Developer documentation portal found at https://developers.faire.com
Documented REST API detected; endpoints require authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7.
Onboarding signals described but not verified live: 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.
The live API operation https://www.faire.com/external-api/v2/brands/profile returns legacy retry-after headers. Adopting the IETF RateLimit headers would earn full credit.
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.
Partial typed error model: error schema defined but not consistently referenced (or vice versa)
How to pass
Document your error responses in your OpenAPI spec: give 4xx and 5xx responses a typed error schema (or use RFC 9457 application/problem+json). A consistent error object with a machine-readable code and a human-readable message lets agents handle failures without guessing.
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.
No CLI tool found
How to pass
Publish an official CLI tool on npm, PyPI, or Homebrew. A CLI lets agents and developers script interactions with your product without building API integrations from scratch.
83% of operations define typed response schemas, 83% use application/json
REST: schema found (40 operations) but only 0% of operations carry an operationId
How to pass
Make your API spec self-describing: a unique operationId and a description on every operation, typed parameters, and response schemas. For GraphQL, a fully typed schema with a documented cost or rate limit reads best.
Partial compatibility: 0/40 operationIds, 38/40 typed schemas
How to pass
Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
Wikidata Q139785345 (Faire) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage
How to pass
Establish a Wikipedia article and a Wikidata entity for your brand, with the domain set as the official website (Wikidata property P856) and a corresponding external link on Wikipedia. Wikipedia is the largest single source of citations in ChatGPT and a primary input to Knowledge Graphs across Google, Bing, and LLM training data. Earn third-party press coverage first to satisfy notability, then draft the article with cited references rather than self-promotion.
NPM package found: @faire/mjml-react - "React component library to generate the HTML emails on the fly"
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.
Cursor-based pagination found in OpenAPI spec response schemas or query parameters
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.
Batch endpoint found in OpenAPI spec (/batch path)
98 native controls, 1 non-native div-soup affordances (99% native).
98/98 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.
What does www.faire.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.faire.com do and who is it for? Explain it back to me.
4 steps1 reasoning step
The agent successfully gathered a comprehensive overview of Faire's business model, pricing, and target users from the site's core pages. However, the site scatters key pricing details (commissions, payment-processing fees, net-60 eligibility criteria) across multiple pages and omits quantified information on order minimums, shipping rates, and promo terms, forcing the agent to document gaps rather than fill them.