Column

{
  "service_type": "platform",
  "base_url": "https://column.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "ACH payments",
    "Wire transfers (FedWire)",
    "Realtime payments (FedNow)",
    "Book transfers",
    "Check processing (RDC, checkbooks, positive-pay)",
    "Bank account creation (FDIC insured)",
    "Card issuing programs",
    "Ledgering",
    "International wires (Swift)",
    "Loan origination",
    "Loan purchase",
    "Debt financing"
  ],
  "raw_analysis": "Column is a nationally chartered bank (Column N.A.) built for developers, providing banking infrastructure via API. It offers a range of products including ACH, wire, realtime payments (FedNow), book transfers, checks, bank accounts, card programs, ledger, international wires, loan origination, loan purchase, and debt financing. The platform is aimed at developers and builders creating financial products. It provides comprehensive developer documentation at docs.column.com and a full site summary at column.com/llms-full.txt. The company emphasizes being built from the ground up for developers, with a focus on modern API access to traditional banking services. The service appears mature, with a changelog indicating ongoing updates. Pricing model is not specified on the page, likely custom or subscription-based. Authentication details are not provided on the surface but would be covered in developer documentation. No explicit rate limits mentioned."
}

3/3 tests passed

{
  "overall": 82,
  "dimensions": {
    "token_efficiency": 9.5,
    "first_try_success": 7.5,
    "response_parseability": 9.5,
    "error_clarity": 8.5,
    "doc_quality": 9.0,
    "auth_simplicity": 6.5,
    "latency": 9.5,
    "consistency": 8.5
  },
  "pricing_normalized": {
    "type": "unknown",
    "note": "Pricing not disclosed on public landing surface; likely custom/enterprise bank pricing. Agents can't quote a concrete price to users."
  },
  "issues": [
    "No published pricing model — agents cannot give users a concrete cost answer, which is often the first follow-up question.",
    "No security headers detected on responses (e.g. HSTS, CSP) — minor trust/security signal gap for a banking platform.",
    "robots.txt disallows /legal/ and /docs/extended-api/ — some documentation is deliberately gated from crawlers/agents.",
    "Onboarding likely requires business/KYC process inherent to a chartered bank; not a pure self-serve 'sign up and go' experience.",
    "Auth flow (API keys, possibly business verification) not fully self-evident from the public surface; no magic-link/SSO-style instant onboarding signal."
  ],
  "recommendations": [
    "Publish a pricing page or at least a pricing model summary in llms.txt so agents can answer cost questions directly.",
    "Add a concise 'getting started in N steps' block to llms.txt/robots-adjacent surfaces to boost first-try success.",
    "Emit security headers (HSTS, CSP, X-Content-Type-Options) — cheap trust win for a bank.",
    "Consider exposing a machine-readable capabilities/openapi manifest (llms.txt already points to docs; ensure an OpenAPI spec is linked) to maximize parseability.",
    "Reduce reliance on gated docs for agent discovery; surface key limits (rate limits, tiers, KYC requirements) in llms.txt."
  ]
}