chainflip-broker.io
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
chainflip-broker.io
Preparing the stored Is Agentic score
chainflip-broker.io
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 16 applicable checks
Ready with gaps
Weighted across 12 applicable checks
Strong
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
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.
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.
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.
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.
Checks are grouped by relevance for App sites.
1582 chars, semantic headings (1 H1 + 7 H2s + 4 H3s), 9.3% content ratio
Site accessible to 6 AI agent user-agents
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)
OpenAPI spec found at https://chainflip-broker.io/openapi.json (version: 3.0.4)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
No OAuth 2.0 or OpenID Connect support detected
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 (404 at https://chainflip-broker.io/ (from OpenAPI servers))
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
Valid sitemap found at https://docs.chainflip-broker.io/sitemap.xml with 32 entries
Rich JSON-LD identity: SoftwareApplication with name, description, url, and category/offers (1 block)
Pricing page found at /pricing
Documentation site found at https://docs.chainflip-broker.io
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 ~1K tokens)
REST API documentation found at https://docs.chainflip-broker.io/features/rpc/. Best-of-protocols score: 7/7.
Onboarding signals described but not verified live: self-serve key generation, sandbox/test environment, zero-auth access
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 - Broker as a Service vv1 (protocol 2025-11-25)
No REST rate-limit headers found on probed endpoints
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.
OpenAPI defines a typed error schema in components.schemas and 4xx/5xx responses reference it
Sunset or Deprecation headers found in OpenAPI spec but no URL or header versioning strategy detected
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.
100% of operations define typed response schemas, 89% use application/json
REST: agent-friendly schema (19 operations, 100% with operationIds, 100% documented by description or summary)
Compatible: 19/19 ops with IDs, 16/19 with typed schemas
Agent found 2 pages by name but no recognizable developer-resource type. Found on site but absent from this search sample: OpenAPI spec. Not found in this search sample: SDK documentation
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.
Verified in Smithery as chainflip-broker/baas via entry-to-product - 506 agent uses
MCP server referenced in llms.txt
Found the llms.txt at https://chainflip-broker.io/llms.txt.
The llms.txt is well-formatted: 33 lines with markdown links, 4,922 characters in total.
When-to-use guidance found in llms.txt
All 5 probed llms.txt links resolve to real content
Code fences balanced across 1 markdown document
Developer portal found at /docs
RFC 9727 api-catalog with 2 API link(s) and rfc9727 profile
Returns markdown when requested via Accept header
All 6 tools on product MCP have detailed descriptions (>= 20 chars)
5/6 tools on product MCP have parameter schemas, 5 with required fields
product MCP identifies as "Broker as a Service" vv1 with instructions
product MCP exposes 6 tools - substantial tool surface
All 6 tool names follow consistent convention, descriptive, and non-generic
product MCP returns structured JSON-RPC errors with code and message
product MCP uses modern Streamable HTTP transport
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.
product MCP: 6/6 tools have behavioral annotations (readOnlyHint/destructiveHint)
MCP server card found at https://chainflip-broker.io/mcp/server-card (server-card extension, all required fields)
Server HTML is a well-structured document (main=true, landmarks=3/4, h1=1, maxHeadingSkip=1).
35 native controls, 0 non-native div-soup affordances (100% native).
35/35 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does chainflip-broker.io 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 chainflip-broker.io do and who is it for? Explain it back to me.
17 steps2 reasoning steps6 searches
The agent assembled a comprehensive explanation of Chainflip-broker.io's purpose, target audience, and differentiation from competitors, but could not locate public pricing information for the managed BaaS service itself. The site's homepage and docs were minimal or JavaScript-heavy, forcing heavy reliance on external Chainflip protocol documentation and web search results rather than self-contained chainflip-broker.io pages.