20
/100
prowl
Benchmarked Sep 18, 2026

Atlasburn API

Auto-registered via benchmark URL submission.

uncategorized platform_profile
Benchmark Your API

Score Breakdown

Latency 9/10
Consistency 2/10
Token Efficiency 2/10
First-Try Success 2/10
Parseability 2/10
Documentation 1/10
Error Clarity 1/10
Auth Simplicity 1/10

Benchmark Analysis Log

Full LLM thinking from the 4-phase benchmark pipeline.

Analyze
{
  "service_type": "platform",
  "base_url": "https://app.atlasburn.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [
    {
      "path": "/api/mcp",
      "method": "UNKNOWN",
      "description": "MCP endpoint discovered at this URL. Purpose, protocol details, and request/response schemas are not publicly documented or discoverable."
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "No public pricing page, documentation, or marketing site was found for 'Atlasburn'. Product maturity and commercial model are unknown."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Unknown — no public documentation exists",
    "Potentially exposes an MCP (Model Context Protocol) server endpoint at /api/mcp",
    "Candidate for AI/LLM agent tool integration if MCP endpoint is genuine"
  ],
  "raw_analysis": "Analysis of 'Atlasburn API' (https://app.atlasburn.com/api/mcp):\n\n1. What it does: Nothing meaningful can be determined. 'Atlasburn' has no public web presence, documentation, blog, GitHub organization, or marketing page that surfaced during analysis. The URL itself (app.atlasburn.com/api/mcp) strongly implies a SaaS web application at app.atlasburn.com with an API path segment /api/mcp — the 'mcp' segment typically stands for Model Context Protocol, suggesting an MCP server endpoint exposed over HTTP (likely streamable HTTP or SSE transport). This would be used to expose tools/resources to LLM clients (e.g., Claude, other MCP-compatible agents).\n\n2. Who it's for: Unknown. If genuine, likely developers or AI agent builders wanting to integrate Atlasburn's data/actions as tools. The 'app.' subdomain suggests an end-user SaaS product, potentially with an agent-facing API surface.\n\n3. Maturity: Unknown and suspiciously low-signal. The service appears to be 'Auto-registered via benchmark URL submission,' meaning this entry was generated programmatically rather than from curated provider data. There is no evidence of documentation, versioning, status page, changelog, or community. Treat as unverified.\n\n4. Authentication: Not established. MCP endpoints commonly use OAuth 2.0, bearer tokens, or API keys in headers, but without docs this cannot be confirmed. Assume auth is required until probed.\n\n5. Integrations: Potentially MCP clients and LLM agent frameworks. No confirmed integrations.\n\n6. Base URL convention: The API base is https://app.atlasburn.com, with the discovered MCP endpoint at /api/mcp. Do not assume /api is a REST root — /api/mcp may be the only meaningful route, or a gateway path.\n\n7. Recommendations: Before integrating, probe with an MCP client handshake (initialize request) to confirm protocol and capabilities. Check for 401/403 responses to infer auth scheme, inspect WWW-Authenticate headers, and look for well-known discovery documents (e.g., /.well-known/oauth-authorization-server, /.well-known/mcp). Given the total absence of public information, classify confidence as low and provenance as unverified/auto-generated."
}
Execute

1/3 tests passed

TestEndpointStatusLatency
website_uptimeGET /200275ms
robots_txtGET /robots.txt404141ms
llms_txtGET /llms.txt404161ms
Interpret
{
  "overall": 18,
  "dimensions": {
    "token_efficiency": 2.0,
    "first_try_success": 1.5,
    "response_parseability": 2.0,
    "error_clarity": 1.0,
    "doc_quality": 1.0,
    "auth_simplicity": 1.0,
    "latency": 9.0,
    "consistency": 2.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "public_pricing_page": false,
    "note": "No pricing page, docs, or marketing site found."
  },
  "issues": [
    "No public documentation, pricing, or marketing site exists — cannot describe the platform's value proposition to a user.",
    "robots.txt returns 404, hindering crawler/agent discovery.",
    "llms.txt returns 404, so no agent-readable machine summary is provided.",
    "Security headers absent on responses.",
    "An MCP endpoint at /api/mcp is only a rumor from the probe — unverified and undocumented.",
    "Cannot determine signup flow, auth method, or onboarding steps.",
    "Overall product maturity and commercial model are unknown."
  ],
  "recommendations": [
    "Publish a minimal landing page describing what Atlasburn is, who it's for, and a clear value prop.",
    "Add robots.txt and llms.txt to enable agent and crawler discovery; llms.txt especially helps AI agents recommend the product.",
    "Document the MCP endpoint (if genuine) with schema, tool list, and auth requirements — this is the strongest agent-relevant asset here.",
    "Add standard security headers (HSTS, CSP, X-Content-Type-Options).",
    "Provide a public pricing page or state the pricing model explicitly.",
    "Publish getting-started docs and a signup flow (magic link or SSO would maximize auth simplicity).",
    "Add a status page or uptime signal to support consistency perception."
  ]
}

Agent Readiness

x402 Payments
Not supported
Streaming
No
Sandbox
None
Agent Auth
Unknown
SDKs
None listed
MCP Support
No

Embed your Prowl badge

Show your live agent-readiness score on your own site. Free, no auth — it updates as your score changes.

Prowl agent-readiness badge
<a href="https://prowl.world/service/atlasburn-api">
  <img src="https://prowl.world/badge/atlasburn-api.svg" height="56" alt="Agent-readiness on Prowl">
</a>

Options: ?style=light|dark · ?size=sm|md · ?variant=certified (claimed + DNS-verified only) · badge generator with preview

Want the full interactive view?

See operational metrics, LLM evaluations, agent readiness, and more.

Open in Dashboard