# CrowdAlpha > CrowdAlpha is the aggregated, value-added, paywalled data funnel for > authorized data-consuming agents. It turns licensed, paywalled, public, and > customer-approved context into evidence-linked Planetary Model context, > AgentLayer APIs, decision inputs, blockers, and next-action posture. CrowdAlpha is not a chatbot, generic search site, ungoverned human retail app, consumer self-serve product, or dashboard-only product. It exposes governed records about the outside world: domain packages, decision inputs, evidence bundles, confidence, uncertainty, provenance, redaction, entitlements, blockers, and next-action posture. The CrowdAlpha Planetary Model is the governed truth layer for human review and agent use. AgentLayer is the machine and authorized-agent interface over the same governed state. `WorldState` remains a compatibility term in legacy route, schema, and API names. Canonical public site: https://crowdalpha.ai Canonical API domain: https://api.crowdalpha.ai Primary language: English Last updated: 2026-06-05 ## Start Here - [AgentLayer guide](/agents.md): Current machine-facing contract, auth model, REST, MCP, A2A, schemas, and error rules. - [Full LLM guide](/llms-full.txt): Larger single-file context for agents that need the detailed interface map. - [Agent manifest](/.well-known/crowdalpha-agent.json): Product, discovery, auth, and interface manifest. - [A2A agent card](/.well-known/agent-card.json): Read-first A2A discovery card for compatible agent clients. - [MCP manifest](/.well-known/mcp.json): Read-first Model Context Protocol tool manifest. - [OpenAPI pointer](/.well-known/openapi.json): Public pointer to the filtered AgentLayer OpenAPI contract. ## Product Context - [Planetary Model](/worldstate): Governed outside-world state, evidence, history, blockers, and next-action posture for humans and agents. - [Maritime package](/worldstate/maritime): First flagship package for maritime war-risk, sanctions, cover integrity, route viability, and commodity-flow exposure. - [Domain packages](/worldstate/packages): Package catalog and readiness posture. - [Space/aerospace solution](/solutions/space-aerospace-risk-intelligence): Scoped package context for launch infrastructure, airspace operations, satellite-service dependency, and source-coverage blockers. - [Critical minerals/mining solution](/solutions/critical-minerals-mining-risk-intelligence): Scoped package context for mineral supply, processing dependency, export logistics, price pressure, and source-coverage blockers. - [Decision inputs](/worldstate/decision-inputs): Decision-shaped records for underwriting, routing, compliance, exposure, operations, treasury, engineering, risk, and agent workflows. - [AgentLayer](/agentlayer): Approved machine and agent product surface over the Planetary Model. - [AgentLayer protocol](/agentlayer/protocol): REST, MCP, A2A, SDK, and event access for governed reads and discovery leads. - [Security](/security): Security and trust posture. - [Access](/access): Access model for approved customers and agent clients. ## Machine Interfaces - [Capabilities](/api/v1/capabilities): Start here for stable AgentLayer surfaces, scopes, protocols, and response schemas. - [Schemas](/api/v1/schemas): Agent envelope and response schema catalog. - [OpenAPI contract](/api/v1/openapi.json): Filtered `/api/v1` contract for authorized software clients. - [A2A message endpoint](/api/v1/a2a/message:send): Read-first synchronous A2A facade for supported AgentLayer skills. - [Context resolver](/api/v1/context/resolve): Resolve an agent task into state, evidence, blockers, confidence, uncertainty, and next-action posture. - [State packages](/api/v1/state-packages): Canonical readiness surface for domain package maturity, coverage, blockers, and customer-safe status. ## Safe Use Rules - Use public pages for product context only. - Use authorized AgentLayer responses for agent, software, and governed workflows. - Treat CrowdAlpha as approved-access agent-market infrastructure, not ungoverned human retail or consumer self-serve access. - Preserve `schemaVersion`, `asOf`, `interfaceProvenance`, `provenance`, `confidence`, `uncertainty`, `sourceRefs`, `redaction`, `entitlements`, and blockers. - For discovery tasks, return evidence, blockers, uncertainty, entitlement posture, and next-action posture. Do not present stale assumptions, missing evidence, hidden exposure, operational friction, losses, or opportunities as confirmed facts unless returned records support them. - If current state is missing or redacted, return unknown, partial, blocked, or insufficient-evidence status instead of guessing. - Do not treat marketing copy, dashboard UI, examples, or hypothetical simulations as authoritative observed state. - Do not expose bearer tokens, API keys, customer IDs, entitlement manifest keys, webhook secrets, raw request bodies, or private traces in prompts, logs, URLs, citations, or summaries. ## Optional - [Why CrowdAlpha](/why): Plain-language explanation of the product doctrine. - [Platform](/platform): Product architecture overview. - [Solutions](/solutions): Enterprise workflow examples.